Planned Roadmap Items

[aviral-mittal]

• Onboarding Check
  The prerequisites to use OneDesign are: all participating websites must have a fully Site Editor–compatible theme, with variables and blocks using the same names, and running WordPress version 6.2.6 or above. Ideally, when connecting websites, if any of these prerequisites are not met, the plugin should either refuse the connection or warn the Dashboard owner. Additionally, during plugin installation, it should prompt the user to configure the Dashboard and Consumer Site roles to minimize errors caused by misconfiguring consumer sites as dashboard sites and vice versa.

• Multisite network compatibility without API keys
  Currently, even the subsites of a multisite network need to use API keys to consume patterns. For multisite, we need to make all subsites in a network selectable by default.

• Two way sync
  Currently, the model is that all new patterns are created in the Dashboard site and consumed on a need basis by consumer sites. However, if a pattern is specifically created on Consumer site, it should be able to sync with Dashboard site, for distribution to other sites.

• Media assets to be handled for consumer sites
  Right now, if media assets are part of a pattern, then consumer sites still refer to the Dashboard sites media file. This needs to be handled better so that in case placeholder images are deleted from Dashboard site, then also patterns don't look broken.

• UI fixes to avoid scroll when selecting a consumer site for a pattern
  Currently, to check which Consumer site has what patterns, there is a horizontal scroll. However, a UI/UX fix is needed to make navigation easier when there are a lot of consumer sites.

• Template Sync
  Allow templates to be synced across any post type/page in the shared network of Consumer sites

[vinay070403]

OneDesign Plugin – Problem Statement & Solutions

Problem Statement:
The OneDesign plugin currently faces limitations in onboarding, multisite support, pattern/media syncing, and UI/UX, which can lead to configuration errors, broken patterns, and reduced flexibility for users managing multiple WordPress sites.

---

Identified Issues & Proposed Solutions

Issue	Effect	Proposed Solution
1. Onboarding & Setup	Users may misconfigure Dashboard vs Consumer sites; plugin may connect incompatible sites.	Implement pre-checks for theme compatibility, variable/block naming, and WordPress version. Prompt users to configure Dashboard and Consumer Site roles during installation.
2. Multisite API Key Requirement	Subsites require separate API keys, adding setup burden.	Enable automatic detection of subsites in a multisite network and allow them to consume patterns without API keys.
3. One-Way Pattern Sync	Patterns created on Consumer sites cannot sync back to the Dashboard.	Implement two-way sync: allow Consumer-created patterns to sync to Dashboard and distribute to other sites.
4. Media Asset Handling	Patterns on Consumer sites reference Dashboard media; deleting media breaks patterns.	Copy or replicate media assets to Consumer sites when syncing patterns to ensure self-contained assets.
5. UI/UX – Pattern Selection Scroll	Horizontal scrolling needed to see consumer site patterns; poor usability with many sites.	Redesign UI to avoid scrolling. Options: collapsible lists, responsive grid, or searchable dropdown for consumer sites.
6. Template Sync Limitation	Templates cannot be synced across arbitrary post types/pages.	Enable template syncing across any post type or page, increasing flexibility in content distribution.

---

Summary

By addressing these issues, OneDesign will become:

• User-friendly: Proper onboarding and role guidance.
• Multisite-ready: Subsites consume patterns seamlessly.
• Flexible: Two-way pattern sync and template sharing across all post types.
• Robust: Media assets handled locally, preventing broken patterns.
• Efficient: Improved UI for managing patterns across many consumer sites.

---