For many organisations Drupal 8 websites evolve over time from a traditional coupled HTML front-end into much more. As the API first initiative is underway unlocking the potential of our content, existing Drupal 8 sites can be progressively decoupled or used as content hubs that power other digital experiences. What does this mean for established websites that are undergoing such transitions? What new considerations do we as developers and content authors need to make during this transition.
In this session I will be covering:
- Auditing the security of your Drupal 8 code and configuration for REST readiness.
- Being aware of API backwards compatibility when updating content models.
- Strategies for including API endpoints as part of your project test suite.
- Effective configuration for users, roles and permissions.
The content in this talk will be broadly applicable to different API specs such as core REST, JSON API and beyond.