Home » Guides » Wordpress » Wordpress Fse Index
📌 Pin 🔗 Copy Link 📋 Copy Markdown ⬇️ Download
2 min read

This is a great way to "program" the AI to act as a structured technical writer. Since you’re speed-running, this index focuses on the mechanical reality of FSE (how the JSON actually compiles) rather than just the "click-here" UI instructions.

1. The FSE Master Index (Initial Topics)

This index covers the "gotchas" we just fought through, plus the architectural layers of a modern block theme.

  • 01-Foundations: The Theme.json Schema
    • Versions and structural hierarchy (Settings vs. Styles).
    • The appearanceTools flag: What it unlocks automatically.
  • 02-Registration: The Preset Engine
    • Color Palettes: From Slugs to --wp--preset--color--[slug].
    • Typography: Fluid sizing and the "kebab-case" sanitization (The h-2 phenomenon).
    • Spacing: Creating your own custom spacing scale and steps.
  • 03-Global Styles: Elements & Specificity
    • Targeting HTML elements globally (h1-h6, links, buttons).
    • How styles.elements interacts with the browser's User Agent stylesheet.
  • 04-Block Mastery: Component-Level Styles
    • Nesting elements inside core/ blocks.
    • Targeting block variations and custom CSS classes within theme.json.
  • 05-Template Hierarchy in FSE
    • templates/ vs parts/: When to use which.
    • Mapping customTemplates in JSON to actual .html files.
  • 06-The Loop & Query Loop Block
    • Customizing the post template without PHP.
    • Passing context between blocks.
  • 07-Advanced: Theme.json Interactivity & Variations
    • Style Variations (Multiple theme.json flavors).
    • Registering block patterns as "sections."

2. The Setup Prompt

Copy and paste this to your code assist instance. It is designed to set the "Rules of Engagement" for your documentation project.

Prompt:

I am building a comprehensive WordPress FSE Guide. Your task is to act as a technical documentarian.

Step 1: Read the existing project structure and the file wordpress-fse-index.md.

Step 2: Generate a "Roadmap" of individual Markdown files we need to create based on the initial index provided.

Step 3: Formatting Requirements: Every file you generate must use our specific YAML frontmatter. Use the following format as a strict template:

tags:

  • wordpress
  • fse

  • [additional-relevant-tags] title: [Descriptive Title]

Step 4: Operational Loop: Do not write all the files at once. After you provide the roadmap and I approve it, you will suggest the first file to write. For every file, ensure you explain the "Why" (the underlying WordPress logic) and the "How" (the JSON/HTML code).

Context Note: We recently learned that WordPress sanitizes slugs (e.g., h2 becomes --wp--preset--font-size--h-2). Ensure the guide covers these "sanitization quirks" so users don't face "variable not set" errors.

Please confirm you have read the index and provide the expanded roadmap now.

Next Step: Once you drop that prompt in, I can help you refine the technical "Why" for any of those specific chapters as the AI starts drafting them. Ready to start with Chapter 1?

Created: March 19, 2026 • Last Modified: March 19, 2026