Overlapping Problems

đź”— **Source:** [Overlapping Problems](https://nomad.blog/2024/02/16/overlapping-problems/)
> [!note]+ Document Notes
> tags:
> - SiteEditing
> - WordPressPhase3
> - GlobalStyles
> Author: Unknown
> Source: WordPress Blog
> Reference:
> date created: 2024-09-10 18:00
>
> # Title: On My Mind: Site Editing Friction Points and Future Challenges
>
<!-- deep-read:sections start -->
## Table of Contents:
- [Summary](#summary)
- [Main Content](#main-content)
- [Changing Site-Wide Elements](#changing-site-wide-elements)
- [Understanding Where Elements Are Used](#understanding-where-elements-are-used)
- [Navigating Inconsistencies in the Interface](#navigating-inconsistencies-in-the-interface)
- [Challenges in Editing and Styling](#challenges-in-editing-and-styling)
- [Looking Forward to Phase 3](#looking-forward-to-phase-3)
- [Notes](#notes)
- [References](#references)
- [Paraphrase](#paraphrase)
- [Newsletter](#newsletter)
- [Action Items](#action-items)
- [Hypotheses](#hypotheses)
- [Methodology](#methodology)
- [Questions](#questions)
- [Future Research](#future-research)
- [Implications](#implications)
- [Logical Validity](#logical-validity)
- [Conclusion](#conclusion)
### References:
- WordPress Blog
## 📝 Summary:
The post explores ongoing challenges and friction points within the WordPress Site Editor, particularly focusing on the nuances of global vs. local changes, navigating interface inconsistencies, and the complexity of understanding inherited values and what users can edit. The goal is to improve the user experience as WordPress moves into Phase 3 of its development cycle.
## đź“– Main Content:
### Changing Site-Wide Elements
One of the most persistent challenges with the Site Editor has been understanding the global impact of seemingly local changes. For instance, users may not realize that editing a synced pattern, replacing an image in a pattern, or adjusting the menu in a header template part could have site-wide consequences. These changes are not always communicated clearly, which can lead to unexpected results. There’s also confusion around the Styles panel, which controls global styles but appears alongside block settings, leading users to mistakenly assume they’re only adjusting one block.
### Understanding Where Elements Are Used
Users often need more visibility into where their edits will be applied. There’s a growing demand for features that show which templates use a given template part, or which patterns are impacted by a particular change. This could clarify the local vs. global changes and help users understand the scope of their edits, especially in complex sites with multiple interconnected templates and patterns.
### Navigating Inconsistencies in the Interface
There are many inconsistencies in the current WordPress interface, especially around icon usage and default options. The same icon might represent vastly different concepts, leading to confusion. For example, the "settings" icon has been repurposed in various parts of the editor, creating ambiguity about its function. Similarly, the "revisions" icon is used to mean "resetting" a template, merging two distinct concepts without sufficient explanation.
### Challenges in Editing and Styling
Inherited values, locked elements, and confusing placeholders are all significant friction points. Users struggle to understand what they can and cannot edit, and why certain elements are locked. The interface does not always communicate these limitations effectively, leading to frustration. Improving the clarity of editing modes, inherited styles, and locking mechanisms is crucial for a better user experience.
### Looking Forward to Phase 3
As WordPress enters Phase 3, which will focus on collaboration and workflows, these issues become even more critical. Users need clarity on how changes made by one user will impact the rest of the site. Additionally, managing permissions and understanding the effects of collaborative edits will be key to ensuring a smooth user experience in multi-user environments.
## 🗒️ Notes:
- Persistent confusion about global vs. local changes.
- Users need more visibility into where templates, patterns, and styles are used.
- Interface inconsistencies with icons and default settings create friction.
- Clarity around inherited values and editing limitations is necessary for improving the user experience.
## đź“– References:
- WordPress Blog
## 🗣️ Paraphrase:
1. **Original**: "Whether it’s editing a synced pattern to add a new block, replacing an image in a pattern with an override in place, or changing out your menu in a header template part, there are a lot of scenarios where folks are traversing changes that might echo far beyond what they might understand."
**Paraphrased**: "Editing a synced pattern, swapping an image with an override, or altering the menu in a header template part can result in changes that extend across the site in ways users might not fully realize."
2. **Original**: "There are a fair number of related requests for more information including seeing which templates use a given template part, seeing what templates pages use in Site Editor > Pages, displaying the templates in which a navigation block is used, and seeing all instance of where a pattern is used."
**Paraphrased**: "Many users have asked for more visibility, such as showing which templates utilize a specific template part, which templates are tied to certain pages, or where patterns and navigation blocks are used across the site."
## đź“° Newsletter:
📢 **WordPress Site Editing Challenges and the Road Ahead!**
As WordPress gears up for Phase 3, it’s time to reflect on the friction points users face in the Site Editor. From confusing global vs. local changes to inconsistencies in icons and inherited styles, there’s plenty of room for improvement. If you’ve found yourself puzzled by site-wide edits or locked elements, you’re not alone! Phase 3 will address many of these concerns, focusing on collaboration and better workflows. Keep an eye on these updates and explore what’s to come in the future of site editing! Read more [here](https://wordpress.org).
## âś… Action Items:
- Evaluate current issues with site-wide changes and consider solutions for clearer communication of global impacts.
- Explore ways to provide more transparency on where elements like templates, patterns, and styles are used.
- Focus on improving the consistency of icons and interface elements in WordPress.
- Clarify the editing and locking mechanisms to reduce user confusion.
## đź§Ş Hypotheses:
- **Hypothesis 1**: Providing clearer visibility into global vs. local changes will reduce user confusion and improve satisfaction.
- **Hypothesis 2**: Consistency in interface elements and iconography will lead to a smoother and more intuitive user experience.
### 📊 Methodology:
- **Data Collection**: Survey WordPress users on their experiences with global vs. local changes and interface consistency.
- **Analysis**: Use qualitative feedback to identify common pain points and test solutions in beta versions.
### âť“ Questions:
- How can WordPress better communicate global vs. local changes to users?
- What are the most confusing elements of the current interface, and how can they be improved?
- How can WordPress Phase 3 streamline collaborative editing and reduce confusion around permissions and global edits?
### đź”® Future Research:
- Investigate user satisfaction with collaborative features in Phase 3 of WordPress.
- Study the effectiveness of improved visibility and consistency in reducing user frustration during site edits.
### đź’ˇ Implications:
Addressing these friction points will not only improve user satisfaction but will also set the stage for a smoother transition into Phase 3, where collaboration and multi-user environments will be critical. A clearer interface and better communication of changes will help reduce errors and enhance the editing experience.
### âś… Logical Validity:
- **Sound Inductive Reasoning**: The author identifies common user pain points, using them to argue for specific improvements in the WordPress Site Editor.
- **Balanced View**: The post doesn’t focus on milestones but rather areas of friction, offering a well-rounded critique aimed at fostering improvements.
## 🎯 Conclusion:
As WordPress progresses into Phase 3, addressing key friction points in the Site Editor—such as global vs. local changes, interface consistency, and understanding inherited values—will be crucial. These improvements will pave the way for a more intuitive, collaborative editing experience for users and teams alike.
<!-- deep-read:sections end -->
đź“„ **Full text:** ![[Full Document Contents/Articles/Overlapping Problems|Overlapping Problems, agm]]
## Highlights
- This tension goes beyond just adding content and also includes Styling changes. [I’d love to see the Styles panel improved](https://github.com/WordPress/gutenberg/issues/53483) and perhaps moved out of being available when editing more individual “pieces”, whether a template or pattern, to help communicate the global impact. Here are just a few examples of all of the various scenarios where, no matter where I go, I could make site wide changes with limited friction to communicate what I might be doing. To this day, I still hear from folks that it took them a long time to realize this Styles option impacted the entire site, especially when it lives next to block settings. ([View Highlight](https://read.readwise.io/read/01j7fgw20mwjsypre9hz2tqsby))
- Note: 1. How can we better communicate the potential global impact of changes made in the Site Editor to help users understand the interconnectedness of their edits?
2. In what ways can we improve visibility into where items are used across the site to enhance user decision-making when making changes?
3. What strategies can be implemented to reduce confusion around icons and inherited values in the editing interface, ensuring that users clearly understand their options and restrictions?