Document Types
updated
A document type groups documents that share fields — an ADR, a runbook, an API endpoint. It decides which Custom Fields its documents have, their order and layout. It never changes a document’s text.
A project without types works as before: every field applies to every document.
Create a type
Project Admins open the project’s Overview → Document types → New document type, and set a Name, an icon, an Alias, a short Description (also read by AI assistants), its Fields and a Layout. The alias is what the type is called in frontmatter and can’t be changed later.
Select the star on a type to make it the Default for new documents — applied to new documents created without a type, from the web, the CLI or an AI assistant.
Change or delete
A document’s type is the Document type row of its properties. Changing it never deletes values: those that no longer apply are kept under Not in this type and return if the type is set again. Deleting a type takes it off its documents but keeps their values.
In your repository
A document’s type is the template: key in its frontmatter. meldoc pull writes it and meldoc push applies it. See Frontmatter Parameters and Document Templates.
What’s next?
Custom Fields — Define the fields a type uses.