Little Big Things for WordPress Editing 🔗 **Source:** [Little Big Things for WordPress Editing](https://rich.blog/little-big-things/) > [!note]+ Document Notes > tags: [wordpress-editing, user-experience, block-editor] > author: Rich Tabor > source: rich.blog > reference: https://rich.blog/little-big-things/ > date created: {{date:YYYY-MM-DD}} {{time:HH:mm}} > > # 🏷️ Title: Little Big Things for WordPress Editing > <!-- 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) ## 📝 Summary - **What happened**: Rich Tabor proposed three UX improvements for WordPress block editor: simplified block locking, unified synced entity editing, and streamlined zoom-out pattern insertion. - **Why it matters**: While agentic workflows are becoming prominent in WordPress, manual editing still needs friction reduction for creators who want direct control. - **Key stakeholders**: WordPress contributors, core developers, content creators, and theme/pattern designers. - **Risks and tradeoffs**: Breaking existing user mental models vs. simplifying complexity that has accumulated over time. - **Bottom line**: Small scope changes can remove significant editing friction by consolidating overlapping features into consistent interaction patterns. ## 📖 Main Content Rich Tabor identifies three "little big things" that could dramatically improve WordPress editing experience through complexity reduction rather than feature addition. ### Block Locking Simplification Currently, WordPress has two separate locking systems: auto-lock for inserted patterns (introduced in WordPress 7.0) and content-only locking. Tabor proposes consolidating these into the existing content-only locking system while adding layout lock options to the block lock modal. This would eliminate the confusing "in-between" state that patterns currently create. The proposal also makes lock controls functional in List View, where they're currently decorative. Users would be able to click the lock icon to access all locking functions (movement, removal, layout) in one place, eventually eliminating the separate block locking modal entirely. ### Unified Synced Entity Editing The current editing flow for synced patterns, template parts, and inserted patterns routes users to different views, causing disorientation and loss of context. Tabor's solution implements a "spotlight mode" where the selected block stays in focus while others fade out, maintaining the user's place in the editor. This creates a consistent interaction pattern: click edit, make changes in place, click done or click elsewhere to return to normal view. The isolated view remains available through "Edit original" for users who prefer it. ### Zoom-Out Pattern Insertion The current zoom-out mode opens a sidebar inserter that displaces content and requires manual navigation to return to the original state. Tabor proposes replacing this with the existing Patterns Explorer modal, which maintains canvas position and provides a clear temporary selection state. Additional improvements include adding "Add before" and "Add after" options to the block toolbar, and changing "Change design" to "Replace" with the Patterns Explorer pre-filtered to relevant categories. ## 🗒️ Notes - All three proposals focus on reusing existing UI patterns rather than creating new ones - The changes aim to reduce cognitive load by eliminating exceptions to established interaction models - Tabor explicitly states he's not precious about his PRs and encourages other contributors to take them forward - The timing aligns with WordPress having "many pieces in place" making complexity reduction the priority - WordPress 7.0 introduced auto-lock for patterns as a separate construct from content-only locking - Current pattern insertion in zoom-out mode uses a custom UI instead of leveraging existing modal patterns ## 📚 References - [Rich Tabor's blog](https://rich.blog/) - WordPress block editor documentation - Referenced pull requests (specific URLs not provided in article) ## 🗣️ Paraphrase Rich Tabor argues that while AI agents are becoming central to WordPress workflows, human editors still need friction-free experiences. He proposes three targeted improvements that consolidate overlapping features rather than adding new ones. Block locking would be simplified by merging two confusing systems into one coherent model. Synced entity editing would keep users in context through spotlight mode instead of routing to separate views. Pattern insertion during zoom-out would use familiar modal patterns instead of custom sidebar interfaces. These changes prioritize consistency and cognitive load reduction over feature expansion. ## 📰 Newsletter **Simplifying WordPress Editing: The Power of Small Changes** Rich Tabor's latest post reminds us that sometimes the biggest improvements come from the smallest changes. While everyone's talking about AI agents in WordPress, he's focused on making manual editing less frustrating for the rest of us. His three "little big things" are masterclasses in UX simplification: consolidating confusing block locking systems, keeping you oriented when editing synced content, and making pattern insertion actually behave like the rest of the editor. The best part? He's already built working prototypes and is encouraging other contributors to run with them. This is exactly the kind of polish work that makes WordPress feel professional rather than cobbled-together. **Resources:** - [Read the full post](https://rich.blog/little-big-things/) - Track the related pull requests in WordPress Core - Join Rich's "Shaping WordPress" newsletter for more insights ## ✅ Action Items #### Core - Review and test Rich Tabor's pull requests for block locking simplification - Evaluate unified synced entity editing implementation for core inclusion - Assessment zoom-out pattern insertion modal replacement proposal - Plan migration path for existing block locking modal users - Update block editor documentation to reflect simplified locking model #### Community - Contributors: Pick up, test, and iterate on the proposed pull requests - Provide feedback on edge cases and accessibility implications - Test with real-world content creation workflows #### Design - Validate spotlight mode UX doesn't confuse users familiar with current flows - Ensure lock controls in List View meet accessibility standards - Review Patterns Explorer modal performance with large pattern libraries ## 🧪 Hypotheses - Consolidating block locking systems will reduce support requests and user confusion - Spotlight mode editing will increase user confidence when working with synced content - Reusing Patterns Explorer modal will reduce cognitive load during pattern insertion - Simplified interaction models will lower the learning curve for new WordPress editors - Removing UI exceptions will make the editor feel more cohesive and professional ### 📊 Methodology - A/B testing between current and proposed block locking workflows measuring task completion time and error rates - User interviews comparing current synced entity editing vs. spotlight mode for context retention - Analytics tracking on pattern insertion completion rates before and after zoom-out modal changes - Usability testing with content creators of varying experience levels - Performance benchmarking of modal vs. sidebar approaches for pattern selection ### ❓ Questions - How will power users who rely on the current isolated editing views react to spotlight mode as the default? - What happens to existing content that depends on the current auto-lock behavior for patterns? - Will the simplified locking model handle complex nested pattern scenarios adequately? - How do these changes impact screen reader navigation and keyboard accessibility? - What's the migration strategy for sites with heavily customized block locking implementations? ### 🔮 Future Research - Investigate applying similar simplification principles to other WordPress admin areas - Explore how these UX patterns could apply to full site editing workflows - Research impact of reduced complexity on new user onboarding success rates - Study how simplified editing interfaces affect content creation productivity - Examine potential for extending spotlight mode to other WordPress editing contexts ### 💡 Implications - **Practice**: Content creators will need less training on WordPress editing nuances - **Policy**: WordPress Core should prioritize consolidation over feature addition during mature phases - **Security**: Simplified locking models may affect access control patterns in enterprise WordPress usage - **Education**: Training materials and documentation will need updates to reflect simplified workflows - **Funding**: Demonstrates that high-impact improvements don't require large development investments ### 🧠 Learning Styles Assessment - **Reading level estimate**: Flesch-Kincaid Grade 12.3 - appropriate for professional WordPress users #### 👀 Visual learners - **Present**: Clear problem/solution structure, specific UI element references - **Improve**: Screenshots of current vs. proposed interfaces, workflow diagrams, before/after comparisons #### 🔊 Aural learners - **Present**: Clear narrative structure explaining each change - **Improve**: Podcast discussion or recorded walkthrough of the proposed changes #### 🗣️ Verbal learners - **Present**: Good use of analogies (spotlight mode, temporary selection state) - **Improve**: Glossary of technical terms, comparison tables between current and proposed approaches #### 🧩 Kinesthetic learners - **Present**: References to actual pull requests and implementations - **Improve**: Interactive demos, sandbox environments to test the proposed changes #### 🧠 Logical learners - **Present**: Clear cause-and-effect reasoning for each proposed change - **Improve**: Decision trees showing when to use each locking option, flowcharts of the editing workflows #### 🧑‍🤝‍🧑 Social learners - **Present**: Call for contributor collaboration - **Improve**: Discussion forums, collaborative testing sessions, contributor office hours #### 🧘‍♀️ Solitary learners - **Present**: Detailed written explanation of each concept - **Improve**: Self-assessment checklist for testing the changes, reflection prompts on current editing pain points #### 🌿 Naturalistic learners - **Present**: Emphasis on removing accumulated complexity - **Improve**: Analogies to natural systems, discussion of sustainable UX patterns ### 📊 Accessibility Assessment #### Screen reader semantics - **Present**: Clear heading structure, descriptive language - **Improve**: ARIA labels for proposed UI changes, semantic markup examples #### Keyboard navigation - **Present**: Discussion of lock controls usability - **Improve**: Keyboard shortcuts documentation, tab order specifications #### Contrast and readability - **Present**: Clean text formatting, good contrast - **Improve**: Consider visual indicators for spotlight mode, ensure lock icons maintain contrast #### Text resizing and reflow - **Present**: Responsive text content - **Improve**: Test proposed modal interfaces at high zoom levels #### Media and captions - **Present**: No multimedia to assess - **Improve**: Screen recordings with captions showing the proposed changes #### Forms and interactions - **Present**: Focus on simplified interactions - **Improve**: Error states for locking operations, confirmation patterns for unlock actions ### 🌍 DEIB Assessment #### Cultural breadth - **Present**: Universal focus on usability rather than culturally specific patterns - **Improve**: Consider right-to-left layout implications, international editing workflows #### Inclusive language - **Present**: Plain language explanations, avoids excessive jargon - **Improve**: Define technical terms, provide more context for WordPress-specific concepts #### Neurodiversity support - **Present**: Focus on reducing cognitive load, consistent interaction patterns - **Improve**: Consider attention and working memory impacts, provide progress indicators #### Representation - **Present**: Focuses on technical implementation - **Improve**: Acknowledge diverse user needs and editing contexts #### Psychological safety - **Present**: Encouraging tone about contributor collaboration - **Improve**: Emphasize that feedback and iteration are welcome, reduce technical intimidation ### ✅ Logical Validity #### Strong reasoning - **Simplification principle**: Clear logic that complexity accumulation hurts usability - supported by UX research - **Consistency argument**: Strong reasoning that exceptions to interaction patterns increase cognitive load - **Evidence-based approach**: Uses concrete examples (patterns, synced entities, zoom-out) rather than abstract principles #### Fallacies - **Appeal to authority**: Minor - relies on his own expertise without acknowledging potential blind spots - **False dichotomy**: Presents current complex system vs. his solution without exploring other alternatives #### Tone of voice - **Collaborative and practical**: "If you know me, you know I'm not precious about my PRs" - emphasizes results over ownership - **Problem-focused**: Clearly identifies pain points before proposing solutions - **Implementation-oriented**: Moves beyond criticism to working prototypes ### 🛡️ DARVO Analysis - **Deny**: No denial patterns present - acknowledges current system limitations directly - **Attack**: No attacks on individuals or groups - focuses on system design issues - **Reverse victim/offender**: No reversal patterns - takes responsibility for proposing solutions rather than just identifying problems - **Overall assessment**: Clean argumentation focused on constructive improvement rather than defensive rhetoric ## 🎯 Conclusion Rich Tabor's "little big things" demonstrate that mature software benefits more from thoughtful consolidation than feature addition. His three proposals - simplified block locking, unified synced entity editing, and consistent pattern insertion - address real usability pain points through complexity reduction rather than interface expansion. The practical next steps for WordPress contributors are clear: test the existing pull requests, provide feedback on edge cases, and help move these improvements toward core inclusion. For the broader WordPress community, this represents a valuable model of how incremental UX improvements can significantly impact daily editing workflows. <!-- deep-read:sections end -->