The truth is: innovation happens at the edges and numerous valuable contributions often come from those whose work goes unrecognized at the edges of the community.

Read more about our journey from Drupal Console to Drupal Decoupled in our latest blog post: octahedroid.com/blog/drupal-...

But one thing stands out every time: each innovation came from the periphery, not from the center.

They came from practitioners working directly with clients and solving immediate problems, and not from those setting the roadmap.

When we developed Decoupled Preview Iframe, it was because content editors deserved better experiences in headless implementations.

The same is happening now with Drupal Decoupled, which is helping to build faster and smarter headless CMS in the ecosystem, without the usual hurdles it implies.

This isn't new. Looking at our journey over the past decade reveals a pattern. Just take a look at the timeline below.

When we created Drupal Console, it was because developers needed better tools for module development.

When we built GraphQL Compose, it was because we needed more flexible API.

We’re continuing the conversation on March 6th in our upcoming webinar, where we’ll address common misconceptions about Drupal Decoupled and how to implement it effectively.

📅 You can register here:
octahedroid.com/webinar/6-dr...