Skip to content
Use cases

Your project sets the shape.

Articles, products or portal content: you define the data model. Reusable components connect your content to the application.

Editorial & magazines

Structure articles, authors and topics. Manage translations and publish content independently of layout.

  • Preview, reference editing and language provenance

Content type: Article

Title
text
Content
richtext
Cover image
image
Autor
reference → Author

Content type: Author

Name
text
Bio
longtext
Photo
image

No ready-made starter for this model. Set it up in the CMS; the App Builder then generates an app that displays this content.

See the editorial workflow

Catalogs & information portals

Present products, offers or places with images and related information.

  • Your own field names and data models

Content type: Product

Name
text
Description
richtext
Price
number
Image
image
Manufacturer
reference → Manufacturer

No ready-made starter for this model. Set it up in the CMS; the App Builder then generates an app that displays this content.

Explore the building blocks

Multiple clients & brands

Separate spaces and environments create clear editorial workspaces.

  • Roles and access per workspace

Content type: Page

Title
text
Hero image
image
Sections
richtext

You set up the same model again in each client space — content types aren't carried over between spaces automatically.

Discuss your project

Existing websites

Keep your frontend and use smartcms as a structured content source. Plan integration and migration around your actual data model.

Content type: Post

Title
text
Slug
slug
Content
richtext
Published
date

No starter needed: your existing frontend reads this content through the delivery API.

Start with the API

Let’s get to know your project.

From the first model to everyday publishing.

Request access
Use cases — smartcms