Only the raw data needs to be received and processed. Because of this, the construction of mobile apps on various platforms is now possible. The programming language is no longer defined. The frontend development view also offers benefits: As a web designer, you’re no longer bound to the requirements of a content management system with a headless CMS. This can be read by any frontend you want, regardless of what technology it’s programmed with. The REST-API only provides the data (in the form of JSON). In a headless CMS, it doesn’t matter what kind of platform is given for the output of content. The described separation is useful from two perspectives: From the point of view of backend development, it helps the desire to spread content through more than one output. This makes REST architecture perfect for a headless CMS API. Resources given with links: Within REST, objects are linked with one another using hyperlinks for simple navigation.īy adhering to these architectural principles, the communication between server/API and various clients can work flawlessly.Messages are self-explanatory: Each message on the server is self-contained and doesn’t refer to any previous ones.Clients request the element in the desired format for content negotiation. With REST, the URI/URL doesn’t refer to a resource in a particular format, but instead to the element itself.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |