Iterating on Notes in WordPress  🔗 **Source:** [Iterating on Notes in WordPress](https://nomad.blog/2026/02/28/iterating-on-notes-in-wordpress/) > [!note]+ Document Notes > tags: [wordpress, user-experience, ai-development, block-editor] > author: agm > source: nomad.blog > reference: https://nomad.blog/2026/02/28/iterating-on-notes-in-wordpress/ > date created: 2024-12-19 15:30 > > # 🏷️ Title: Iterating on Notes in WordPress > <!-- deep-read:sections start --> ## 🧰 Action Inbox - [H1] Review PR 76024 for show/hide notes functionality — UX flow concerns #wordpress - [H2] Evaluate filter terminology (Open vs Unresolved) — PR 75982 #user-experience - [H3] Test compact notes implementation — PR 74985 before resizable sidebar #block-editor ## 🧭 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 - [PR 76024 - Show/hide notes](https://github.com/WordPress/gutenberg/pull/76024) - [PR 75982 - Filter options](https://github.com/WordPress/gutenberg/pull/75982) - [PR 74985 - Compact notes](https://github.com/WordPress/gutenberg/pull/74985) ## 📝 Summary - What happened: Three WordPress Notes features missed the 7.0 deadline but development continues with AI assistance - Why it matters: Notes functionality is critical for collaborative editing in WordPress block editor - Key stakeholders: WordPress core contributors, block editor users, collaborative content creators - Risks: UX friction with show/hide functionality, terminology confusion, sidebar space limitations - Bottom line: Iterative approach balancing feature completeness with user experience clarity ## 📖 Main Content The author shares three WordPress Notes improvements developed with Claude AI that didn't make WordPress 7.0: show/hide notes on canvas, filtering in Notes panel, and compact notes display. Each feature addresses specific UX challenges but introduces new design questions. The show/hide notes feature (PR 76024) aims to reduce canvas clutter but may add friction compared to Google Docs' streamlined approach. The filtering system (PR 75982) debated "Open vs Resolved" versus "Unresolved vs Resolved" terminology. The compact notes option (PR 74985) addresses sidebar space constraints without requiring complex resizable sidebar implementation. These features represent practical AI-assisted development while highlighting the tension between feature richness and user experience simplicity in WordPress core development. ## 🗒️ Notes This content is a blog post without video timestamps, so the Notes section will focus on the three main features discussed: #### 📝 Show/Hide Notes Feature (PR 76024) - Key idea: Reduces canvas clutter by allowing users to hide notes - Evidence: "adds some friction... compared to a one click option with Google docs" - Concern: Extra clicks needed to access full Notes sidebar #### 🔍 Filter Options in Notes Panel (PR 75982) - Key idea: Radio menu filtering system for note status - Evidence: "Should the filter by Unresolved and Resolved or Open and Resolved?" - Decision point: Terminology clarity affects user comprehension #### 📏 Compact Notes Implementation (PR 74985) - Key idea: Space-efficient note display without resizable sidebar - Evidence: "Notes take up a fair amount of space as is" - Trade-off: Value of minimization versus technical complexity #### 🤖 AI Development Process - Key idea: Features built using Claude code for learning purposes - Evidence: "Learn AI deeply efforts" - Context: Demonstrates practical AI application in WordPress development #### 🔄 WordPress 7.0 Timeline Pressure - Key idea: Feature punting happens for good reasons in core development - Evidence: "punting happens and it happened for good reason" - Reality: Balancing feature completeness with release schedules #### 🎯 UX Design Philosophy - Key idea: Clarity versus convenience trade-offs in interface design - Evidence: "adds clarity to what one is looking at when they open the Notes sidebar" - Challenge: Multiple valid approaches to user experience problems #### 🔧 Technical Implementation Constraints - Key idea: Resizable sidebar requires more complex technical work - Evidence: "width of the sidebar is hard-coded and there's not a private API" - Limitation: Current architecture constrains certain UX improvements #### 📊 Comparative Analysis Approach - Key idea: Google Docs provides useful UX reference points - Evidence: Multiple comparisons to Google Docs behavior patterns - Strategy: Learning from established collaborative editing interfaces ## 📚 References - [Show/hide notes PR 76024](https://github.com/WordPress/gutenberg/pull/76024) - [Filter options PR 75982](https://github.com/WordPress/gutenberg/pull/75982) - [Compact notes PR 74985](https://github.com/WordPress/gutenberg/pull/74985) ## 🗣️ Paraphrase - WordPress Notes improvements are being developed iteratively with AI assistance, focusing on show/hide functionality, filtering options, and compact display modes - Each feature addresses real user needs but introduces UX trade-offs that require careful consideration and community feedback - The development process demonstrates practical AI application in WordPress core while highlighting the complexity of balancing user experience with technical constraints ## 📰 Newsletter **WordPress Notes Features Get AI-Powered Iteration** While WordPress 7.0 beta 2 rolls out, exciting collaborative editing improvements are in development! Three Notes features are being refined with AI assistance: canvas show/hide controls, smart filtering options, and compact display modes. The show/hide functionality tackles canvas clutter but raises UX flow questions compared to Google Docs. Filter terminology debates ("Open" vs "Unresolved") show how word choice impacts user clarity. Compact notes offer space efficiency without complex sidebar resizing. This work demonstrates practical AI application in WordPress development while highlighting core's careful balance between features and user experience. **Key Takeaways:** - AI tools can accelerate WordPress feature development - UX decisions require community input and iteration - Core development balances innovation with usability Resources: [Learn WordPress](https://learn.wordpress.org/), [Developer Docs](https://developer.wordpress.org/), [WP-CLI](https://wp-cli.org/) ## ✅ Action Items #### WordPress - Core: Review Notes UX patterns for consistency with collaborative editing standards - Core Program Team: Coordinate Notes feature timeline with 7.1 planning cycle - Community: Gather feedback on PR implementations from diverse user groups - Design: Establish Notes interaction patterns that scale across different content types - Documentation: Create Guidelines for Notes feature usage and best practices - Accessibility: Audit Notes features for keyboard navigation and screen reader support #### Community - Contributors: Test Notes PRs with real collaborative workflows - Sponsors: Consider funding UX research for collaborative editing features ## 🧪 Hypotheses - Show/hide notes functionality will reduce visual clutter but may decrease feature discoverability - "Open/Resolved" terminology will be clearer to users than "Unresolved/Resolved" - Compact notes display will improve sidebar usability without requiring resizable implementation - AI-assisted development can accelerate WordPress feature iteration while maintaining code quality ### 📊 Methodology - A/B testing of terminology options with WordPress users across different experience levels - Usability testing of show/hide workflows compared to current Notes sidebar behavior - Performance analysis of compact notes rendering with large comment threads ### ❓ Questions - How do collaborative editing patterns in WordPress compare to established tools like Google Docs? - What's the optimal balance between Notes feature richness and interface simplicity? - Can AI-assisted development maintain WordPress core's code quality and accessibility standards? ### 🔮 Future Research - Comprehensive UX research on collaborative editing workflows in WordPress - Investigation of resizable sidebar implementation paths and technical requirements - Analysis of Notes feature adoption patterns across different WordPress user segments ### 💡 Implications - Practice: AI tools can accelerate WordPress development while requiring careful UX validation - Policy: Core development processes may need updates for AI-assisted contributions - Education: WordPress developers need guidance on effective AI collaboration techniques - Funding: Investment in collaborative editing UX research could benefit the entire WordPress ecosystem ### 🧠 Learning Styles Assessment Reading level estimate: Grade 12 (Flesch-Kincaid) #### 👀 Visual learners - Present: Screenshots comparing filter options, Google Docs interface examples - Improve: Flowcharts showing UX decision trees, before/after interface comparisons #### 🔊 Aural learners - Present: None identified - Improve: Audio walkthrough of Notes features, developer interview podcast #### 🗣️ Verbal learners - Present: Clear terminology discussions, UX trade-off explanations - Improve: Analogies comparing WordPress Notes to familiar collaborative tools #### 🧩 Kinesthetic learners - Present: Links to actual PRs for hands-on testing - Improve: Step-by-step testing checklist, interactive demo environment #### 🧠 Logical learners - Present: Systematic feature comparison, technical constraint analysis - Improve: Decision matrix for UX options, feature impact assessment tables #### 🧑‍🤝‍🧑 Social learners - Present: Call for community feedback, PR collaboration examples - Improve: Structured feedback collection, collaborative testing guidelines #### 🧘‍♀️ Solitary learners - Present: Individual reflection on UX decisions - Improve: Self-assessment questions for Notes feature preferences #### 🌿 Naturalistic learners - Present: Organic development process description - Improve: Connections to software ecosystem evolution patterns ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Standard blog structure with clear headings - Improve: Ensure PR links have descriptive labels, add ARIA descriptions for complex UI #### Keyboard navigation - Present: Standard web navigation available - Improve: Notes features should support full keyboard accessibility #### Contrast and readability - Present: Meets basic contrast requirements - Improve: Ensure compact notes maintain sufficient contrast ratios #### Text resizing and reflow - Present: Responsive blog design - Improve: Test Notes features at 200% zoom for usability #### Media and captions - Present: Screenshots used without alt text descriptions - Improve: Add descriptive alt text for UI screenshots, consider video demos with captions #### Forms and interactions - Present: Basic comment form - Improve: Ensure Notes filtering controls have proper labels and error handling ### 🌍 DEIB Assessment #### Cultural breadth - Present: English-focused development discussion - Improve: Consider Notes feature implications for multilingual WordPress sites #### Inclusive language - Present: Technical language appropriate for developer audience - Improve: Define WordPress-specific terminology for broader audience #### Neurodiversity support - Present: Well-structured content with clear sections - Improve: Add summary bullets, consider cognitive load of multiple Notes features #### Representation - Present: Individual contributor perspective - Improve: Include diverse voices in UX decision-making process #### Psychological safety - Present: Welcomes feedback appropriately - Improve: Establish clear channels for constructive feature critique ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Clear logic from UX problems to proposed solutions - Inductive strength: Uses Google Docs patterns to inform WordPress decisions - Causal reasoning: Links interface changes to user behavior outcomes - Analogical strength: Appropriate comparisons to established collaborative tools #### Fallacies - False dichotomy: Presents resizable vs. compact notes as either/or when both could coexist - Appeal to authority: Heavy reliance on Google Docs patterns without questioning their universal applicability #### Tone of voice - Overall tone: Thoughtful and collaborative, inviting feedback while acknowledging uncertainty ### 🛡️ DARVO Analysis - Deny: No denial patterns present - Attack: No attack patterns present - Reverse victim/offender: Not applicable to this technical content - Emotional cues: Professional and constructive throughout ## 🎯 Conclusion This post exemplifies thoughtful WordPress core development that balances innovation with user experience. The AI-assisted development approach shows promise while highlighting the continued importance of community feedback and iterative design in WordPress features. The Notes improvements address real collaborative editing needs but require careful UX validation. The transparent development process and openness to feedback reflect WordPress's open-source values while pushing forward with modern development tools. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad Purpose: Stage CEE units that become Literature notes. Split level: H3 ### [H1] AI tools accelerate WordPress feature development > [!quote] [Iterating on Notes in WordPress](https://nomad.blog/2026/02/28/iterating-on-notes-in-wordpress/) by [[agm]] via [[nomad.blog]]. Published February 28, 2026. Accessed December 19, 2024. > "These are all purposefully contained features to consider and have some open questions. They are all done with Claude code as part of my 'Learn AI deeply' efforts." Demonstrates practical application of AI assistance in WordPress core development while maintaining focus on user experience validation. [view highlight](https://nomad.blog/2026/02/28/iterating-on-notes-in-wordpress/#H1) #xref #articleseed ID:rw_wp_notes_ai ### [H2] WordPress UX decisions require community feedback loops > [!quote] [Iterating on Notes in WordPress](https://nomad.blog/2026/02/28/iterating-on-notes-in-wordpress/) > "Feedback welcomed, here or on the PRs. Whether any of these land or not, they have been absolutely awesome to work on." Shows importance of collaborative decision-making in WordPress core feature development process. [view highlight](https://nomad.blog/2026/02/28/iterating-on-notes-in-wordpress/#H2) #xref ID:rw_wp_community_feedback --- ### 🔖 Atomic Split Pad (Zettel Candidates) Purpose: Promote reusable claims into Atomic notes. Split level: H4 #### [Z1] Feature friction analysis improves UX decisions - Applies to software interface design across platforms - Reference to Google Docs comparison and click-count analysis - Links: [[User-Experience-Design]] [[Interface-Friction]] #### [Z2] Technical constraints shape feature implementation paths - Universal software development principle - Pointer to sidebar resizing limitations discussion - Links: [[Technical-Debt]] [[Architecture-Constraints]] --- ### ✏️ Fleeting Queue Purpose: Capture quick actions for Fleeting notes. - [F1] Test WordPress Notes PRs for UX friction — https://github.com/WordPress/gutenberg/pull/76024 #fleeting #inbox - [F2] Research collaborative editing patterns — Google Docs vs WordPress comparison #fleeting #inbox - [F3] Evaluate AI coding tools for WordPress development — Claude code effectiveness #fleeting #inbox <!-- deep-read:sections end --> [[3. Resources/Readwise/Full Document Contents/Articles/Iterating on Notes in WordPress|Full Document Contents]] ## Document Notes --- tags: #wordpress #user-experience #ai-development #block-editor author: agm source: nomad.blog reference: https://nomad.blog/2026/02/28/iterating-on-notes-in-wordpress/ date created: 2024-12-19 15:30 --- # 🏷️ Title: Iterating on Notes in WordPress ## 🧰 Action Inbox - [H1] Review PR 76024 for show/hide notes functionality — UX flow concerns #wordpress - [H2] Evaluate filter terminology (Open vs Unresolved) — PR 75982 #user-experience - [H3] Test compact notes implementation — PR 74985 before resizable sidebar #block-editor ## 🧭 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 - [PR 76024 - Show/hide notes](https://github.com/WordPress/gutenberg/pull/76024) - [PR 75982 - Filter options](https://github.com/WordPress/gutenberg/pull/75982) - [PR 74985 - Compact notes](https://github.com/WordPress/gutenberg/pull/74985) ## 📝 Summary - What happened: Three WordPress Notes features missed the 7.0 deadline but development continues with AI assistance - Why it matters: Notes functionality is critical for collaborative editing in WordPress block editor - Key stakeholders: WordPress core contributors, block editor users, collaborative content creators - Risks: UX friction with show/hide functionality, terminology confusion, sidebar space limitations - Bottom line: Iterative approach balancing feature completeness with user experience clarity ## 📖 Main Content The author shares three WordPress Notes improvements developed with Claude AI that didn't make WordPress 7.0: show/hide notes on canvas, filtering in Notes panel, and compact notes display. Each feature addresses specific UX challenges but introduces new design questions. The show/hide notes feature (PR 76024) aims to reduce canvas clutter but may add friction compared to Google Docs' streamlined approach. The filtering system (PR 75982) debated "Open vs Resolved" versus "Unresolved vs Resolved" terminology. The compact notes option (PR 74985) addresses sidebar space constraints without requiring complex resizable sidebar implementation. These features represent practical AI-assisted development while highlighting the tension between feature richness and user experience simplicity in WordPress core development. ## 🗒️ Notes This content is a blog post without video timestamps, so the Notes section will focus on the three main features discussed: #### 📝 Show/Hide Notes Feature (PR 76024) - Key idea: Reduces canvas clutter by allowing users to hide notes - Evidence: "adds some friction... compared to a one click option with Google docs" - Concern: Extra clicks needed to access full Notes sidebar #### 🔍 Filter Options in Notes Panel (PR 75982) - Key idea: Radio menu filtering system for note status - Evidence: "Should the filter by Unresolved and Resolved or Open and Resolved?" - Decision point: Terminology clarity affects user comprehension #### 📏 Compact Notes Implementation (PR 74985) - Key idea: Space-efficient note display without resizable sidebar - Evidence: "Notes take up a fair amount of space as is" - Trade-off: Value of minimization versus technical complexity #### 🤖 AI Development Process - Key idea: Features built using Claude code for learning purposes - Evidence: "Learn AI deeply efforts" - Context: Demonstrates practical AI application in WordPress development #### 🔄 WordPress 7.0 Timeline Pressure - Key idea: Feature punting happens for good reasons in core development - Evidence: "punting happens and it happened for good reason" - Reality: Balancing feature completeness with release schedules #### 🎯 UX Design Philosophy - Key idea: Clarity versus convenience trade-offs in interface design - Evidence: "adds clarity to what one is looking at when they open the Notes sidebar" - Challenge: Multiple valid approaches to user experience problems #### 🔧 Technical Implementation Constraints - Key idea: Resizable sidebar requires more complex technical work - Evidence: "width of the sidebar is hard-coded and there's not a private API" - Limitation: Current architecture constrains certain UX improvements #### 📊 Comparative Analysis Approach - Key idea: Google Docs provides useful UX reference points - Evidence: Multiple comparisons to Google Docs behavior patterns - Strategy: Learning from established collaborative editing interfaces ## 📚 References - [Show/hide notes PR 76024](https://github.com/WordPress/gutenberg/pull/76024) - [Filter options PR 75982](https://github.com/WordPress/gutenberg/pull/75982) - [Compact notes PR 74985](https://github.com/WordPress/gutenberg/pull/74985) ## 🗣️ Paraphrase - WordPress Notes improvements are being developed iteratively with AI assistance, focusing on show/hide functionality, filtering options, and compact display modes - Each feature addresses real user needs but introduces UX trade-offs that require careful consideration and community feedback - The development process demonstrates practical AI application in WordPress core while highlighting the complexity of balancing user experience with technical constraints ## 📰 Newsletter **WordPress Notes Features Get AI-Powered Iteration** While WordPress 7.0 beta 2 rolls out, exciting collaborative editing improvements are in development! Three Notes features are being refined with AI assistance: canvas show/hide controls, smart filtering options, and compact display modes. The show/hide functionality tackles canvas clutter but raises UX flow questions compared to Google Docs. Filter terminology debates ("Open" vs "Unresolved") show how word choice impacts user clarity. Compact notes offer space efficiency without complex sidebar resizing. This work demonstrates practical AI application in WordPress development while highlighting core's careful balance between features and user experience. **Key Takeaways:** - AI tools can accelerate WordPress feature development - UX decisions require community input and iteration - Core development balances innovation with usability Resources: [Learn WordPress](https://learn.wordpress.org/), [Developer Docs](https://developer.wordpress.org/), [WP-CLI](https://wp-cli.org/) ## ✅ Action Items #### WordPress - Core: Review Notes UX patterns for consistency with collaborative editing standards - Core Program Team: Coordinate Notes feature timeline with 7.1 planning cycle - Community: Gather feedback on PR implementations from diverse user groups - Design: Establish Notes interaction patterns that scale across different content types - Documentation: Create Guidelines for Notes feature usage and best practices - Accessibility: Audit Notes features for keyboard navigation and screen reader support #### Community - Contributors: Test Notes PRs with real collaborative workflows - Sponsors: Consider funding UX research for collaborative editing features ## 🧪 Hypotheses - Show/hide notes functionality will reduce visual clutter but may decrease feature discoverability - "Open/Resolved" terminology will be clearer to users than "Unresolved/Resolved" - Compact notes display will improve sidebar usability without requiring resizable implementation - AI-assisted development can accelerate WordPress feature iteration while maintaining code quality ### 📊 Methodology - A/B testing of terminology options with WordPress users across different experience levels - Usability testing of show/hide workflows compared to current Notes sidebar behavior - Performance analysis of compact notes rendering with large comment threads ### ❓ Questions - How do collaborative editing patterns in WordPress compare to established tools like Google Docs? - What's the optimal balance between Notes feature richness and interface simplicity? - Can AI-assisted development maintain WordPress core's code quality and accessibility standards? ### 🔮 Future Research - Comprehensive UX research on collaborative editing workflows in WordPress - Investigation of resizable sidebar implementation paths and technical requirements - Analysis of Notes feature adoption patterns across different WordPress user segments ### 💡 Implications - Practice: AI tools can accelerate WordPress development while requiring careful UX validation - Policy: Core development processes may need updates for AI-assisted contributions - Education: WordPress developers need guidance on effective AI collaboration techniques - Funding: Investment in collaborative editing UX research could benefit the entire WordPress ecosystem ### 🧠 Learning Styles Assessment Reading level estimate: Grade 12 (Flesch-Kincaid) #### 👀 Visual learners - Present: Screenshots comparing filter options, Google Docs interface examples - Improve: Flowcharts showing UX decision trees, before/after interface comparisons #### 🔊 Aural learners - Present: None identified - Improve: Audio walkthrough of Notes features, developer interview podcast #### 🗣️ Verbal learners - Present: Clear terminology discussions, UX trade-off explanations - Improve: Analogies comparing WordPress Notes to familiar collaborative tools #### 🧩 Kinesthetic learners - Present: Links to actual PRs for hands-on testing - Improve: Step-by-step testing checklist, interactive demo environment #### 🧠 Logical learners - Present: Systematic feature comparison, technical constraint analysis - Improve: Decision matrix for UX options, feature impact assessment tables #### 🧑‍🤝‍🧑 Social learners - Present: Call for community feedback, PR collaboration examples - Improve: Structured feedback collection, collaborative testing guidelines #### 🧘‍♀️ Solitary learners - Present: Individual reflection on UX decisions - Improve: Self-assessment questions for Notes feature preferences #### 🌿 Naturalistic learners - Present: Organic development process description - Improve: Connections to software ecosystem evolution patterns ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Standard blog structure with clear headings - Improve: Ensure PR links have descriptive labels, add ARIA descriptions for complex UI #### Keyboard navigation - Present: Standard web navigation available - Improve: Notes features should support full keyboard accessibility #### Contrast and readability - Present: Meets basic contrast requirements - Improve: Ensure compact notes maintain sufficient contrast ratios #### Text resizing and reflow - Present: Responsive blog design - Improve: Test Notes features at 200% zoom for usability #### Media and captions - Present: Screenshots used without alt text descriptions - Improve: Add descriptive alt text for UI screenshots, consider video demos with captions #### Forms and interactions - Present: Basic comment form - Improve: Ensure Notes filtering controls have proper labels and error handling ### 🌍 DEIB Assessment #### Cultural breadth - Present: English-focused development discussion - Improve: Consider Notes feature implications for multilingual WordPress sites #### Inclusive language - Present: Technical language appropriate for developer audience - Improve: Define WordPress-specific terminology for broader audience #### Neurodiversity support - Present: Well-structured content with clear sections - Improve: Add summary bullets, consider cognitive load of multiple Notes features #### Representation - Present: Individual contributor perspective - Improve: Include diverse voices in UX decision-making process #### Psychological safety - Present: Welcomes feedback appropriately - Improve: Establish clear channels for constructive feature critique ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Clear logic from UX problems to proposed solutions - Inductive strength: Uses Google Docs patterns to inform WordPress decisions - Causal reasoning: Links interface changes to user behavior outcomes - Analogical strength: Appropriate comparisons to established collaborative tools #### Fallacies - False dichotomy: Presents resizable vs. compact notes as either/or when both could coexist - Appeal to authority: Heavy reliance on Google Docs patterns without questioning their universal applicability #### Tone of voice - Overall tone: Thoughtful and collaborative, inviting feedback while acknowledging uncertainty ### 🛡️ DARVO Analysis - Deny: No denial patterns present - Attack: No attack patterns present - Reverse victim/offender: Not applicable to this technical content - Emotional cues: Professional and constructive throughout ## 🎯 Conclusion This post exemplifies thoughtful WordPress core development that balances innovation with user experience. The AI-assisted development approach shows promise while highlighting the continued importance of community feedback and iterative design in WordPress features. The Notes improvements address real collaborative editing needs but require careful UX validation. The transparent development process and openness to feedback reflect WordPress's open-source values while pushing forward with modern development tools. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad Purpose: Stage CEE units that become Literature notes. Split level: H3 ### [H1] AI tools accelerate WordPress feature development > [!quote] [Iterating on Notes in WordPress](https://nomad.blog/2026/02/28/iterating-on-notes-in-wordpress/) by [[agm]] via [[nomad.blog]]. Published February 28, 2026. Accessed December 19, 2024. > "These are all purposefully contained features to consider and have some open questions. They are all done with Claude code as part of my 'Learn AI deeply' efforts." Demonstrates practical application of AI assistance in WordPress core development while maintaining focus on user experience validation. [view highlight](https://nomad.blog/2026/02/28/iterating-on-notes-in-wordpress/#H1) #xref #articleseed ID:rw_wp_notes_ai ### [H2] WordPress UX decisions require community feedback loops > [!quote] [Iterating on Notes in WordPress](https://nomad.blog/2026/02/28/iterating-on-notes-in-wordpress/) > "Feedback welcomed, here or on the PRs. Whether any of these land or not, they have been absolutely awesome to work on." Shows importance of collaborative decision-making in WordPress core feature development process. [view highlight](https://nomad.blog/2026/02/28/iterating-on-notes-in-wordpress/#H2) #xref ID:rw_wp_community_feedback --- ### 🔖 Atomic Split Pad (Zettel Candidates) Purpose: Promote reusable claims into Atomic notes. Split level: H4 #### [Z1] Feature friction analysis improves UX decisions - Applies to software interface design across platforms - Reference to Google Docs comparison and click-count analysis - Links: [[User-Experience-Design]] [[Interface-Friction]] #### [Z2] Technical constraints shape feature implementation paths - Universal software development principle - Pointer to sidebar resizing limitations discussion - Links: [[Technical-Debt]] [[Architecture-Constraints]] --- ### ✏️ Fleeting Queue Purpose: Capture quick actions for Fleeting notes. - [F1] Test WordPress Notes PRs for UX friction — https://github.com/WordPress/gutenberg/pull/76024 #fleeting #inbox - [F2] Research collaborative editing patterns — Google Docs vs WordPress comparison #fleeting #inbox - [F3] Evaluate AI coding tools for WordPress development — Claude code effectiveness #fleeting #inbox ## Highlights - Details matter and I’m torn on this one: Should the filter by `Unresolved` and `Resolved` or `Open` and `Resolved`? Here’s what each looks like side by side. I lean towards `Open` rather than `Unresolved` as it feels clearer and simpler. ([View Highlight](https://read.readwise.io/read/01kjjj590b991mwsh3hx8mtdar)) - Tags: 👻 ai highlighted ## 🌱 Spawned Notes - [[Lit · AI tools accelerate WordPress feature development]] - [[Lit · WordPress UX decisions require community feedback loops]] - [[Zet · Feature friction analysis improves UX decisions]] - [[Zet · Technical constraints shape feature implementation paths]] - [[Flt · Test WordPress Notes PRs for UX friction httpsgithubcomWordPressgutenbergpull760]] - [[Flt · Research collaborative editing patterns Google Docs vs WordPress comparison]] - [[Flt · Evaluate AI coding tools for WordPress development Claude code effectiveness]]