Content & blog

The Content area of your workspace lets you model collections, save validated records and publish them as a blog on your website.

01

Create a collection

Open Content in your workspace, choose a website and select New collection. Add fields of these types: short text, long text, number, yes / no, date, web link (HTTPS) and related record (from the same site). Use blog fields adds a ready-made set: title, excerpt, body, author and date.

02

Save records as private drafts

Records are validated against their collection before they are saved, and stay private to your workspace. Saving a record does not change your live website. If you change a collection’s fields, the change must stay compatible with saved records; values are never silently converted or dropped.

  • Up to 20 collections, 32 fields per collection and 1,000 records per site.
  • Each record can hold up to 64 KiB of content.
03

Prepare a snapshot

A snapshot freezes the exact saved versions of up to 100 records you select. Nothing is published by preparing a snapshot; it gives your site a stable, reviewable set of content to use.

04

Set up the website blog

In Website blog, choose a prepared snapshot and its collection, then map fields onto your blog: an index title and description, posts ordered newest date first, and post addresses by slug (/blog/your-post). A blog can hold up to 20 posts. Saving the setup does not publish anything.

05

Preview and publish

Select Preview website to see your saved pages together with the generated blog pages, then Publish website. The blog index lives at its path (for example /blog), every further ten posts at /blog/page/2, /blog/page/3 and so on, and each post at its own address. Posts are listed in your sitemap and carry their own canonical link and social preview. Later record edits stay private until you prepare a new snapshot, update the setup and publish again; restoring an earlier version from history brings back that version’s blog pages too.

On the Business plan, REST API keys reach your content too, with an OpenAPI reference.

Next guideTeams & roles