JAMstack is revolutionising the way we think about workflow by providing a simpler developer experience, better performance, lower cost and greater scalability.
This simple guide will help you understand why it exists and how to get started.
— Mathias Biilmann (CEO & Co-founder of Netlify).
Websites are served as static HTML files. These can be generated from source files, such as Markdown, using a Static Site Generator.
Here are the main benefits provided by the JAMstack
Serve pre-built markup and assets over a CDN
No need to worry about server or database vulnerabilities
Hosting of static files are cheap or even free
Front end developers can focus on the front end, without being tied to a monolithic architecture. This usually means quicker and more focused development
If your product suddenly goes viral and has many active users, the CDN seamlessly compensates
The following tips will help you leverage the best out of the stack.
Since all the markup and assets are pre-built, they can be served via CDN. This provides better performance and easier scalability.Learn more
Each deploy is a full snapshot of the site. This helps guarantee a consistent version of the site globally.Learn more
Once your build is uploaded, the CDN invalidates its cache. This means that your new build is live in an instant.Learn more
Your codebase lives in Version Control System, such as Git. The main benefits are: change history of every file, collaborators and traceability.Learn more
Your server is notified when a new build is required, typically via webhooks. Server builds the project, updates the CDNs and the site is live.Learn more
Here's how an ideal JAMstack workflow would look like
A brief history of stack shows its growth in popularity
However you decide to generate your HTML assets is up to you. The three most common approaches are:
Simple and effective method of writing HTML, it's ideal for super simple pages.
Most JAMstack sites are powered by a static site generator. There's no enforcement on which SSG you decide to use.
Most frameworks don't output static HTML files, however it is possible to do that but it requires more tooling experience and maintenance.
Your built site needs to be hosted somewhere. There are great services that provides this for free and with ease.
JAMstack websites don't have to be static. There are great services available to help bring some dynamic data to your product.
As you add features to your site, you may want to store user profiles, shopping cart data, game levels, or other dynamic data. Get started for free with FaunaDB Serverless GraphQL
Many JAMstack products have dynamic comment sections. These are typically used on blogs
A great way to interact with your audience
Setting up an online store on the JAMstack has never been easier
Rely on third party services to integrate a search functionality
JAMstack sites can also be controlled via a Content Management System, these are typically known as Headless CMS. Once a change in the CMS is made, a new build of your site will be triggered and then deployed as static assets.
Here's a list of hand-picked JAMstack resources ranging from learning materials to third party services.
The goal of this project is to gather the concept of JAMstack in a straight-forward way to encourage other developers to adopt the workflow.