Use a small vocabulary

Markdown represents common document structures with ordinary text characters. A heading, a list, and a descriptive link are enough for many working notes. Begin with those elements rather than relying on complex extensions that may render differently in another editor.

Try a project note with a title, a purpose paragraph, a decisions section, and a next-actions list. The file should remain understandable even when opened in a basic text editor. That is a useful test of portability.

Make links understandable later

A link labeled “reference” does not tell your future self what you expected to find. Use the document title or a short description of the relevant topic. Record an access date when the state of a changing resource matters to your work.

For local links, choose a consistent folder structure and test what happens when the collection is moved. Copying one note without its attachments can break the context. Keep essential explanations in text rather than relying entirely on a screenshot.

Separate working notes from published material

A rough note can contain unanswered questions and provisional conclusions. Mark those clearly. Before publishing, verify claims, check links, and remove private information. Plain text is easy to copy, so treat the boundary between a private folder and a public repository deliberately.

Once a month, open a few older notes and ask whether they still explain what happened. Add missing context when you can. The value of a note is not that it was captured; it is that it remains useful when the original conversation is no longer fresh.

Further reading

Original sources and related references. These links lead to independent websites; inclusion does not imply a partnership or endorsement.

Browse the complete resource shelf →