Understand document types, templates, contents, slots, and rules
Understand how a document definition controls structure and why an optional slot can be skipped without failing the deliverable.
In this article
- Document type
- Expected deliverable family, such as letter, project sheet, curriculum, or specification.
- Template
- Structure selected for the type and context; rules can include, exclude, or order its contents.
- Content
- Block or section defined in the template, with text, instructions, child contents, or references.
- Slot
- Value expected during the workflow and supplied by data, a source, or generation; it can be required or optional.
- Rule
- Condition evaluated from context to select a template or content.
Practical guidance
Templates describe the structure a configured workflow can assemble. Their rules and values are not a user-facing guarantee that every possible section will appear. When the workflow asks for clarification, answer with confirmed information or identify the gap; a plausible invented value can change both the narrative and the selected sections.
Advanced tips
When a section is absent, compare the project context with the section’s intended applicability before treating the omission as a formatting bug. Ask the template owner to inspect unexpected selection behavior rather than modifying governed rules through the request.
Was this article helpful?