A Markdown template is a starting note with just enough structure to prompt the next useful thought. Because it is plain text, you can keep it in a folder, copy it between tools, and edit it without a special template system.
The best template is usually shorter than the finished note. Empty sections create work and make the important parts harder to see.
Meeting note
# Design review
**Date:** 2026-09-25
**People:**
## Decisions
-
## Open questions
-
## Next actions
- [ ] Action — owner
Write decisions in complete sentences. A transcript records what was said; a useful meeting note records what changed, who owns the next step, and what remains unresolved.
Project note
# Project name
One sentence describing the outcome.
## Now
- [ ]
## Later
-
## Decisions
- 2026-09-25 — Decision and reason
## References
-
Keep Now small enough to scan. Move finished work to a dated log or check it off rather than continually rewriting history.
Daily note
# 2026-09-25
## Focus
-
## Notes
-
## Carry forward
- [ ]
A date in ISO order (YYYY-MM-DD) sorts naturally in a file list. If a title matters more than chronology, use both: 2026-09-25-editor-review.md.
Decision record
# Decision: Short title
**Status:** proposed
**Date:** 2026-09-25
## Context
What constraint or problem led here?
## Decision
What are we choosing?
## Consequences
What becomes easier, harder, or newly required?
This format separates the decision from the discussion around it. Future readers can understand the reason without reconstructing a chat history.
README
# Project name
What this project does and who it is for.
## Start
```sh
command-to-run
```
## Structure
- `docs/` — project notes
- `src/` — source
## Contributing
How to propose a change.
When placing a fenced code block inside another example, use a longer outer fence or copy the template from the live tool to avoid closing the example early.
Keep templates portable
Use ordinary headings, paragraphs, lists, links, and fenced code for the parts that must travel well. Task lists and tables are common extensions, but their rendering can differ. App-specific properties, queries, or front matter can be useful; document them so the plain text still makes sense elsewhere.
Use relative links when the referenced file moves with the note:
[Research](../research/reader-interviews.md)
Use descriptive link text and image alt text. Those small choices help when the note is read as source, rendered on the web, or used with assistive technology.
Try a template
The live Markdown preview includes Field note, Meeting, Project, README, and Blank examples. Choose one, edit it inline or beside the rendered preview, and download the result as a .md file. Draft saving remains off unless you enable it on that device.
After using a template three times, remove any section you consistently leave empty. Add a prompt only when its absence caused you to miss useful information. That review keeps a template helpful instead of ceremonial.