Most organisations that run many websites got there one project at a time. Consolidation brings those sites onto one platform, and it goes more smoothly when a few questions are settled before the first site moves.
Which sites can share a template?
Sites that share layouts and widgets can be built once and cloned. In Visor, each site keeps its own record, URLs, and theme, and the frontend loads the theme at runtime, so sites can share every component and still look nothing alike. Group sites by the content they carry, and treat brand differences as themes.
Who approves what?
List the kinds of content each site publishes and who signs each one off. A product page may need legal review, and a news post only an editor's. Visor workflows are drawn on a canvas and assigned per collection and per site, and a filter rule can send one category down a longer path. Agree the paths first and you won't redraw them later.
Where do the sites have to run?
Some sites can run in the cloud. Others hold content that has to stay on your network. Visor runs in both, in containers on AWS or inside your intranet, so the answer can differ from site to site.
What happens on your busiest day?
Find the day each site gets the most traffic: a results release, a product launch, a service disruption. Sites whose content changes when it is published can be built as static files and served from the edge, where a spike meets cached pages. Keep server rendering for pages that change on every request.
Who runs it after launch?
Someone has to patch servers, renew certificates, upgrade the CMS, book security tests, and answer incidents. On Visor's Website Platform, patching, certificates, and CMS upgrades are handled by the platform, security tests are booked in a portal, and incidents go to a service desk. Xtremax forward deployed engineers can also join your team for the build. Decide early which of these you want to keep in house.
