Today we released a new series, Decoupled Drupal. This series walks through the basic considerations and planning that goes into deciding whether or not a decoupled approach is right for you.
Assuming you've decided to decouple, we'll then talk about what considerations should go into building your API. We'll also cover what exactly we mean when we say REST. Having undertaken the work of designing our API, we'll dig into the API Blueprint specification to see how easy it is to document and test our API.
We will then take a look at multiple options for creating this Drupal-powered API. We'll write some custom code, as well as the Views Datasource and Services modules. The next lesson covers the RESTful module, my preferred method of exposing data in Drupal 7. With Drupal 8's recent release, we'll also take a look at the REST server included in core.
Introducing this Node.js server impacts how you go about hosting your site. The final tutorial in this series takes a look at some of those implications and considerations.
Tutorials in this series
- Decoupling Explained (FREE)
- Is Decoupling the Right Choice?
- Building a Solid API
- API Documentation and Testing
- Exposing an API with Drupal
- Explore the RESTful module
- Exposing Your API in Drupal 8 (FREE)
- Building a Simple Decoupled Front-End
- Replicate Complex Interaction
- SEO with Server-Side Rendering
- Hosting Implications and Considerations
Our next series, coming out in December, will take a look at the Configuration Management System in Drupal 8. We're also hard at work on a comprehensive series about Theming in Drupal 8.