What is the JAMstack?
The JAMstack isn’t a specific set of tools, but a new, modern way of building websites & apps. Where does “J-A-M” come from, you may ask? From these three core concepts:
JavaScript: Any dynamic programming during the request/response cycle is handled by JavaScript, running entirely on the client.
APIs: All server-side functions or database actions are abstracted into reusable APIs, accessed over HTTPS with JS. Be it SaaS, third-party services or custom-built.
Markup: Templated markup should be prebuilt at build time, usually using a site generator for content sites, or a build tool for web apps.
Here is the
- Github Repository redwoodjs/redwood
- Official Website link
Latest Release : v0.2.5
A Redwood application is split into two parts: a frontend and a backend. This is represented as two node projects within a single monorepo(is a software development strategy where code for many projects is stored in the same repository.).
The frontend project is called web and the backend project is called api. For clarity, we will refer to these in prose as "sides", i.e. the "web side" and the "api side".
Web Side : The web side is built with React. Redwood's router makes it simple to map URL paths to React "Page" components (and automatically code-split your app on each route). Pages may contain a "Layout" component to wrap content.
Api side : The api side is an implementation of a GraphQL API. Your business logic is organized into "services" that represent their own internal API and can be called both from external GraphQL requests and other internal services.