|
| 1 | +=== OneDesign === |
| 2 | +Contributors: rtcamp, parthnvaswani, up1512001, singhakanshu00, danish17, aviral-mittal, vaishaliagola27, rishavjeet, vishal4669, iamimmanuelraj |
| 3 | +Donate link: https://rtcamp.com/ |
| 4 | +Tags: OnePress, Pattern distribution, Pattern sync, OneDesign, Design consistency |
| 5 | +Requires at least: 6.2.6 |
| 6 | +Tested up to: 6.8 |
| 7 | +Stable tag: 1.0.0 |
| 8 | +Requires PHP: 7.4 |
| 9 | +License: GPLv2 or later |
| 10 | +License URI: https://www.gnu.org/licenses/gpl-2.0.html |
| 11 | + |
| 12 | +Synchronize block patterns across multiple WordPress sites. Create once, deploy anywhere with centralized pattern management for enterprise teams. |
| 13 | + |
| 14 | +== Description == |
| 15 | + |
| 16 | +OneDesign is a powerful pattern synchronization solution designed for enterprises managing multiple WordPress sites or multisite networks. It enables you to define block patterns on a Dashboard site and distribute them to consumer sites, maintaining design consistency across your entire network. |
| 17 | + |
| 18 | +**Why OneDesign?** |
| 19 | + |
| 20 | +Managing multiple websites—whether for different brands, regions, or languages shouldn't mean reinventing the wheel each time. Instead of designing layouts from scratch for each site, OneDesign lets you create once and deploy anywhere, in just one click. |
| 21 | + |
| 22 | +Built for enterprise teams, OneDesign unifies your design, editorial, and development processes across all web properties. The result? A shared design system that dramatically cuts down on development, decision-making, and opportunity costs—saving you hundreds of thousands of dollars. |
| 23 | + |
| 24 | +**Key Benefits:** |
| 25 | + |
| 26 | +* **50% Time Savings:** Eliminate redundant pattern creation across multiple sites |
| 27 | +* **Brand Integrity Guardian:** Prevent design drift and maintain consistent branding |
| 28 | +* **Cost Reduction:** Reduce operational costs through centralized pattern management |
| 29 | +* **Design Governance:** Control which patterns can be used across sites |
| 30 | +* **Scalable Growth:** Connect unlimited sites without multisite limitations |
| 31 | + |
| 32 | +**Core Features:** |
| 33 | + |
| 34 | +* **Dual Architecture Support:** Works with WordPress multisite networks and standalone installations |
| 35 | +* **Secure API Integration:** REST API with unique authentication keys for safe pattern transfer |
| 36 | +* **Intuitive Pattern Browser:** Full-screen admin interface with search and filtering functionality |
| 37 | +* **Batch Operations:** Deploy multiple patterns across multiple sites simultaneously |
| 38 | +* **Pattern Status Monitoring:** Track deployment success and synchronization across connected sites |
| 39 | +* **Pattern Management:** View, apply, and remove patterns from the centralized dashboard |
| 40 | + |
| 41 | +**Pattern Management Actions:** |
| 42 | + |
| 43 | +* Browse and preview all available patterns from Dashboard site |
| 44 | +* Search and filter patterns by categories and names |
| 45 | +* Apply selected patterns to specific consumer sites |
| 46 | +* Remove patterns from specific sites |
| 47 | +* Bulk operations for multiple pattern deployment |
| 48 | +* Real-time pattern synchronization status tracking |
| 49 | + |
| 50 | +**Perfect for:** |
| 51 | + |
| 52 | +* Enterprise WordPress deployments with multiple brands or regions |
| 53 | +* Agencies managing multiple client sites |
| 54 | +* Organizations requiring consistent design standards |
| 55 | +* WordPress multisite networks |
| 56 | +* Teams using Full Site Editing (FSE) themes |
| 57 | + |
| 58 | +== Installation == |
| 59 | + |
| 60 | +1. Upload the OneDesign plugin files to the `/wp-content/plugins/onedesign` directory, or install the plugin through the WordPress plugins screen directly |
| 61 | +2. For multisite installations, network activate the plugin through the 'Plugins' menu in WordPress |
| 62 | +3. For single site installations, activate the plugin through the 'Plugins' menu in WordPress |
| 63 | +4. Set up one site as the "Dashboard Site" for centralized pattern management |
| 64 | +5. Configure other sites as "Consumer Sites" |
| 65 | +6. Copy API keys from each Consumer Site's settings page |
| 66 | +7. Register all Consumer Sites in the Dashboard Site with their respective: |
| 67 | + * Site name |
| 68 | + * URL |
| 69 | + * Logo |
| 70 | + * API key |
| 71 | + |
| 72 | +== Frequently Asked Questions == |
| 73 | + |
| 74 | += How are patterns transferred between sites? = |
| 75 | + |
| 76 | +Patterns are transferred securely via WordPress REST API with unique authentication keys, ensuring that all pattern data, including blocks and settings, are properly synchronized. |
| 77 | + |
| 78 | += Can I customize which patterns are available to specific sites? = |
| 79 | + |
| 80 | +Yes, you can control which patterns are applied to each consumer site by managing the selections in the Design Library interface. |
| 81 | + |
| 82 | += Are there any limits to how many patterns I can sync? = |
| 83 | + |
| 84 | +There are no hard limits on the number of patterns you can sync, but performance may vary depending on your server resources and the complexity of the patterns. |
| 85 | + |
| 86 | += Can I remove patterns from specific sites? = |
| 87 | + |
| 88 | +Yes, you can remove patterns from specific sites directly through the dashboard interface by accessing the applied patterns list for each site. |
| 89 | + |
| 90 | += What themes are supported? = |
| 91 | + |
| 92 | +OneDesign works with Full Site Editing (FSE) compatible themes. All sites should use the same theme with consistent variables and variations for optimal results. |
| 93 | + |
| 94 | += Does this work with WordPress multisite? = |
| 95 | + |
| 96 | +Yes, OneDesign supports both WordPress multisite networks and standalone WordPress installations connected via API. |
| 97 | + |
| 98 | += What happens if a block used in a pattern isn't available on the target site? = |
| 99 | + |
| 100 | +All blocks used in the patterns must be available on all target sites. Ensure consistent block availability across your network for proper pattern synchronization. |
| 101 | + |
| 102 | +== Screenshots == |
| 103 | + |
| 104 | +1. OneDesign Dashboard - Centralized pattern management interface |
| 105 | +2. Pattern Browser - Search and filter patterns with live previews |
| 106 | +3. Site Registration - Configure Dashboard and Consumer sites |
| 107 | +4. Bulk Operations - Select and apply patterns to multiple sites |
| 108 | +5. Disabled Sites - Which is already having currently selected patterns |
| 109 | + |
| 110 | +== Changelog == |
| 111 | + |
| 112 | += 1.0 = |
| 113 | +* Initial release |
| 114 | +* Centralized pattern management dashboard |
| 115 | +* Support for WordPress multisite and standalone installations |
| 116 | +* Secure REST API with authentication keys |
| 117 | +* Pattern browser with search and filtering |
| 118 | +* Bulk pattern operations |
| 119 | +* Pattern status monitoring and synchronization |
| 120 | +* Full Site Editing (FSE) theme compatibility |
| 121 | + |
| 122 | +== Upgrade Notice == |
| 123 | + |
| 124 | += 1.0 = |
| 125 | +Initial release of OneDesign. Perfect for enterprises managing design consistency across multiple WordPress sites. |
| 126 | + |
| 127 | +== Requirements == |
| 128 | + |
| 129 | +* WordPress 6.2.6 or higher |
| 130 | +* PHP 7.4 or higher |
| 131 | +* Full Site Editing (FSE) compatible theme across all sites |
| 132 | +* Same theme variables and variations across network |
| 133 | +* All blocks used in patterns must be available on all sites |
| 134 | +* REST API enabled on all sites |
| 135 | + |
| 136 | +== Support == |
| 137 | + |
| 138 | +For support, feature requests, and bug reports, please visit our [GitHub repository](https://github.com/rtCamp/OneDesign). |
| 139 | + |
| 140 | +== Contributing == |
| 141 | + |
| 142 | +OneDesign is open source and welcomes contributions. Visit our [GitHub repository](https://github.com/rtCamp/OneDesign) to contribute code, report issues, or suggest features. |
| 143 | + |
| 144 | +Development guidelines and contributing information can be found in our repository documentation. |
0 commit comments