Content types and relations

In the site admin, open Content Types to define the collections and fields your content uses.

Checked against the product’s code on 7 November 2026.

Content Types is EmDash’s screen for defining content structure, also called its schema. A content type describes a collection of records, such as posts or a custom directory. It is different from a Composer page type, which supplies a page recipe.

Create a collection

You need an Admin role to create a collection. The copilot offers structure changes only to Admins and still asks for approval. Editors can ask it to list registered content types or read their structure.

1. Open Content Types.
2. Choose New Content Type.
3. Fill in Label (Singular).
4. Fill in Label (Plural).
5. Review Slug.
6. Add a description if useful.
7. Turn on Routable for entries that need public addresses. It requires a slug before an entry can be published.
8. If the entries need public addresses, set URL Pattern for them.
9. Review its navigation settings.
10. Review its editing lock.
11. Review its SEO options.
12. Review its comments options.
13. Choose Create Content Type.

If you configured public addresses, add and publish a test entry, then check its address before you rely on the pattern.

Some collections are Defined in code. The screen identifies settings that need a code file change. On a hosted Praxis site, ask Amadalis support instead. On hosted Praxis, creating or changing block types and adding block fields, which hold structured page components, are refused.

Open the collection’s schema to add fields. System Fields are separate from Custom Fields. Check the hosted limits above before choosing a field type.

1. Choose Add Field.
2. Choose a supported field type.
3. Enter its Label.
4. Review its Slug.
5. Review Required where offered.
6. Review Unique where offered.
7. Review Searchable where offered.
8. Fill in the settings offered for that type.
9. Choose Add Field to save it.
10. Check the field in the collection’s schema.

Field deletion has its own confirmation.

Relate two collections

Start from Content Types in the site admin navigation. If you are editing a collection’s schema, return to Content Types in the navigation first. Relations shows relationships between content types.

1. Choose Relations beside New Content Type.
2. Choose New Relation.
3. Choose the type under Links from.
4. Choose the type under Links to.
5. Review the names for each side.
6. Review the stable Slug.
7. Choose how many records may be linked from each side.
8. Choose Create Relation.
9. Check the relation in the list.

A relation supplies shared rules for reference fields, which link records to other records. Its content types and slug cannot change after creation. Review the impact shown before changing limits or deleting a relation. Deleting a field can also offer to remove the relationship it uses; read that additional consequence.

Reorder the content types

An Admin can change the order content types appear in for everyone editing the site. This changes navigation order, not content, fields or tables.

1. Ask the copilot to list the current content types.
2. Ask it to show that complete list in your intended order.
3. Read Reorder the content types? and the before and after lists.
4. Choose Save this order if they are right.
5. Open Content Types to check the saved order.

A partial list is refused. If the set changes while the card is open, ask for a new proposal. The receipt’s Undo puts back the previous order while nobody has reordered again. See Content type requests.

Keep content and schema changes distinct

Creating a collection does not fill it with records. Hiding it from navigation removes shortcuts, not its underlying content or API access.

Use a Collection index page to list entries from an existing collection. Creating that page does not create the collection or its records.

Deleting a content type also deletes all content in its collection and every relation it takes part in. Read Delete Content Type? carefully before you confirm. The copilot pauses for supported schema writes; relation creation and editing use EmDash’s own screen.

Your next step

Create a draft in the collection you configured. Use Pages, posts and media to review the content before publishing.