Marketing teams running campaign microsites

The problem

Marketing needs a site for a product launch, another for a regional rollout, another for a three-month campaign, and a landing page for a trade event next week. Every one goes through engineering. Each becomes a small codebase someone maintains long after the campaign ends. Because they get built in a hurry by whoever is free, they drift off-brand: different type, different buttons, different footer. Six months on, nobody is certain which of the fourteen live microsites still need to exist.

The solution

Let marketing stand up and run sites themselves, assembling pages from a component library that engineering owns.

How Visor handles it

- Developers build widgets, layouts, and themes once. Those become the approved building blocks, and they are the only pieces available to assemble from.

- Page Builder lets editors compose pages by arranging widgets, setting hierarchy and navigation, previewing, then publishing. Routine updates need no ticket and no deploy.

- Layouts, themes, and widgets carry across sites, so a new microsite inherits the design system it should already look like.

- New sites get provisioned as tenants on the running platform. AI-assisted setup handles the scaffolding, including converting design slices into Visor-conforming layouts and widgets.

What changes

Launches stop waiting on engineering availability. Off-brand drift becomes hard to produce, because the components available to editors are the sanctioned ones. Retiring a campaign site is a platform action with a clear owner. Engineering time moves to the component library that every site draws on.