CMS Platform
Content models that make every channel structurally sound
Design the shape of your content once. Deploy it to web, mobile, commerce, and every API consumer without rebuilding schema per system.
0+Content platform projects delivered
REST
+ GQLBoth APIs generated from every content type automatically
+ GQLBoth APIs generated from every content type automatically
0msSchema migration time when adding a new field type
0xChannels delivered from a single content model
The content structure problem
Most teams are modeling content with the wrong tools
When structure lives in spreadsheets and Slack threads, every channel reinterprets the same content differently. That inconsistency costs you velocity and accuracy.
The old way
- Content type definitions scattered across Google Docs and tribal knowledge
- Every new channel requires a developer to re-map fields manually
- Validation errors discovered after publish, not before
- No versioning means broken schemas break live consumers silently
With Redefine
- Visual content type builder: no code required to define schemas
- One model, all channels: REST and GraphQL consume the same schema
- Schema-level validation blocks incomplete records before they reach editors
- Versioned content models with a full change history: roll back without fear
Content modeling process
From blank schema to live content in four steps
Every content model you build in Redefine is immediately consumable by your front-end team and instantly commerce-aware.
1
Step 1
Define your content type
Name the model, set field types and validation at the schema level.
2
Step 2
Add relational references
Nest content types and link fields to live PIM product records.
3
Step 3
Set validation rules
Mandatory fields, completeness gates, and publish-blocking schema checks.
4
Step 4
Publish to all channels
REST, GraphQL, web, mobile, and kiosk: all from one content model.
Content Type Builder: New Type
Type name
Editorial Article
titleShort TextRequired
slugURL SlugRequired
bodyRich TextOptional
hero_imageMedia AssetRecommended
Add field
Relational References: Editorial Article
Referenced content types
related_products
References: PIM Product (live)
author
References: Author Profile
category
References: Category Taxonomy
related_products pulls live inventory counts from PIM: no sync required
Schema Validation Rules
Completeness gate before publish
title must not be emptyEnforced
slug must be URL-safe, uniqueEnforced
hero_image min 1200px wideEnforced
author reference must be publishedWarning
2 records blocked from publish: missing required fields
Channel Delivery: Editorial Article
Delivering to 4 channels from one model
REST API
Live · 42msGraphQL
Live · 38msMobile App
Live · CDNDigital Kiosk
Live · CDNWhat you get
Every capability your content schema needs
Flexible content type builder
Build any content type your brand needs: Articles, Product Features, Landing Sections, FAQs, Author Profiles, with typed fields chosen from a visual palette. No code, no YAML, no migrations to run.
- Short text, long text, rich text, number, boolean, date, JSON
- Media asset fields with automatic format conversion
- Repeatable field groups for arrays and lists
- Field-level localization overrides per locale
- Reference other content types: Author inside Article, Slide inside Carousel
- Reference live PIM product records: no sync, no copy-paste
- Circular reference detection at save time
- Polymorphic reference fields for flexible slot architecture
Nested and relational content references
Structure your content like your business, not like a flat document. Nest types inside types, reference live commerce data, and build component libraries that non-developers can reuse without breaking the schema.
Structured data and schema validation
Set rules that enforce content quality at the schema layer: before an editor can save or route to review. Catch missing hero images, empty slugs, and invalid references at the point of entry rather than after publish.
- Required field enforcement: records cannot progress without complete fields
- Field-level format validation (URL, email, min and max values, regex)
- Publish-gate integration: schema errors block workflow progression
- Full field-level and type-level change history
- Restore any prior schema version without migration scripts
- Named versions and release notes per schema change
Content versioning and revision history
Every change to a content model is tracked. Your team can roll back a schema change, compare field revisions, and understand exactly what changed and who changed it, without opening a support ticket.
Reusable content components and blocks
Define a Button, a Callout, or a Stat Block once. Reference it from any content type across every site and locale. Your design system and your content model stay in sync because they share the same component library.
- Component library shared across all content types and sites
- Override individual component fields at the page level
- Composable slot architecture for page builder integration
Customer proof
Structured content at scale: real outcomes from one model
Regional Nursery Group
Headless Commerce and CMSA California-based nursery serving thousands of plant enthusiasts online, with complex seasonal catalog data and multi-channel content needs.
0
percent uptime at seasonal peak: zero schema-related outages
0
channels delivered from a single content model after migration
Problem
The legacy platform could not support advanced filtering, faceted navigation, or plant-specific attributes. Content types were defined without validation, causing inconsistent data flowing to the storefront and mobile app.
Resolution
A headless architecture was introduced with structured content types for plant species, care guides, and seasonal collections. Relational references linked content records to live product variants, and schema validation blocked incomplete records before they reached any consumer.
Why Redefine
Three things other headless CMS platforms cannot match
01
Commerce-aware content types
A standalone headless CMS stores content in a silo. Redefine content types can reference live PIM product records directly: so a Landing Page type can include a Product Spotlight field that pulls real inventory, pricing, and availability without any custom integration work.
Marketers publish product-aware landing pages. Developers do not build sync scripts. Both groups win.
02
One governance engine across CMS and commerce
Content approval in Redefine is part of the same workflow engine used for order approvals, PIM enrichment, and form routing. A rule set defined once applies everywhere: you do not configure separate approval gates in five tools.
That means a single policy can gate a product page update and a B2B price change simultaneously, with one audit log.
03
B2B-aware multi-site content scoping
Content types in Redefine can be scoped per site, per B2B account group, or per dealer tier. A Dealer Portal site can inherit the same Article type as your main site but restrict which records are visible based on account role: no custom API logic required.
This capability does not exist in standalone CMS tools that are unaware of your B2B account hierarchy.
Schema graph
See every relationship in one view
Every content type and reference rendered as a live graph: entities as nodes, relationships as labelled edges, integrity checks running continuously.
API delivery
Your content model becomes an instant API
Save a content type and Redefine exposes it immediately via REST and GraphQL. No schema migrations, no deployment: your front-end team can start querying within seconds.
REST endpoint
GET /api/content/editorial-article
Authorization: Bearer <token>
Response 200
{
"id": "art_7f3k",
"title": "Spring collection",
"slug": "spring-2025",
"related_products": [...]
}
Authorization: Bearer <token>
Response 200
{
"id": "art_7f3k",
"title": "Spring collection",
"slug": "spring-2025",
"related_products": [...]
}
GraphQL query
query {
editorialArticle(
slug: "spring-2025"
) {
title
hero_image { url }
related_products {
sku price inStock
}
}
}
editorialArticle(
slug: "spring-2025"
) {
title
hero_image { url }
related_products {
sku price inStock
}
}
}
Live delivery stats
CDN hit rate97.4%
Average response time38ms
Schema versions active3
Channels consuming4
Frequently asked
Common questions about content modeling
Speak with a Redefine content architect before you commit to anything.
Speak With A Content ArchitectContent modeling software lets your team define the structure, fields, and relationships of your content before any copy is written. You build reusable content types: like Article, Product Feature, or Landing Section, with typed fields, validation rules, and relational references, so every piece of content is predictable, structured, and ready for any channel.
Content types in Redefine are commerce-aware. A marketer can build a content type that references a live PIM product record, meaning product data flows directly into landing pages and editorial content without any custom API work or sync script.
Yes. Redefine's content type builder uses a visual, no-code interface. Architects and content strategists can define fields, validation rules, and nested references without writing code. Developers then consume these models through the REST or GraphQL API.
A standalone headless CMS stores content in isolation. Redefine's content modeling sits inside a unified platform alongside PIM, OMS, and commerce: so a content type can reference live inventory, account-tier data, or B2B pricing rules natively, without middleware or custom integration work.
Yes. Every content type supports mandatory field rules, field-type validation, and completeness checks before a content record can enter the review or publish workflow. Invalid or incomplete records are blocked at the schema level, not discovered after publish.
Is this right for you?
A good fit, and when it is not
Good fit when
- You operate more than one channel (web, mobile, kiosk, marketplace) from the same content base
- Your content needs to reference live product data, pricing, or inventory without a sync script
- Non-developers need to define and manage content structure independently of engineering
- Content quality gates and approval workflows need to run alongside commerce approvals
Not a fit if
- You only publish to a single static website with no API consumers
- Monthly content output is fewer than 10 records and schema complexity is minimal
- You have no plans to connect content to a commerce, order management, or product information management system
Not sure? Tell us your situation and we'll be straight with you.
Get started
Build content models your whole team can trust
See how Redefine content modeling connects to your commerce stack, your channels, and your governance policy. No commitment. No pitch.
Form
Call within 48 hours · proposal in 3 days · Sprint 1 within 1 week of sign-off
Brief received
We'll review your workflow and send a scoped proposal within 3 business days.
Response within 48 hours
Proposal in 3 days
180+ projects completed
Full code ownership on handoff
See it working
Build content models your whole team can trust
See how Redefine content modeling connects to your commerce stack, your channels, and your governance policy in a single demo.
Submit your brief → call within 48 hours → scoped proposal in 3 days → Sprint 1 within 1 week of sign-off
No commitment. No pitch.
