There are many different approaches to progressively decoupling Drupal, all with different pros and cons. This webinar will cover the different compelling approaches and some use cases of each, including:
Now that we've covered debugging Drupal 8 in PhpStorm using local web-based approaches, let's move on to command line debugging.
As Drupal is increasingly widely used as a back end for application ecosystems, developers of wildly diverse backgrounds are now retrieving and manipulating data from Drupal in unprecedented ways. With Drupal 8 and core REST support articulating an API-first vision for the decoupled future, Drupal is eminently well-prepared to back a bevy of applications with divergent approaches. There's just one problem: non-Drupal developers don't know Drupal.
That's where Waterwheel comes in. Waterwheel is an emerging ecosystem of software development kits (SDKs) built by the Drupal community which ease and accelerate development of applications in other technologies. If you will momentarily forgive the flawed metaphor, Waterwheel helps non-PHP and non-Drupal developers "speak" Drupal.
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.
Progressive decoupling, a concept outlined last year in Dries Buytaert’s first post about decoupled Drupal, is a compelling approach to building Drupal's front end where content editors, site assemblers, and front-end developers maintain contiguous experiences. For content editors and site assemblers, progressive decoupling allows for contextualized interfaces, content workflow, site preview, and other features to remain usable and integrated with Drupal as a whole.
At ClikFocus, we have been following and playing with Drupal 8 for more than a year.
Welcome to Post #2 in my series about debugging in Drupal 8.
Drupal 8 is a great platform to work with not only because it is so multilingual capable out-of-the-box, but also because you can easily expand while maintaining the translatability of your data. Drupal 8’s multilingual core offers a robust multilingual foundation, making the integration process much more seamless.
The majority of Drupal 8's APIs are designed to support multilingual by default and make sane assumptions about common scenarios. As a result, there are several important things to keep in mind to build the best integration possible.
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.
Composer, Drush, Git, and Configuration Management all work together to make the Drupal 8 site development and management process faster, more efficient, and less error prone. With the right knowledge of these tools, site-building and management can become a lot simpler.
This webinar will cover the advanced site-building tools and techniques available to Drupal 8 site-builders. We’ll focus on how to build and maintain a site with Composer, as well as how to use Configuration Management to push changes from a local environment to a production one. Other topics will include:
Welcome to my series of blogs about debugging in Drupal 8.
The reason why I decided to create this series is that a lot of Drupalists use ”legacy” ways of non-interactive debugging based on php-native commands like
debug_print_backtrace() or commands provided by contributed modules or themes like
dump() inside of twig templates.
tl;dr: Acquia Pipelines lets you automate building, testing, and deploying sites on Acquia Cloud using tools like Composer, Sass, and Behat.
The Drupal community hit a huge milestone with the release of Drupal 8.0. One of the biggest changes is that this version can now significantly improve with each feature release twice a year under the new “semantic versioning” system. With Drupal 8.2, scheduled to release in October, comes some exciting new additions.
In this webinar, Angie “webchick” Byron and Gábor Hojtsy will provide an overview and status update on the Drupal 8 strategic initiatives announced at DrupalCon New Orleans. Topics will include: