Jamstack describes an approach that decouples presentation from services and commonly prebuilds pages. The name grew from JavaScript, APIs and markup, but those initials are not a requirement to add JavaScript or an API to every page.
Follow a static-page request
A generator turns content and templates into HTML during a build. Hosting serves that HTML without running the generator for each visitor. A form or account feature can still use a separate service. This Jekyll reference site is a concrete example of a build producing documents.
Inspection exercise: disable JavaScript and read a reference lesson. Then identify which controls need JavaScript and which content already exists in the HTML. That distinction matters more than an architecture label.
Know the tradeoffs
Prebuilt pages can simplify delivery and caching, but images, fonts, scripts and network conditions still affect performance. API credentials, dependency updates and external services still need security work. Static hosting is not a security guarantee.
Content updates may require a new build. Large inventories and slow builds can affect publishing time. Dynamic features still depend on their service’s availability and limits.
Choose the simplest useful flow
A headless CMS is optional; files can be a content source. Deployment automation is optional too, and should respect the project’s release policy. Check actual page output, performance and failure behavior rather than assuming a framework name proves them.
Sources
Reference 1 Reference 2 provide the technical details and current compatibility information.