Topic Proposal - Headless WordPress with JAMstack Sites

Details

• Topic description: An introduction to using WordPress as a headless CMS
  to power JAMstack sites. Covers the concept of decoupled architecture,
  how WordPress REST API exposes content, and how a static
  site generator (e.g. Next.js or Astro) consumes that content to build
  a fast, modern frontend.

• Audience: Developer

• Learning objectives:

  1. Explain what "headless WordPress" means and how it differs from a
     traditional coupled WordPress setup.
  2. Identify use cases where a headless/JAMstack approach is appropriate.
  3. Configure WordPress to expose content via the REST API or WPGraphQL.
  4. Query WordPress content from a frontend framework (e.g. Next.js)
     during static site generation.
  5. Understand the trade-offs: lost features (theme layer, plugins that
     render HTML), gained benefits (performance, frontend flexibility).

• Content type: Course

• Will you be creating this content? Yes

Related Resources

• WordPress REST API Handbook: https://developer.wordpress.org/rest-api/
• Next.js WordPress example (Vercel):
  https://github.com/vercel/next.js/tree/canary/examples/cms-wordpress
• Astro + WordPress guide:
  https://docs.astro.build/en/guides/cms/wordpress/
• "JAMstack" overview: https://jamstack.org/what-is-jamstack/
• Existing Learn WP content on REST API (for continuity):
  https://learn.wordpress.org

Next steps for SMEs

Please follow the team handbook "Vetting topic ideas"
(https://make.wordpress.org/training/handbook/training-team-how-to-guides/vetting-topic-ideas/)
to vet this topic.

Start with the team handbook’s “Vetting topic ideas” guide, then review the linked WordPress REST API, Next.js, Astro, and JAMstack resources. Use the stated audience and learning objectives to assess the proposed course. Done means the topic has been vetted and its planned content addresses the listed objectives and trade-offs.