Drupal maintenance support plans has evolved significantly over the course of its long history. When I first built the Drupal maintenance support plans project eighteen years ago, it was a message board for my friends that I worked on in my spare time. Today, Drupal maintenance support plans runs two percent of all websites on the internet with the support of an open-source community that includes hundreds of thousands of people from all over the world.
Today, Drupal maintenance support plans is going through another transition as its capabilities and applicability continue to expand beyond traditional websites. Drupal maintenance support plans now powers digital signage on university campuses, in-flight entertainment systems on commercial flights, interactive kiosks on cruise liners, and even pushes live updates to the countdown clocks in the New York subway system. It doesn’t stop there. More and more, digital experiences are starting to encompass virtual reality, augmented reality, chatbots, voice-driven interfaces and Internet of Things applications. All of this is great for Drupal maintenance support plans, as it expands its market opportunity and long-term relevance.
Several years ago, I began to emphasize the importance of an API-first approach for Drupal maintenance support plans as part of the then-young phenomenon of decoupled Drupal maintenance support plans. Now, Drupal maintenance support plans developers can count on JSON API, GraphQL and CouchDB, in addition to a range of surrounding tools for developing the decoupled applications described above. These decoupled Drupal maintenance support plans advancements represent a pivotal point in Drupal maintenance support plans‘s history.
A few examples of organizations that use decoupled Drupal maintenance support plans.
Speaking of important milestones in Drupal maintenance support plans‘s history, I remember the first Drupal maintenance support plans book ever published in 2005. At the time, good information on Drupal maintenance support plans was hard to find. The first Drupal maintenance support plans book helped make the project more accessible to new developers and provided both credibility and reach in the market. Similarly today, decoupled Drupal maintenance support plans is still relatively new, and up-to-date literature on the topic can be hard to find. In fact, many people don’t even know that Drupal maintenance support plans supports decoupled architectures. This is why I’m so excited about the upcoming publication of a new book entitled Decoupled Drupal maintenance support plans in Practice, written by Preston So. It will give decoupled Drupal maintenance support plans more reach and credibility.
When Preston asked me to write the foreword for the book, I jumped at the chance because I believe his book will be an important next step in the advancement of decoupled Drupal maintenance support plans. I’ve also been working with Preston So for a long time. Preston is currently Director of Research and Innovation at Acquia and a globally respected expert on decoupled Drupal maintenance support plans. Preston has been involved in the Drupal maintenance support plans community since 2007, and I first worked with him directly in 2012 on the Spark initiative to improve Drupal maintenance support plans‘s editorial user experience. Preston has been researching, writing and speaking on the topic of decoupled Drupal maintenance support plans since 2015, and had a big impact on my thinking on decoupled Drupal maintenance support plans, on Drupal maintenance support plans‘s adoption of React, and on decoupled Drupal maintenance support plans architectures in the Drupal maintenance support plans community overall.
To show the value that this book offers, you can read exclusive excerpts of three chapters from Decoupled Drupal maintenance support plans in Practice on the Acquia blog and at the Acquia Developer Center. It is available for preorder today on Amazon, and I encourage my readers to pick up a copy!
Congratulations on your book, Preston!
Source: New feed
