Make a note the home for a thread
A note can be a meeting record, a project brief, a research trail, or a place to think out loud. Start with a title that tells future-you what the note is about. Then write enough context that the note can stand on its own.
When a thought becomes a decision, record both the decision and the reason behind it. When it becomes work, add a task rather than moving the action into a separate list.
Use structure when it earns its keep
Margin keeps familiar writing patterns and adds meaning where it helps. A light structure is often enough:
| When you are... | Try... |
|---|---|
| Capturing context | Use a heading and a few clear paragraphs. |
| Recording a next action | Write a task so it can be tracked later. |
| Grouping a theme | Add a tag such as #client or #research. |
| Keeping a reference nearby | Link a file or related note from the same workspace. |
Keep related material close
Images and files can live alongside the note they support. Related notes can link to one another with the note-link syntax, so a decision can point directly to the project or task that depends on it.
Client kickoff
#client
Decision
Use the existing onboarding flow.
Related notes
[[Onboarding review]]
[[Project scope]]Keep the files portable
Your workspace stays on your machine in plain text files. That means you can back it up, move it, or use your existing file-management habits without handing your notes to a hosted database.
For a deeper look at the syntax that makes this possible, visit the Margin format guide.