Skip to main content

Launch the Next Site as a Configuration Change, Not a Project

Stack9 Experience is a headless CMS with 100+ pre-built, brand-approved page sections and 50+ configurable settings per site. A new microsite reuses the Web App Template you already have — typically 2 to 10 days for infrastructure, with your team populating content in parallel.

Multi-Site Without Multi-Codebase

A content home per site

Each portal or microsite gets its own content repository — pages, media, assets and site settings, isolated from every other site — while content editors manage them all through one shared editorial workflow.

Rebrand through configuration

50+ Site Settings fields cover branding, colour schemes, social links and navigation menu sets, consumed directly by the component library. A new brand identity is applied by setting values, not by writing front-end code.

Pages as stacks of governed sections

A Page Slice is a reusable, full-width content section; a page is a stack of them. Editors compose from 100+ pre-approved sections, so brand consistency is enforced by the platform rather than caught in manual review.

Ordinary web development, not a certified specialty

Web App Templates are standard HTML, JavaScript and CSS. Any competent web developer — yours or ours — can extend one. There is no proprietary templating language and no vendor-certified partner requirement.

Migration that is verified page by page

My Plan Manager moved 1,000+ pages onto Stack9 Pages automatically, with an automated pixel-by-pixel visual audit against the source before go-live. The source platform there was WordPress — the same method applies to other legacy CMSes.

Content first, presentation later

Stack9 Pages supports API-driven content consumption, so a site can adopt Stack9 for content management without committing to Stack9’s own front-end rendering. Useful when a migration needs to be phased.

Standing Up a New Site

1

Create the content repository

A new Stack9 Pages repository becomes the site’s self-contained content home.

2

Apply brand and navigation

Site Settings and the existing component library carry the brand across. No custom front-end development for a new look.

3

Reuse the Web App Template

The front end you already run is reused. No new codebase, no new vendor engagement, no new integration effort.

4

Provision the infrastructure

Domain, SSL certificate and — where authentication is required — SSO configuration. Typically 2 to 10 days. That timeframe covers infrastructure and technical setup only; your business users populate content in parallel on their own timeline.

Digital Experiences at Scale

Multi-brand networks, member organisations and migrated estates.

Multi-tenanted dealership website network with per-brand theming
Eagers Automotive — a 450+ dealership site network on Stack9 Experience, with inventory, email marketing and intranets on the same platform. Partnered since 2020.
Stack9 Pages editor showing a page composed from governed Page Slices
Pages are composed from 100+ brand-approved sections. Off-brand pages are prevented structurally, not reviewed after the fact.
Public website with an integrated jobs board and membership area
Landscape Queensland — public website, jobs board, membership and subscription management and CRM, consolidated onto one platform.

Governed by Design — and We Will Say So Plainly

Stack9 Pages is a headless CMS. There is no free-form, WYSIWYG page design outside the governed component library. That is deliberate — it is what makes brand consistency a platform guarantee — but if your team expects unrestricted visual design, you should know before you buy, not after.