Quiverblocks chooses Diggama to deliver 200+ articles every month

Free tool · Content Model Generator

Your content model, in one minute.

Pick the kind of site you run, adjust what it needs, and get every content type, field and reference, ready to build. As a diagram, JSON or TypeScript.

01 · Start from

02 · Your site needs

Content types

Fields

References

Click a dot to make a field required or optional · × to remove it

Tick at least one need above to see its content types.

With Diggama

From this model to a working API, today.

In Diggama, each content type above is a blueprint: the same fields, the same types, the same references. Create them in the editor or start from the matching templates, and your editors get forms while your developers get a REST API.

  • Twelve field types, the same ones as this generator
  • Ready-made templates for every need on this page
  • Change a field later without a migration script

No credit card · Cancel anytime

Blueprints 5 + New blueprint
Post → Author, Category 9 fields
Author 6 fields
Category 4 fields
Landing Page → Section 8 fields
Site Settings 9 fields

Post · fields

title Text

Required

slug Slug

From title

author Reference

→ Author

body RichText

Headings, images

FAQ

Content models, explained

What is a content model?

The list of things your site is made of (pages, posts, authors, products) and the fields each one has. It is the first thing to get right in a headless CMS: editors fill the fields, developers query them, and nobody pastes layout into a text box.

Where do these content types come from?

From the templates of the Diggama marketplace, built and used by real teams, plus two types every site needs: settings and navigation. When two needs share a type name, the second one gets a prefix so nothing collides.

Can I use the JSON with another CMS?

Yes. It is plain JSON: a list of types, each with named, typed fields. Most headless CMSs have the same building blocks under other names, and the TypeScript types work with any API that returns these fields.

What does a grey reference mean?

The field points to a type that is not in your model yet, for example a Post that references an Author when the Team need is off. Add the need that holds it, or remove the field.