Product
Model the things only you have.
Singletons for a homepage or settings. Collections for anything there are many of.
Start free
How it works.
-
Start from a template
A homepage hero, pricing plans, testimonials, a contact block. Rename a field or delete one, then keep going.
-
Choose singleton or collection
One of a thing, or many of a thing. That is the only structural decision there is.
-
Fill it in like a form
A calendar for a date, a picker for a link, a real editor for a body. Nobody types an id.
- Fourteen field types
- Text, rich text, images, galleries, dates, choices, booleans, numbers, references, links.
- Links that survive a rename
- Point at an article or category by id. The slug resolves on every read.
- Reference other entries
- A product has a category. A page has a menu. Resolved one level deep.
- Filter and sort
- On any field the type declares, validated against the schema.
- 14
- field types, each with the right control
- 2
- kinds of type: one of a thing, or many
- 6
- things a link field can point at safely
Frequently asked questions
What people ask about custom content before they commit to it.
What is the difference between a singleton and a collection?
A singleton is one of a thing: your homepage hero, your contact details. A collection is many of a thing: case studies, services, team members. That is the only structural decision you have to make.
Can one entry point at another?
Yes. A reference field points at another entry and resolves it one level deep on read, so a product can carry its category without you fetching twice.
What happens if I rename something a menu points at?
The menu follows. A link field stores an id, not a URL, and the current title and slug are resolved on every read. Renaming a category cannot break a navigation built on one.
Start with a project and a key.
Free while we are in beta. Paid plans when we ship them, and never a surprise bill.