Blog Sections Open
Multisite Patterns in Evolution CMS with One Shared Database
A shared-database multisite can work, but only if content ownership, URL boundaries, and synchronization rules are designed from the start.
the original question asked whether several subdomain-based sites could share one Evolution CMS database while duplicating or reusing much of the same content.
What Makes Shared-Database Multisite Hard
- One update may affect several sites at once.
- Navigation and URLs must remain site-specific.
- Shared and local content need clear boundaries.
- Permissions and editorial ownership become more complex.
Good Principle
Treat multisite as a content architecture problem, not just a database trick. The key question is not whether one database is possible, but whether the rules for shared versus site-specific content are clear enough to keep the system maintainable.
Assigning Sequential Classes to Wayfinder Menu Items
How to generate class names like mm1, mm2, and mm3 automatically in Wayfinder output instead of hard-coding them in static HTML.
Saving eForm Leads into the Database
A practical pattern for recording eForm submissions in a database for later export or follow-up work.