Why Drupal is optimal for building developer portals.The introduction section of this article is conceptual, so it’s also optimal for readers who aren’t familiar with Content Management Systems (CMS) and developer portals: Part 1: Developer portal – technology and community Overview of the journey you’re about to take The third part is mainly for Drupal developers, and contains tips & tricks and best practices that may help them using JSON:API. We recommend the first two parts of this article to any reader interested in the topic.

To do this, we first need to familiarize ourselves with some basic concepts, then we have to compare the advantages and disadvantages of the different architectures. Its purpose is to present the trends that have become popular in the world of Content Management Systems (CMS) and to contextualize these with the needs of developers, administrators, and users. This study reviews the articles already published by the Pronovix team on the subject, takes them as a basis, but also looks further. The design, the service, and the content must form one organic unit and serve everyone who is part of the developer portal’s ecosystem, be it a developer, a designer, a content editor, or an API consumer. Tradition and progress: just as in the case of architecture, but in the world of developer portals as well, it is important not to consider only the technological advantages when making a decision. By: Ádám Balogh and co-author Ákos Seress (technical advisor, Front-end developer)

Headless drupal angular