JAMstack CMSs Have Finally Grown Up!

This article summarizes Brian's Connect.Tech 2019 presentation (slides available for download). It explores the evolution of JAMstack CMSs, focusing on the shift from developer-centric tools to solutions suitable for non-technical content creators.

Developers readily grasp the JAMstack's advantages: speed (static resources served from a CDN), security (no server-side components to compromise), and streamlined development/deployment. However, the content creation workflow presented initial challenges. While traditional CMSs faced developer criticism, early JAMstack solutions often burdened non-technical users.

Initially: A Developer-Focused Ecosystem

Static site generators (Jekyll, Hugo, Gatsby) gained popularity due to developer adoption. These were typically developer-built, maintained, and content-populated projects. As stated in a 2015 O'Reilly report:

Static site generators are built for developers. Non-developers are unlikely to be comfortable with Markdown, YAML, or JSON—the formats used for content and metadata.

Even by 2017 (O'Reilly book co-authored with Raymond Camden), early tools like Jekyll Admin and Netlify CMS were immature compared to WYSIWYG editors in platforms like WordPress. The editing experience demanded Markdown and other markup language proficiency. This limited mainstream adoption.

The Maturation Phase: Git-Based and API-First CMSs

Over the next few years, two trends transformed the JAMstack landscape: the rise of git-based CMSs and API-first headless CMSs.

Netlify CMS (open-source) exemplifies a git-based approach. Instead of traditional content storage, it provides tools for editing Markdown, YAML, and JSON, committing changes directly to the repository, triggering a site rebuild. Other web-based options like Forestry exist.

API-first CMSs (Contentful, DatoCMS, Sanity) offer a more traditional editing experience, storing content and providing it via API to any frontend. This decoupling works well with JAMstack, separating content management from frontend display. Many integrate with popular static site generators. HeadlessCMS.org offers a comprehensive list of available tools. Bejamas' post provides a detailed comparison of git-based vs. API-first CMSs.

While these improved content creation, the disconnect between backend editing and frontend display remained. The lack of immediate visual feedback, coupled with rebuild times, created an imperfect workflow.

The Future: Frontend Editing and Preview

JAMstack_conf_sf showcased tools bridging this gap. Forestry's TinaCMS (open-source) provides a WYSIWYG frontend editing experience for Gatsby and Next.js sites using git-based CMSs. Stackbit Live (Stackbit, where I'm a Developer Advocate) offers a CMS and static site generator-agnostic solution for on-page editing and previewing.

These advancements demonstrate the viability of "JAMstack headless" as a true alternative to traditional CMSs. The trade-off between developer experience and content editor usability is diminishing. By 2020, JAMstack CMSs had matured significantly. ??‍?

The above is the detailed content of JAMstack CMSs Have Finally Grown Up!. For more information, please follow other related articles on the PHP Chinese website!