Markdown, media, diagrams, and tasks

Quire combines a visual collaborative editor with Markdown portability. Use semantic structure first: headings for hierarchy, lists for related items, and tables only when rows and columns clarify a comparison.

Markdown essentials

Common Markdown patterns work as expected:

## Deployment checklist

- Confirm the release owner
- Review the migration plan
- [ ] Notify support

See the [runbook](https://example.com/runbook).

Use one page title and begin body sections at level two. Short paragraphs and descriptive link labels improve scanning and accessibility.

Images and files

Attach an image when visual context materially improves the document. Add meaningful alt text that communicates the image's purpose. Quire stores document images with the document and supports optimized display variants.

Collection files are useful for source materials such as PDFs or spreadsheets. Agents can list, view, attach, move, delete, and restore files when their authorization permits it.

Tables and diagrams

Tables are appropriate for repeated fields or exact comparisons. Mermaid code blocks are useful for flows, sequences, and relationships. Keep an explanatory sentence near every diagram so the instructions remain complete if a reader cannot see it.

| Owner | Decision | Status |
| --- | --- | --- |
| Maya | Launch date | Approved |

Tasks

Task lists record lightweight completion state inside a document. Comment action items are different: they have a discussion thread, an assignee, and completion behavior. Use task lists for page-local checklists and action items for accountable collaboration.