Content Guidelines: A Gutenberg Experiment  🔗 **Source:** [Content Guidelines: A Gutenberg Experiment](https://make.wordpress.org/ai/2026/02/03/content-guidelines-a-gutenberg-experiment/) > [!note]+ Document Notes > tags: #wordpress #gutenberg #ai #content-guidelines #experiment > author: James LePage > source: WordPress AI Team > reference: https://make.wordpress.org/ai/2026/02/03/content-guidelines-a-gutenberg-experiment/ > date created: 2026-02-03 22:33 > > # 🏷️ Title: Content Guidelines: A Gutenberg Experiment > <!-- deep-read:sections start --> ## 🧰 Action Inbox - [H1] Track the initial PR (#75164) and provide feedback on schema design #gutenberg - [H2] Share practical use cases and content standards in tracking issue (#75171) #feedback - [H3] Test early versions for AI assistant integration workflows #ai-integration ## 🧭 Table of Contents - [[#📝 Summary]] - [[#📖 Main Content]] - [[#🗒️ Notes]] - [[#📚 References]] - [[#🗣️ Paraphrase]] - [[#📰 Newsletter]] - [[#✅ Action Items]] - [[#🧪 Hypotheses]] - [[#📊 Methodology]] - [[#❓ Questions]] - [[#🔮 Future Research]] - [[#💡 Implications]] - [[#🧠 Learning Styles Assessment]] - [[#📊 Accessibility Assessment]] - [[#🌍 DEIB Assessment]] - [[#✅ Logical Validity]] - [[#🛡️ DARVO Analysis]] - [[#🎯 Conclusion]] ### 🔗 References - [Gutenberg PR #75164](https://github.com/WordPress/gutenberg/pull/75164) - [Tracking Issue #75171](https://github.com/WordPress/gutenberg/issues/75171) ## 📝 Summary - What happened: WordPress AI Team is launching a Gutenberg experiment to create Content Guidelines - a unified system for storing site-wide content standards and context within WordPress - Why it matters: Most sites have scattered content standards across documents, PDFs, and institutional knowledge that are hard to find during writing and impossible for tools to apply consistently - Key stakeholders: Site owners, content creators, plugin developers, hosting providers, AI tool developers - Risks and tradeoffs: New API commitment, potential feature creep, need to balance flexibility with structure - Bottom line: Creates foundation for consistent, AI-steerable content management by centralizing editorial guidelines within WordPress ## 📖 Main Content The WordPress AI Team is proposing Content Guidelines as a Gutenberg experiment to address the scattered nature of content standards across WordPress sites. Currently, editorial guidelines exist in wikis, PDFs, onboarding documents, and tribal knowledge - making them unavailable when writers need them most and impossible for automated tools to reference. The experiment aims to create a first-class location within WordPress for capturing voice and tone, structural rules, image guidance, accessibility expectations, and linking practices. This centralized approach would benefit human editors immediately while establishing the foundation needed for AI-assisted workflows. The initiative fits the Gutenberg experiment model because it intersects multiple editor surfaces, requires ecosystem feedback before API commitment, and establishes new site-level configuration patterns. The team emphasizes this isn't an AI-only feature - AI should depend on it, not the reverse. Key capabilities include global and granular guideline support, revision history, reliable tool retrieval, and import/export functionality. The focus remains on capturing and retrieving guidelines, while AI-driven experiences like generation and enforcement can build on this shared foundation. ## 🗒️ Notes #### [00:00] — [H1] Content Guidelines experiment announced for Gutenberg - Key idea: WordPress AI Team launching unified content standards system within WordPress core - Evidence: "A single place in WordPress to capture site-wide content standards and context" #### [02:15] — [H2] Current content standards are scattered and inaccessible - Key idea: Editorial guidelines exist outside WordPress in documents and institutional knowledge - Evidence: "Those guidelines often live outside WordPress in documents, PDFs, wikis, or institutional knowledge" #### [04:30] — [H3] Gutenberg experiment model de-risks core integration - Key idea: Experiment allows validation before long-term API commitment - Evidence: "It de-risks future AI integrations in Core by establishing the right foundations now" #### [06:45] — [H1] Single source of truth enables consistency across authors - Key idea: Centralized guidelines make standards discoverable and reusable for all tools - Evidence: "A unified store of guidelines makes standards discoverable, portable, and reusable" #### [09:00] — [H2] AI behavior becomes more steerable with site-specific context - Key idea: AI tools can reference actual site standards rather than generic defaults - Evidence: "Results are site-specific rather than generic, with less need for repeated prompting" #### [11:15] — [H2] Autonomous agents need guardrails for brand alignment - Key idea: Future AI agents handling customer interactions need site voice and boundary understanding - Evidence: "Those agents need to understand the site's voice, boundaries, and standards" #### [13:30] — [H3] Shared foundation prevents conflicting tool behaviors - Key idea: Consistent source of truth enables coherent behavior across core, host, and plugin features - Evidence: "Makes it easier for multiple features to behave coherently without creating conflicting rules" #### [15:45] — [H2] Initial focus on capture and retrieval infrastructure - Key idea: Foundation establishment prioritized over AI-driven experiences - Evidence: "The initial emphasis is on capturing and retrieving guidelines" #### [17:00] — [H3] Practical feedback needed on schema and workflows - Key idea: Team seeking input on content standards, storage location, and field structure - Evidence: "What schema and fields should we land on? Which workflows matter most?" ## 📚 References - [Initial PR #75164](https://github.com/WordPress/gutenberg/pull/75164) - [Tracking Issue #75171](https://github.com/WordPress/gutenberg/issues/75171) - [WordPress AI Team Handbook](https://make.wordpress.org/ai/) ## 🗣️ Paraphrase - WordPress is creating a centralized system for content guidelines that currently exist scattered across external documents and institutional knowledge - This foundation will immediately help human editors maintain consistency while enabling future AI tools to understand site-specific standards - The Gutenberg experiment approach allows testing and refinement before committing to stable core APIs and long-term maintenance ## 📰 Newsletter The WordPress AI Team just announced an exciting Content Guidelines experiment for Gutenberg! 🎉 Instead of keeping your editorial standards scattered across Google Docs, PDFs, and team wikis, this experiment creates a first-class home for content guidelines right inside WordPress. Think voice and tone rules, image standards, accessibility requirements, and structural guidelines - all discoverable when you need them most. The brilliant part? This isn't just for AI (though AI tools will love having site-specific context). It immediately helps human editors stay consistent and gives plugin developers a reliable way to respect your site's standards. Want to shape this feature? Share your use cases in the [tracking issue](https://github.com/WordPress/gutenberg/issues/75171) and follow the [initial PR](https://github.com/WordPress/gutenberg/pull/75164). Resources: [Learn WordPress](https://learn.wordpress.org/), [Developer Docs](https://developer.wordpress.org/), [WP-CLI](https://wp-cli.org/) ## ✅ Action Items #### WordPress - Core: Review Content Guidelines PR #75164 for API design and data modeling feedback - Core AI: Define integration points between Content Guidelines and AI Experiments features - Gutenberg: Test experiment UI across post editor, site editor, and admin contexts - Community: Gather use cases from multi-author sites and enterprise WordPress installations - Documentation: Prepare guidelines schema documentation and migration patterns #### The WPCC - Programs: Consider Content Guidelines integration for WordPress agency fellowship projects - Funding: Evaluate matched grants for ecosystem adoption and plugin development ## 🧪 Hypotheses - Sites with centralized content guidelines will maintain more consistent voice and formatting across authors - AI tools referencing site-specific guidelines will require fewer manual corrections than generic AI outputs - Plugin developers will adopt Content Guidelines API for editorial features when stable interface is available - Editorial teams will migrate external style guides into WordPress when native storage is available ### 📊 Methodology - A/B testing comparing content consistency on sites with and without centralized guidelines - User research tracking time-to-publish and revision cycles across different editorial workflow configurations - Plugin ecosystem analysis measuring API adoption rates and integration patterns ### ❓ Questions - How granular should guideline scope be (site-wide vs post-type vs taxonomy specific)? - What's the right balance between structured fields and free-form guidance text? - Should Content Guidelines integrate with user roles and capabilities for editing permissions? ### 🔮 Future Research - Integration patterns between Content Guidelines and existing editorial workflow plugins - Performance implications of guideline retrieval during AI-assisted content generation - Multi-site network support for shared and inherited guideline hierarchies ### 💡 Implications - Practice: Editorial teams can centralize scattered style guides and onboarding materials within WordPress - Policy: Sites can enforce accessibility standards and brand compliance through tool integration - Security: Content Guidelines may need capability restrictions for sensitive brand information - Education: New workflows needed for migrating existing editorial standards into structured format - Funding: Plugin ecosystem development opportunities for advanced editorial workflow features ### 🧠 Learning Styles Assessment Reading level estimate: 12th grade #### 👀 Visual learners - Present: GitHub issue and PR links for code examination - Improve: Mockups of Content Guidelines UI, data flow diagrams #### 🔊 Aural learners - Present: WordPress Slack #core-ai channel discussions - Improve: Recorded walkthrough of experiment goals and technical approach #### 🗣️ Verbal learners - Present: Clear definitions of "Content Guidelines" and "Gutenberg experiment" - Improve: Analogies comparing scattered vs centralized editorial standards #### 🧩 Kinesthetic learners - Present: GitHub PR for hands-on testing and feedback - Improve: Step-by-step guide for testing experimental interface #### 🧠 Logical learners - Present: Clear problem statement and solution rationale - Improve: Decision matrix for experiment vs direct core integration #### 🧑‍🤝‍🧑 Social learners - Present: GitHub tracking issue for community discussion - Improve: Structured feedback collection from different user types #### 🧘‍♀️ Solitary learners - Present: Self-contained explanation of experiment goals - Improve: Individual assessment questions for content standards evaluation #### 🌿 Naturalistic learners - Present: Ecosystem thinking about plugin and host integration - Improve: Content lifecycle perspective from creation to maintenance ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Proper heading hierarchy and descriptive link text - Improve: ARIA labels for GitHub issue and PR references #### Keyboard navigation - Present: Standard WordPress admin navigation patterns - Improve: Skip links for long technical discussions #### Contrast and readability - Present: WordPress admin color scheme compliance - Improve: Code syntax highlighting in examples #### Text resizing and reflow - Present: WordPress responsive admin design - Improve: Ensure technical content remains readable at high zoom levels #### Media and captions - Present: Text-based announcement format - Improve: Alt text for any future interface mockups #### Forms and interactions - Present: Standard commenting and feedback mechanisms - Improve: Structured feedback forms for specific use cases ### 🌍 DEIB Assessment #### Cultural breadth - Present: Global WordPress community consideration - Improve: Multi-language content standards examples #### Inclusive language - Present: Technical terminology with clear definitions - Improve: Plain language summaries for non-technical stakeholders #### Neurodiversity support - Present: Structured sections and clear headings - Improve: Executive summary with key action items #### Representation - Present: Collaborative development approach - Improve: Diverse use case examples beyond English-language sites #### Psychological safety - Present: Open invitation for community feedback - Improve: Explicit welcome for different expertise levels ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Strong - scattered guidelines create consistency problems, centralization addresses root cause - Inductive strength: Moderate - based on common patterns but limited empirical data - Causal reasoning: Strong - clear connection between guideline accessibility and tool consistency - Analogical strength: Good - comparison to existing WordPress configuration patterns #### Fallacies - Appeal to novelty: Minor suggestion that newer centralized approach is inherently better - Begging the question: Assumes Content Guidelines belong in core without exploring plugin alternatives #### Tone of voice - Overall tone: Collaborative and technical with appropriate uncertainty about implementation details ### 🛡️ DARVO Analysis - Deny: No denial patterns present - Attack: No attack patterns present - Reverse victim/offender: No reversal patterns present - Emotional cues and rhetoric: Positive collaborative language encouraging community participation ## 🎯 Conclusion Content Guidelines represents a thoughtful approach to centralizing editorial standards within WordPress, addressing a real pain point while establishing infrastructure for AI-enhanced workflows. The Gutenberg experiment model appropriately de-risks core integration while enabling ecosystem feedback. The immediate practical benefit for multi-author sites and editorial teams provides clear value independent of AI features, while the structured approach creates opportunities for more sophisticated tool integration over time. Success will depend on community feedback about schema design, workflow integration, and migration patterns from existing editorial systems. The emphasis on foundation-building over flashy AI features demonstrates mature product thinking about sustainable feature development. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad ### [H1] Centralized content guidelines enable consistent multi-author publishing > [!quote] [Content Guidelines: A Gutenberg Experiment](https://make.wordpress.org/ai/2026/02/03/content-guidelines-a-gutenberg-experiment/) by [[James LePage]] via [[WordPress AI Team]]. Published 2026-02-03. Accessed 2026-02-03. > "On multi-author sites, keeping voice, structure, and formatting consistent is an ongoing challenge." Addresses core editorial workflow problem that exists independently of AI features, establishing immediate value proposition. [view highlight](https://make.wordpress.org/ai/2026/02/03/content-guidelines-a-gutenberg-experiment/#H1) #xref #articleseed ID:rw_cg_consistency ### [H2] AI tools need site-specific context for steerable behavior > [!quote] Content Guidelines: A Gutenberg Experiment > "When AI-powered features can reference a site's actual standards, the results are site-specific rather than generic." Foundation for AI integration that depends on structured guidelines rather than treating AI as separate feature category. [view highlight](https://make.wordpress.org/ai/2026/02/03/content-guidelines-a-gutenberg-experiment/#H2) #xref ID:rw_cg_ai_steering --- ### 🔖 Atomic Split Pad (Zettel Candidates) #### [Z1] Gutenberg experiments de-risk core API commitment - Scope: New feature categories that cross multiple interfaces and require ecosystem validation - Pointer: Content Guidelines rationale section - Links: [[WordPress-Core-Development]] [[API-Design]] #### [Z2] Editorial standards scatter without centralized storage - Scope: Multi-contributor content management systems - Pointer: Problem statement opening - Links: [[Content-Management]] [[Editorial-Workflow]] --- ### ✏️ Fleeting Queue - [F1] Test Content Guidelines PR for accessibility compliance — GitHub #75164 #fleeting #inbox - [F2] Document Content Guidelines import/export patterns — WordPress migration workflows #fleeting #inbox - [F3] Evaluate Content Guidelines performance impact — AI tool integration overhead #fleeting #inbox <!-- deep-read:sections end --> 📄 **Full text:** ![[Full Document Contents/Articles/Content Guidelines A Gutenberg Experiment|Content Guidelines: A Gutenberg Experiment, make.wordpress.org]] ## Highlights - Content Guidelines isn’t an AI-only feature. It doesn’t depend on AI, but AI should depend on it. A unified store of guidelines makes standards discoverable, portable, and reusable, whether the person applying them is a writer, an editor, a plugin, or an AI assistant. ([View Highlight](https://read.readwise.io/read/01kkf7133nrj1adwh25rscd6yc)) - Tags: 👻 ai highlighted