In a nutshell, Jamstack works by decoupling front and backend systems, allowing data to be incorporated as required and subsequently displayed in whatever User Interface (UI) format is optimal. Jamstack provides developers with greater flexibility and customisation, by making the need for business logic redundant, allowing for third parties and custom logic to be incorporated through the use of APIs.
Below are some explanations of key terminology:
Decoupling separates the system and service required to operate a site, whether that’s between the frontend and database, or backend and CMS. A clean separation between the two allows them to be operated and modified independently, providing greater customisation and flexibility.
Developers can then employ specialist third party applications, incorporating services as they see fit rather than having to rely on homegrown functionality.
With Headless CMS the frontend and the backend systems are completely separate. Imagine the frontend is the “head” and backend is the “body” - and that’s where the “headless” term originated.
With headless CMS data can be stored and sorted separately, without needing to know where or how it will be displayed. By alleviating the dependency on display concerns, developers have more freedom to focus on UI optimisation.
Application Programming Interface, or APIs, are effectively the middle man for Jamstack sites. They function as the connective tissue between applications, allowing them to talk to each other.
Jamstack improves customisation with the ability to incorporate third-party applications and custom logic through the use of APIs. APIs allow developers to create more complex applications without having to worry about developing the domain themselves.
Those are three of the crucial components of Jamstack, but there are many more listed in this glossary by Jamstack itself.