Lots of people think that template engines like Twig cannot be interactively debugged. I heard this several times as an argument against template engine, and for using legacy php processing like phptemplate (standard in Drupal 7).
Well, it’s not entirely true.
Welcome to Post #2 in my series about debugging in Drupal 8.
Regardless of the purpose of your Drupal site, it is important that the site be reliably available and performant for your users. For those of us with limited resources at our disposal it isn’t feasible to scale up hardware indefinitely. Thankfully, Drupal provides us with a number of tools in core, and even more in the contrib community, that make caching accessible to even the least technical amongst us. Let’s walk through the basics of the Drupal cache and discuss the importance of properly configuring cache with the goal of avoiding common missteps.
Deploying your website to production shouldn't be stressful. It should be easy. You should release with confidence.
To make that a reality, you need a repeatable, reliable and most importantly automated deployment process. BLT provides tools for connecting your GitHub, Travis CI, and Acquia Cloud accounts together to ensure that changes to your website are validated, tested, and deployed automatically.
This is Part 3 of an interview with Will Eisner, Senior Director, Product at Acquia.
Drupal is one of the most flexible content management systems in existence.
If there's anyone who has command of the command line, it's Dave Myburgh, a senior engineer at Acquia.
So we asked him to share how he works with the CLI -- to help us all improve the way we work. Here are the top ten command line tips that Dave suggested. Check them out, and increase your speed of development.
When you spin up sites for a living, velocity is important. The developers at Acquia understand this, which is why we’re always looking for ways to make website development simpler and easier.