Decoupled applications are increasing in popularity as brand experiences continue to move beyond the traditional website. Although your content management system (CMS) might house your content alongside Drupal, it doesn’t just stay put. APIs are making calls to extend that content to things like digital signage, kiosks, mobile … really, the sky’s the limit (as long as there’s an API).
Decoupled Drupal seems to be taking the world by storm. I'm currently in Sydney, and everyone I talked to so far, including the attendees at the Sydney Drupal User Group, is looking into decoupled Drupal. Digital agencies are experimenting with it on more projects, and there is even a new Decoupled Dev Days conference dedicated to the topic.
In this article we’ll discuss the three main areas that needed to be addressed during the build of POWDR’s front end architecture: Routing & Syncing with the API, Component Driven Content, and the Build Process & Tools.
The mere mention of website templates makes some clients bristle. Nobody likes being told they have to conform to a set of rules they feel weren’t written with them in mind. They also believe that their site will look like everyone else’s and not meet their unique needs.
Let’s start by dispelling that myth: that using templates means your site will look like everyone else’s.
When Acquia-related developer content starts piling up around the Web, it's time for an Acquia Dev Scan.
In this two-part series of blog posts, I'm going to show you how we built a Drupal 8 photo gallery site, integrated with Amazon S3, Rekognition, and Lambda to automatically detect faces (allowing u