I have an idea/suggestion for syncing layouts/blocks in a WAAS.
When creating a website template (Network-Site, WP Ultimo Template) the creator (WP-Superadmin, Cloud Manager) creates a project in the Brizy Cloud and makes it a template project (e.g. by a simple checkbox). When creating the template page(s) in WP, he stores blocks and layouts as usual. Nice to have would be own libraries (layout landing pages, layout contact, layout portfolio, block hero, block team, etc.).
After the client created his website based on a template (wp ultimo or not) and opens the editor, Brizy recognizes (based on the website URL/ID, userID...) the existence of the template account and that the current client is not a manager and from now he has read-only access to the pre-populated layouts and blocks. In addition, a personal (sub-)account is automatically created for the client in the background (access data are automatically assigned and remain unknown to the client, connect/disconnect/sync is hidden, sync always takes place automatically) and the client can save its own layouts and blocks - ideally in an own library, otherwise the existing single library is supplemented. It is important that each client (besides the template contents) only gets access to his personal layouts/blocks and cannot see those of the others. In case of connecting problems, the manager/superadmin should have a reconnect option.
Using the cloud sync function should also be possible with Brizy-Whitelabel.
Thus, the superadmin/cloud manager can create a set of layouts/blocks for each website template and later continuously edit and add to them, which can be readonly accessed by any client that gets a website based on this template (for example with WP-Ultimo). Ideally organized in an own library. Each client can still save and use their own layouts/blocks without having to register, log (editor, browser) or press any sync-buttons.
Please sign in to leave a comment.