Markdown adds a small amount of structure to plain text. A heading marker or list marker is part of the source file; a renderer decides how to display it. Keep the note useful even when no preview is available.
Copy the original template
Download the note template. It includes a topic, date, context, key points, decisions, actions, and references. Replace bracketed prompts with real permitted content. The example reference link is explicitly a placeholder to replace, not an asserted source for your note.
# Workshop preparation
Date: 2026-11-17
Context: Fictional planning exercise
## Key points
- Keep the first session small.
## Decisions
- Use the Cedar room if availability is confirmed.
A # plus a space creates a level-one heading in CommonMark. Two hashes create a subsection. A hyphen plus a space starts a bullet item. Blank lines help separate blocks.
Compare source and rendering
Open the rendered note example on this site. It builds the heading, bullet list, literal filename, code block, and official reference from the exact completed example Markdown file. Compare that display with the full source shown beside it. Both read the same file; the completed example uses level-two headings to fit inside the practice page. The practice page is static; it does not upload or render your private notes.
Use backticks around a short filename or literal marker so it is read as code rather than accidental formatting. Use [label](destination) for a link, then inspect the destination and make the label meaningful.
Keep extensions distinct
The downloaded template uses - [ ] for actions. Task-list checkboxes are a GitHub-flavored Markdown extension, not a universal interactive control in every CommonMark renderer. Some viewers show [ ] as ordinary text. You can still maintain it manually as a status marker.
Do not assume Markdown supports every table, checkbox, embedded HTML, or diagram syntax in the same way across applications. Use the smallest subset your actual editor and recipient support.
Save and reopen
Save as a UTF-8 .md file, close it, and reopen it. Check that the source remains readable, the date has a clear meaning, and the action owner and due date are explicit when known. A preview that looks tidy can still hide an unresolved placeholder or a broken link.
A consistent template reduces the effort of starting a note. It does not replace deciding what was actually agreed, and it should not force every short note to contain empty sections. Remove sections that serve no purpose for the particular note.
References & scope
These official references support the software instructions. Practice documents are original, fictional teaching examples; labels can vary by release.
- CommonMark quick reference
Heading, list, link and code syntax in CommonMark. - About READMEs
README purpose, headings, and relative file links. - About tasklists
GitHub task-list markers - [ ] and - [x] are an extension, not universal interactive Markdown.