Even a solution which is not “the default one” gets a massive amount of usage, testing and support. This is another example of how mature Drupal is. It is thoroughly tested by the community. The module is used by over 1000 websites. The GraphQL module from contrib allows you to expose graphql schemas from Drupal. It is worth mentioning that the JSON:API provided by Drupal strictly follows the JSON:API specification. Thanks to this, any developer familiar with the standard can very quickly start working with the API without having to learn a lot of Drupal. Your development team will be able to tailor Drupal to your needs. These both are great examples of how much power the developers have over how they want the APIs to operate. The best example is the JSON:API extras module and the services module. Thanks to deep integration, the REST APIs are extendable and the way they work can be altered. You can create your own modules and they will work the same way for the headless part of the CMS and for the frontend part.All modules which extend Drupal, will work with services (if they are applicable of course).
The fine-grained permissions mechanisms, the workflows, relations, processes etc are executed in just the same way if you request data via API or try to access it via the frontend.
HEADLESS DRUPAL BENEFITS FULL
They receive the full support of the core project team. The Services and JSON:API modules are now in Drupal core. One which has a clear roadmap of development and will be still relevant and supported in years to come.ĭrupal has started the API first initiative years ago and the community was working very hard to get it done. If you intend to invest in a headless CMS that will power your websites for the foreseeable future, you have to select a solution that is stable and solid. Drupal is mature and is a fully ready headless CMS If I were to recommend the options, I would suggest going with Drupal most of the time. It might be difficult to drill down and make the right decision. These are both - open source and proprietary solutions or mixtures of both worlds.Īs a product owner, you have a plethora of options to choose from.
New entrants to the market, which are focusing only on providing the headless version.Wordpress followed along with making the REST API available. This happened with Drupal API first initiative and inclusion of JSON:API and services modules into Drupal core. The existing CMSes are adopting to the headless approach.Content now has to be distributed via all the channels in which Drupal is present.īoth these movements are helping the headless CMSes thrive. The publish once, push everywhere idea which is adopted along with the rise of the Omnichannel brand presence and the advent of Digital Experience Platforms.React, Angular and Vue are great in building these, but they require a backend for content storage. The emergence of javascript frameworks which allow for the creation of superb user experiences.The headless CMSes space is exploding in recent years. Today I want to focus on why you should really consider Drupal if you need a headless CMS. I discussed the pros and cons of building a headless and listed some considerations you should take into account when deciding whether headless is right for you. I recently wrote an extensive article about a headless CMS.
0 kommentar(er)
