Whether you are a Drupal newcomer or a seasoned Drupal developer, you're bound to run into one, some, or all of the issues outlined below. Some are obvious, some not so obvious, but we'll show you how to troubleshoot them all regardless.
Firewise USA™'s paper application process existed for 15 years but, in 2016, the Firewise team decided to bring the process online. They chose to build this process on top of Drupal 8.
Since moving to Drupal, the Wildfire Division of the National Fire Protection Association has streamlined their processes - enabling them to more efficiently deliver on their program’s goal: teaching individuals how to adapt to living with wildfires and take community action to prevent loss of property.
Join us, Acquia, and our client Aron to discuss the challenges and rewards of bringing a paper process online as a Drupal 8 web app. Topics we’ll discuss:
- Leveraging an agile philosophy to respond quickly to change, collaborate across disciplines and stakeholder groups and get to a working product in as little time as possible.
- Balancing effective deliverables with shared understanding to produce working software that meets the organization’s needs.
- Organizational hurdles to overcome when adding structure and bringing an established paper application process online.
A point of sales system is already in production in Drupal 7; people are using it and seem to like it. And now, we've ported it to Commerce 2 for Drupal 8. Check out this week's High5 to learn more!What does this mean?
In Drupal 8, the POS is much more built in, and you can easily do things like change out widgets. So if you update your orders and you add a new field, the field will show up there. If you add a specific widget that controls how that field displays, you can pick from a list of available options and it will work in the POS.How is this different?
In Drupal 7, the POS was very stand alone—it was all custom-built forms and custom-built options. You actually configured it outside of Commerce itself. It used some of the underlying parts of Commerce, but from a user perspective it was almost as if it was a separate module.
For Drupal 8, that's not the case. It has the same level of functionality, but it's integrated much more so you can use a lot of the Commerce infrastructure. For instance: Drupal 7 had the concept of locations (as in store locations), but Drupal 8 has the concept of stores built right in, so we just use that. There's lots of stuff that goes along with stores: you can attach addresses and extra billing information and so on, and the POS can take full advantage of that in Drupal 8.Are there any new features?
We have quite a bit more reporting (such as KPI reports for tacking metrics for sales people, for instance.) We also have a new "quick add" section that lets you easily add common products without having to look them up by SKU—it's quite robust and fits nicely into the user interface.When will all this be ready?
We're only at Alpha 1 right now. Alpha 2 should be coming soon. The module should be fully ready to go in the near future. You can download it's current state and follow progress here.The bottom line
POS is finally ready for Drupal 8. You can start using it, and we're going to continue releasing new features at least once a month for the foreseeable future.
Hello Drupalers! Here is another #Tips&Trick to make your placeholder translatable. Recently, I have an opportunity to fix one of the issues in Drupal 8 instance where the website was not multilingual hence unable to handle internationalization. After fixing the issue, the contact form now supports more than 25 languages. Let me explain you, what exactly was the issue over here? And how did we overcome this issue?
Issue: Here, Drupal Contact Form Placeholder was not translatable from User Interface Translation.
As we all know anything passes…
This time we want to draw your attention to one of the serious questions - Drupal adoption, and two easy things everyone can do to facilitate it. I guess the Drupal Community helped you a lot when you were a newbie. Now it’s time to pay back and help the Community and its developers to grow and mature faster.
Appnovation Technologies: Website Accessibility Series, Part 2: Accessibility, Audits and Alterations
We recently Open Sourced our temporary environment builder, M8s. In this blog post we will be demoing everything you need to get started!by Nick Schuch / 21 November 2017 Introduction
In this video we will introduce you to M8s and the problem which it is solving.Provisioning a M8s cluster
Now that you are acquainted with the M8s project, it's time to get a cluster provisioned!
In this video we will setup a Google Kubernetes Engine cluster and deploy the M8s API components.Setting up CircleCI
Now that our M8s cluster is up and running, it's time to setup our pipeline to run a build.
In this video we will be configuring CircleCI to run the M8s CLI.Pushing a topic branch
It's time to put it all together!
In this video we will be pushing a topic branch to demonstrate how M8s interacts with a Pipeline.Finale
You made it to the finale! In this video we will be checking out the build environment and how a developer can access the Mailhog and Solr containers.Conclusion
To learn more about the M8s project you can go and checkout:
We welcome any and all feedback via Twitter and our Github Project issues page.Tagged m8s, Kubernetes, Drupal Development
Sys Ops Lead
Dated 21 November 2017Add new comment
This month, our membership campaign celebrates the ways we, together, build community on the home of the Drupal project. Hear from the Drupal Association team how and why Drupal.org offers you tools to make more connections, to increase your potential for a fulfilling professional career, and to enable your contributor journey in Drupal.
You can do a lot on Drupal.org and its sub sites. Check out the campaign page. We hope you are inspired to learn more about what Drupal.org offers and if you aren't yet a Drupal Association member, join today!Want to help our campaign?
We need your help so we meet our two goals: sign up 50 new members and raise $1500. We've made a page of resources for you to share.
Thank you for building community with us!