Whether you want to implement a classic monolithic Drupal or simply publish content via an interface – or both –, it makes sense to form a basis for decision-making first. To decouple or not?Ĭoupled, progressively decoupled or fully decoupled? Lately, this question has been repeatedly raised. Complex translation workflows or integrated e-commerce applications can be optimally built upon. The structured collection of content through an appropriate editorial interface with finely granular permissions and adaptive workflows form the heart of most modern Drupal websites. This allows the website to evolve into a landscape of web applications without the core system having to abandon its primary tasks. ![]() New requirements for the integration of a PWA, connection of a React Native App or the delivery of web content to other third-party systems can be complemented by Drupal's modular interface capabilities. The web solution can evolve dynamically, especially with the gradual expandability of Drupal. In fully decoupled operation, one or more frontends consume the data from Drupal to display them in a stand-alone web site or application. ![]() The specific page areas then operate like a decoupled app which accesses the backend via the interface. Using the integrated API interfaces such as REST, JSON:API and GraphQL, parts of the Drupal web solution can be “progressively decoupled”. Operated as a classic monolithic CMS, backend and frontend are closely interlinked and enable the efficient implementation of web projects. ![]() Drupal 8 offers various interfaces to perform decoupling in several stages.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |