This article is part of our series on Visor. For the full picture, start with The choice behind every website.
Few organisations run just one website. There is the main site, and then sites for campaigns, departments, brands, regions, and particular audiences. Many were built at different times, by different teams, on different platforms.
On most platforms, each of those sites is its own project, with its own servers, updates, design, and way of approving content. The cost and the work grow with every site, and the sites drift apart in how they look and how well they are protected.
Many websites, one platform
Visor runs many websites on the same platform. Each website is kept separate, with its own content, settings, design, and editors, and one site's content stays with that site. Underneath, all of them share the same platform and the same central controls.
That lets each website be run by its own team. The communications team can run the main site while a department runs its own, and permissions can keep each team to its own site.
Rules set once, for every site
The rules for security, design, and publishing are set once and applied to every site from one place. Every site sits behind the same protection and gets the same security testing. Sites can share the same approval steps. The platform handles patching and upgrades for every site on it.
Build a template once
Templates make this practical. A team builds a website once, with its layouts, building blocks, and approval steps, and sets it as the template for the group. New websites are created from it.
Each new site starts with the right structure, design, and rules in place, and can still have its own look. A site's design is a theme that loads on its own, so sites can share every building block and look nothing alike. A brand that needs its own colours gets its own theme, with no code changes.
Because consistency comes from the starting point, there is less to check afterwards. Setting up the fiftieth website takes no more effort than the fifth.
Public sites and private ones
Not every website is for the public. Staff portals, internal knowledge bases, and sites that hold sensitive information often have to stay inside a private network, for security or regulatory reasons.
Visor can run in the cloud or inside your organisation's own private network, often called an intranet, and each site can run where it needs to. Internal sites get the same platform, controls, and way of working as public ones, so teams don't need a separate system for them.
Help with the first sites
Setting up a template for a whole group is easier with people who have done it before. Forward Deployed Engineers from Xtremax can join your team to build the first sites, set up templates for your organisation, or deliver a large set of websites faster.
In short
Visor runs many websites on one platform. Each site keeps its own team, content, and look. The rules for security, design, and publishing are set once for all of them, templates give every new site the right start, and each site can run in the cloud or inside your own network.
Read more: The choice behind every website, Inside the Visor CMS: approvals, building blocks, and data, and What a website costs after it goes live.
