Topic Proposal - Headless WordPress with JAMstack Sites

[leen-neel]

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.

[leen-neel]

Module Structure (tentative):

Module 1: What is Headless WordPress?
Module 2: WordPress as a Content Backend
Module 3: Setting Up Your JAMstack Frontend
Module 4: Fetching WordPress Content
Module 5: Handling Media and Assets
Module 6: Deployment and the Decoupled Stack
Module 7: Trade-offs and Real-World Considerations

Sharing a tentative module structure for visibility. Happy to adjust based on team feedback:

[rjekic]

@leen-neel

Great initiative! So, just to make sure we are on the same page - this is a proposal for the single lesson? Since we are using Modules for lesson separation in the course. So, all the proposed modules should be sections inside one lesson?

Thank you!
cc @sumitsinghwp @devmuhib009 @jonathanbossenger

[leen-neel]

@rjekic yes
I will split the lesson up into sections to cover the topics
Maybe I can put a "Menu" at the top so that people can refer to individual modules

[jonathanbossenger]

If it helps, a Learn WordPress course can include a series of individual lessons, or one or more groups of one or more lessons, grouped by modules.

Course -> Lessons

or

Course -> Module(s) -> Lesson(s)

So if each of the Modules you've listed above are the lessons, then you can go with the top structure. However if each module will include more than one lesson, you can go with the bottom structure.

[rjekic]

@leen-neel

Do you have any idea about the size of the content? For instance, compared to the blog article found somewhere online, do you think it can fit into one article? You don't need to specify it exactly, just a rough estimation would be enough to lead us to the next step - to decide how to organize the content.

Thank you @jonathanbossenger for stepping in to help us - your knowledge and experience in the content creation is invaluable for this project.

[leen-neel]

@jonathanbossenger hmm seems like I need to do it in a course structure then. Thanks you so much for the info!

@rjekic After mapping out the module structure, this is definitely course-sized content. Each module has enough hands-on depth to warrant its own lesson. Module 4 alone (fetching posts, slug routing, pagination, handling embedded HTML) could easily run 1500–2000 words with code examples, and Modules 2 and 6 are comparable in scope.

For reference, a typical in-depth tutorial covering just the "fetch content from a headless CMS" part (roughly Modules 3–4 here) already runs 3000 - 4000 words on sites like Smashing Magazine. The full seven-module scope is roughly 3 - 4 times that.

P.S: I've updated the proposal to "Content Type: Course"

Cheers!