Model your content
A good content model is the contract between your editors and your code. Mojimoto gives you typed fields, reusable components, and references so the structure stays honest no matter who edits it.
Types come in three kinds
- Collection - many reusable entries browsed as a list (Pages, Posts, Team members).
- Single - exactly one entry, opened directly (Navigation, Site settings).
- Component - a building block edited inside its parent and hidden from the main list (a nav item, a page section).
Choose the right field for the job
Every field is typed, so a date is a date and a number is a number. That means fewer defensive checks in your front end and fewer surprises in production. The core field types are short text, long text, rich text, number, boolean, date, select, media, reference, slug, location and JSON.
Add a Slug field to any collection so its entries are addressable by a stable, URL-friendly key rather than a numeric id.
Compose pages from components
Rather than one giant page type, give the page a Blocks field with a palette of block types - Hero, Feature grid, Quote - and let editors add, reorder and remove sections inside the entry. The page stays flexible without ever going off-model, and your front end renders each block by its type. Save References for content that genuinely belongs to more than one page, like a shared call to action.
The Blocks guide walks through the block syntax, the editor and rendering blocks in React.
Link entries with references
A Reference field connects one entry to another - an article to its author, a product to its category. When you read content, references resolve to the linked entry inline (one level deep by default), so you get the related data in the same response without a second request.
# depth=2 inlines references two levels deep (max 3) curl "https://your-domain.com/api/v1/your-project/documents?depth=2" \ -H "Authorization: Bearer mjmt_your_public_read_token"
Give a page a Blocks field so editors add, reorder and remove typed sections inside the entry, then render each block by its type.
Query published content by type, slug and locale, paginate, sort, and resolve references - all from one REST endpoint.
Author an entry per locale against the same model, request a language from the API, and fall back gracefully when a translation is missing.