Visor
One CMS to Build and Manage Enterprise-grade Websites with AI

Yes. Visor is engineered for multisite management, letting you launch and manage multiple websites from a single hub. The Sites module is the core tenant data store, where each site entry represents a tenant and holds its own configuration, including CMS URL, developer preview URL, active theme, and frontend linkage. Settings modules are restricted to Admin roles only, and a site must be created before its frontend can be configured.

AI works as a development assistant inside your IDE rather than a one-click migration tool. The convert-html skill converts static HTML slicing into ready-to-use layouts, theme, and widgets, so developers do not have to manually translate markup into React components. It can be run from Claude Code, Antigravity, VS Code, or Kiro, and it reads the HTML, CSS/SCSS, and JS files placed in the source folder and maps sections of markup to theme, layouts, and widgets following DSS Base Template conventions. The output is a working starting point, and naming, content bindings, and edge cases may still need manual adjustment before registering it in Visor Studio.

No. Page Builder is the core module for content editors, providing a built-in drag-and-drop interface for assembling pages with widgets and acting as the central configuration point for slugs, layouts, status, and content blocks. Editors build, update, preview, and publish page content without writing code. Widgets are dragged into placeholder areas and configured through a settings form on each widget.

Editors can only use what developers have built and registered. Widgets are React components that receive content from Visor, split into platform widgets shipped with the template and site widgets added per project. Each widget exports a configuration object that Visor Studio uses to register it, and the fields defined in that configuration are what appear in the editor's form. A corresponding widget definition must be created in Visor Studio before editors can add it to pages through Page Builder.

Yes, and without changing application code. A workflow definition is a JSON-based configuration describing the states and transitions content can move through, for example Draft to Review to Approved to Published, and acts as a reusable template that can be assigned to one or more content collections. You can model anything from a simple two-step approval to a complex multi-stage editorial pipeline. States and actions are composed in a drag-and-drop builder that generates the JSON automatically, and a workflow assignment then activates the definition for a collection.

No. The Search module lets you configure which fields in a collection are indexed, and you can map multiple collections into one search configuration so results carry all mapped data and give the frontend everything it needs in a single response. A Search Engine entry then defines the search endpoint the frontend consumes, with search mappings attached to it. Multiple mappings can sit behind one engine entry, giving the frontend a unified search endpoint across the collections you have indexed.

Visor is headless, so content management is separate from the frontend. The DSS Base Template is a Next.js application that acts as the frontend head, fetching content from Visor Studio through the DaaS API, resolving layouts and widgets from configuration, and rendering the final HTML. It follows a config-driven rendering pattern where a route resolves its page and layout config from Visor, the layout renders placeholder zones, and each placeholder renders its assigned widgets. Three rendering modes are supported, SSR, SSG, and ISR, switched through an environment variable and a prebuild script.

Edits are stored as versioned records first, and the item is promoted to the main version when you transition its status, for example to Published. Publishing Execution then gives a read-only log of every static site generation build trigger on the platform, recording when each build ran and its context, which is useful for monitoring build activity. For pre-launch review, Dev Mode routes the Visor preview to your local Next.js server instead of the live deployment, so content changes appear in real time during development.