CMS Architecture for SaaS Websites

Why SaaS sites need structured content

SaaS marketing sites evolve constantly. New features ship, pricing changes, blog posts drive organic traffic, and the changelog keeps users informed. A structured CMS means your marketing team can update all of this without engineering bottlenecks.

Recommended collections

Features

• Name (text, required) — feature name.
• Description (rich text) — what it does and why it matters.
• Icon (image) — feature icon or illustration.
• Category (select) — core, analytics, integrations, security.
• Screenshot (image) — product screenshot showing the feature.
• Available on (multi-select) — which pricing tiers include this feature.
• Order (number) — display order on the features page.
• New (boolean) — flag recently launched features.

Blog posts

SaaS blogs drive a huge share of organic traffic:

• Title (text, required) — keep under 60 characters for SEO.
• Body (rich text, required)
• Excerpt (text) — for card displays and meta descriptions.
• Author (reference) — link to team members.
• Category (select) — product, engineering, company, guides.
• Tags (multi-select) — for filtering and related posts.
• Featured image (image)
• Publish date (date)
• SEO title (text) — override for search results.
• Meta description (text) — 150-160 characters.

Changelog

Keep users informed about product updates:

• Title (text, required) — e.g., "Dark mode support".
• Date (date, required)
• Description (rich text) — what changed.
• Type (select) — new feature, improvement, bugfix, deprecation.
• Image (image) — screenshot of the change.
• Related feature (reference) — link to the feature this updates.

Integrations

• Name (text, required) — e.g., "Slack", "Zapier".
• Logo (image, required)
• Description (text)
• Category (select) — communication, analytics, CRM, developer tools.
• Documentation URL (url)
• Featured (boolean)

Testimonials

Social proof drives conversions:

• Quote (text, required)
• Person name (text, required)
• Title (text) — their job title.
• Company (text)
• Company logo (image)
• Rating (number)
• Use case (select) — which product use case this testimonial supports.

Key relationships

• Blog posts → Authors (single reference)
• Changelog → Features (single reference, optional)
• Features → Pricing tier (multi-select)
• Testimonials → Use case (select)

Tips for SaaS CMS

1. Changelog is essential — even a simple date + title + description collection builds trust with users.
2. Gate features by tier in your CMS — use a multi-select field on Features to track which pricing plans include each feature. This powers comparison tables.
3. Blog SEO fields are not optional — add SEO title and meta description fields from day one. Retrofitting SEO is painful.
4. Use "featured" booleans generously — for homepage features, top testimonials, and highlighted integrations.
5. Integration logos in a collection — not hardcoded. You will add integrations frequently.