> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/sustainability-best-practices/backend/jamstack.md). # JAMstack The adoption of JAMstack architecture, Static Site Generation (SSG), and Content Delivery Network (CDN) distribution stands as a commendable choice for sustainable system design. [JAMstacks](https://jamstack.org/) decoupled approach separates the frontend from the backend, allowing for efficient resource allocation and reduced server-side processing. When combined with Static Site Generation (SSG), which pre-generates static content at build time, this results in decreased server load and faster loading times. CDN distribution further amplifies these benefits by delivering content from geographically distributed edge servers, minimizing data transfer distances and latency. This holistic approach not only optimizes user experiences but also reduces energy consumption by minimizing server processing needs and data transmission over long distances. By prioritizing resource efficiency and performance, **JAMstack**, **Static Site Generation (SSG)**, and **Content Delivery Network (CDN)** distribution align seamlessly with sustainable design principles. They create web systems that operate in an ecologically responsible manner while delivering exceptional user experiences. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.umbraco.com/sustainability-best-practices/backend/jamstack.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.