A ready-made website to start from.
A Next.js template that resolves layouts, loads widgets, and applies themes. Build it as static files or render per request.
Visor API
Content and settings
Layout
Matched by name
Widgets
Fill the placeholders
Theme
From the site record
Page
SSG, SSR, or ISR
Everything you need to start a site.
Pages put together from your settings in Visor
The template fetches a route's page data and layout configuration from the Visor API, renders the layout's placeholder zones, and fills each one with its widgets. Two routes cover the whole site: the home page and a catch-all for every other page.
- Content, layouts, and site settings from one API
- Layouts matched by name, widgets by collection
- A home route and one catch-all route
- Fallbacks for anything unmatched
Seven layouts and 40+ widgets to start with
Platform layouts cover the home page, inner pages, articles, group pages, and side navigation. Platform widgets cover headers, navigation, banners, cards, statistics, accordions, breadcrumbs, and search. Your own layouts and widgets sit beside them as ordinary React components.
- Platform and site folders for each
- A site widget replaces a platform widget of the same name
- Client variants for live editing in Studio
- Register the name in Studio and editors can use it
Change the look without changing the code
Each theme is a scoped SCSS folder compiled to its own stylesheet, with colours, radii, and other tokens set as CSS variables. Widgets read the tokens, so a new theme needs no component changes.
- One folder per theme
- Tokens as CSS custom properties
- Loaded at runtime from the site record
- The default theme as the fallback
Build pages ahead of time, or on each visit
One environment variable picks SSR, SSG, or ISR at build time. A static build outputs HTML files you can serve from Nginx, S3, or any static host, including under a sub-path. The dev server always renders live content.
- SSR and ISR build to a Node server
- SSG exports plain HTML files
- Sub-path hosting for static builds
- Media from the API or your own CDN
Questions
Something else? Ask us directly.
The template is Next.js and it is the supported starting point. Content is served through the Visor API, so other frontends can read it as well.
More in CMS.
CMS overviewSee Headless architecture on a real site.
Book a demo and we'll walk you through it.