Block Theme Cheat Sheet for WordPress 🔗 **Source:** [Block Theme Cheat Sheet for WordPress](https://elliottrichmond.co.uk/block-theme-cheat-sheet-for-wordpress/) > [!note]+ Document Notes > tags: [WordPress, Block Themes, Full Site Editing] > author: elliott richmond > source: elliottrichmond.co.uk > reference: [https://elliottrichmond.co.uk/block-theme-cheat-sheet-for-wordpress/] > date created: 2025-11-15 12:00 > > # 🏷️ Title: Block Theme Cheat Sheet for WordPress > <!-- deep-read:sections start --> ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - Include links cited in or relevant to the article. ## 📝 Summary - What happened: A developer published a curated “Block Theme Cheat Sheet” for WordPress Full Site Editing. - Why it matters: Saves time by centralizing core blocks, patterns/templates, theme.json, and commonly used hooks, plus a troubleshooting log. - Key stakeholders: WordPress theme developers, especially those new to FSE. - Risks and tradeoffs: Not exhaustive; may lag core changes; opinionated curation. - Bottom line: A practical, working reference to keep open while building FSE themes. ## 📖 Main Content - Core arguments: Centralized reference reduces context switching and repeated Googling; curated “only what’s useful in practice.” - Context/definitions: - Full Site Editing (FSE): Build themes using blocks across the entire site (templates, parts, styles). - theme.json: Declarative config for settings/styles. - Hooks: Actions/filters to modify behavior. - Uncertainties: Coverage breadth, update cadence, and version specificity are not detailed. ### 🗒️ Notes - “You’re constantly looking stuff up” in FSE development; this is a quick-reference, not a tutorial. - Includes: - Core blocks list with categories/uses. - Patterns, templates, template parts: types, values, structure. - theme.json: settings and styles reference. - Actions/filters: a practical subset “I actually use.” - Troubleshooting tab: running log of real issues and fixes to help “future self.” ## 📚 References - WordPress Block Editor Handbook: https://developer.wordpress.org/block-editor/ - Core blocks reference: https://wordpress.org/documentation/article/blocks/ - theme.json reference: https://developer.wordpress.org/block-editor/reference-guides/theme-json/ - Templates and template parts: https://developer.wordpress.org/themes/templates/ - Plugin API (actions/filters): https://developer.wordpress.org/plugins/hooks/ ## 🗣️ Paraphrase - Paragraph A: Building FSE themes requires frequent lookups; a curated cheat sheet prevents reinventing solutions. - Paragraph B: Aimed at hands-on builders who need fast, reliable reference points rather than full tutorials. ## 📰 Newsletter - Level up your FSE workflow: a practical Block Theme Cheat Sheet compiles core blocks, template structures, theme.json options, and go-to hooks—plus a living troubleshooting log. Ideal to keep open while you build. Brush up with the official theme.json guide and core blocks catalog, then dive back into shipping your next theme. ## ✅ Action Items #### DevRel - Publish demos showing cheat sheet-driven workflows; measure time-to-implement reductions. - Offer office hours for FSE theming; collect FAQ to refine the sheet. - Create quickstarts/templates aligned to entries (blocks, parts, theme.json). #### OSPO - Establish license notice and update cadence if shared internally. - Add hook usage guidelines to engineering standards. #### Community - Host “troubleshooting clinics” to crowdsource recurring FSE issues. - Pair newcomers with mentors to extend the cheat sheet. #### WordPress - Documentation: cross-link cheat sheet topics to DevHub/HelpHub gaps. - Themes: create test matrices for common template parts and theme.json settings. - Accessibility: add checks for patterns/templates. #### The WPOCC - Fund microgrants to maintain up-to-date FSE references. - Run documentation sprints focusing on theme.json and hooks. ### FAIR - Keep provenance/version notes for entries; note WP version compatibility. - Publish governance for edits and sunset policies. ## 🧪 Hypotheses - A curated FSE cheat sheet reduces developer context-switching by ≥25%. - Logging recurring issues halves repeat debugging time over 3 months. - A minimal set of hooks covers ≥80% of common theme customizations. - New FSE developers ship first theme ≥30% faster using the sheet. ### 📊 Methodology - Time-and-motion study comparing with/without cheat sheet. - Issue tracker analysis for repeated bugs and resolution time. - Survey developers on perceived usefulness and coverage. - Versioned A/B usage across project teams. ### ❓ Questions - Which WP versions and block APIs does the sheet target? - How are deprecations and new blocks tracked? - What taxonomy best organizes troubleshooting entries? ### 🔮 Future Research - Map theme.json options to visual outcomes with examples. - Build a searchable, version-aware index of hooks used in themes. ### 💡 Implications - Practice: Faster theming, fewer tabs, more consistency. - Policy: Encourage shared, versioned references in teams. - Education: Use as scaffold in FSE workshops. ### 🧠 Learning Styles Assessment - Reading level: ~8–9th grade (FKGL ≈ 8–9). #### 👀 Visual learners - Present: Structured lists; could add screenshots/diagrams. - Improve: Architecture diagrams of template hierarchy. #### 🔊 Aural learners - Improve: 3–5 minute audio summary. #### 🗣️ Verbal learners - Present: Plain-language descriptions. - Improve: Glossary of theme.json keys. #### 🧩 Kinesthetic learners - Present: Apply while building. - Improve: Step-by-step mini-labs. #### 🧠 Logical learners - Present: Categorized references. - Improve: Decision trees for choosing blocks/hooks. #### 🧑‍🤝‍🧑 Social learners - Improve: Peer review prompts and discussion threads. #### 🧘‍♀️ Solitary learners - Present: Self-paced reference. - Improve: Reflection checklists. #### 🌿 Naturalistic learners - N/A; not relevant. ### 📊 Accessibility Assessment #### Screen reader semantics - Improve: Ensure headings/landmarks and alt text on any images. #### Keyboard navigation - Improve: Visible focus and logical order. #### Contrast and readability - Improve: Confirm ≥4.5:1 and readable line-height. #### Text resizing and reflow - Improve: Check 200% zoom, reduce-motion support. #### Media and captions - Improve: Provide captions/transcripts if media added. #### Forms and interactions - N/A unless interactive. #### Standards reference - Map to WCAG 2.2 AA. ### 🌍 DEIB Assessment - Inclusive language: Generally neutral; define jargon. - Improve: Multilingual links; global examples; plain-language summaries. ### ✅ Logical Validity #### Strong reasoning - Inductive: Curated items reflect “what’s useful in practice.” #### Fallacies - None apparent; avoids overclaiming comprehensiveness. #### Tone of voice - Practical, collegial, “for working developers.” ### 🛡️ DARVO Analysis - Not applicable; no conflict framing detected. ## 🎯 Conclusion - Bottom line: A curated, working FSE cheat sheet centralizes high-signal references and a troubleshooting log to speed theme development. - Next steps: Keep it open while building, contribute recurring issues, and align it with official docs and WP version notes. ## 🧱 Refactor Appendix (append after 🎯 Conclusion) ### 📚 Literature Split Pad - Purpose: Stage Konik CEE units that become per-source Literature notes. - Split level: H3. - Include verbatim quotes under 25 words and a [view highlight] link. ### [H1] Centralized FSE references speed development > [!quote] [Block Theme Cheat Sheet for WordPress](https://elliottrichmond.co.uk/block-theme-cheat-sheet-for-wordpress/) by [[elliott richmond]] via [[elliottrichmond.co.uk]]. Published 2025-11-15. Accessed 2025-11-15. > “This isn’t some comprehensive guide… It’s a quick reference.” Two lines: reduces context switching; practical building aid. [view highlight](https://elliottrichmond.co.uk/block-theme-cheat-sheet-for-wordpress/#H1) #xref #articleseed ID:rw_[MISSING] ### [H2] Troubleshooting logs prevent repeat mistakes > [!quote] [Block Theme Cheat Sheet for WordPress](https://elliottrichmond.co.uk/block-theme-cheat-sheet-for-wordpress/) > “My past self helps out my future self.” Two lines: captures non-obvious fixes; shortens future debugging. [view highlight](https://elliottrichmond.co.uk/block-theme-cheat-sheet-for-wordpress/#H2) #xref ID:rw_[MISSING] --- ### 🔖 Atomic Split Pad (Zettel Candidates) #### [Z1] Troubleshooting logs accelerate FSE iteration - Holds when issues recur across themes. - Pointer: article troubleshooting section. - Links: [[FSE]] [[Developer-Experience]] #### [Z2] Curated hooks cover most theme needs - Scope: typical block theme customizations. - Pointer: “Actions and filters” section. - Links: [[Hooks]] [[WordPress-Themes]] --- ### ✏️ Fleeting Queue (Extract by Selection) - [F1] Add version notes per WP release — context/https://elliottrichmond.co.uk/block-theme-cheat-sheet-for-wordpress/ #fleeting #inbox - [F2] Map theme.json keys to UI screenshots — context/https://developer.wordpress.org/block-editor/reference-guides/theme-json/ #fleeting #inbox - [F3] Build decision tree for template parts — context/https://developer.wordpress.org/themes/templates/ #fleeting #inbox --- <!-- deep-read:sections end -->