Not every note serves the same purpose. Choosing the right structure helps you find information more quickly later.

Instead of using one template for everything, match your note structure to the task.

Daily notes provide a simple record of what you plan to do, what you've completed, and anything worth remembering.

# 15 July 2026

## Today's Priorities

- Finish API documentation
- Review pull requests
- Publish release notes

## Notes

- Customer requested PDF export.
- Documentation needs updated screenshots.

## Follow-up

- Schedule design review.
- Reply to support tickets.

Result

Best for

• Personal planning
• Daily journals
• Task tracking
• Work logs

Why this structure works: Keeping priorities, notes, and follow-up actions separate makes it easier to review your day without searching through long paragraphs.

Meeting notes should focus on decisions and actions rather than recording every conversation.

# Weekly Team Meeting

**Date:** 15 July 2026

## Attendees

- Emma
- Liam
- Noah

## Discussion

- Reviewed roadmap
- Planned next release
- Discussed documentation updates

## Decisions

- Launch scheduled for next Monday.
- API changes approved.

## Action Items

- Emma: Update documentation.
- Liam: Prepare release build.
- Noah: Test deployment.

Result

Best for

• Team meetings
• Client calls
• Project reviews
• Sprint planning

Why this structure works: Separating discussion from decisions and action items makes it easy to scan for who owns what, without rereading the whole conversation.

Organise information by topic instead of writing one continuous block of text.

# Introduction to Databases

## Key Concepts

- Relational databases
- Primary keys
- Foreign keys

## Important Terms

- Table
- Record
- Query

## Example

A customer table stores information about each customer using a unique identifier.

## Questions

- How do indexes improve performance?

Result

Best for

• Lecture notes
• Exam revision
• Course summaries
• Self-study

Why this structure works: Splitting concepts, terms, and open questions into their own sections lets you review key ideas quickly without rereading the entire lecture.

Research notes should capture facts, observations, and useful references in one place.

# Markdown Editors Research

## Objective

Compare popular Markdown editors for technical documentation.

## Findings

- Editor A focuses on simplicity.
- Editor B includes live preview.
- Editor C supports collaborative editing.

## Questions

- Which editor offers offline support?
- Which one has the best export options?

## Next Steps

Test each editor with a real documentation project.

Result

Best for

• Research projects
• Market analysis
• Technical investigations
• Content planning

Why this structure works: Recording the objective, findings, and open questions separately keeps research actionable instead of turning into an unstructured pile of notes.

Instead of highlighting everything, record ideas you'll want to remember later.

# Clean Code

## Main Ideas

- Write meaningful names.
- Keep functions small.
- Reduce duplication.

## Favourite Quote

"Leave the code cleaner than you found it."

## Personal Takeaways

Improve naming consistency in future projects.

## Related Topics

- Refactoring
- Code reviews

Result

Best for

• Book notes
• Article summaries
• Course readings
• Personal libraries

Why this structure works: Reading notes become far more valuable when they include your own takeaways rather than copied passages you'll never revisit.

Keep project information together so progress is easy to track.

# Website Redesign

## Goal

Improve navigation and mobile usability.

## Current Status

In Progress

## Completed

- New homepage
- Updated colour palette

## Next Tasks

- Accessibility review
- Performance testing

## Risks

Navigation changes may require updated documentation.

Result

Best for

• Product projects
• Freelance work
• Personal side projects
• Team initiatives

Why this structure works: Combining goals, status, progress, and risks into one document makes it easy to update throughout the project and gives anyone reading it the full picture at a glance.

Knowledge base notes focus on one idea at a time, making information easier to organise and connect.

# Markdown Tables

## Summary

Markdown tables organise structured information into rows and columns.

## Common Uses

- Documentation
- Feature comparisons
- Reports

## Related Notes

- Markdown Lists
- Markdown Links
- Markdown Formatting

Result

Best for

• Personal wikis
• Team knowledge bases
• Obsidian or Logseq vaults
• Documentation hubs

Why this structure works: A short summary, common uses, and related notes make each entry easy to scan and link into a wider network of notes.

When collecting ideas, don't worry about perfect organisation. Capture everything first, then organise it later.

# Blog Ideas

- Markdown shortcuts
- Documentation checklist
- README best practices
- API examples
- Common Markdown mistakes

## Promising Ideas

- Interactive cheat sheet
- Markdown workflow guide

## Next Action

Create outlines for the strongest ideas.

Result

Best for

• Idea capture
• Content planning
• Product brainstorms
• Retrospectives

Why this structure works: Brainstorming notes should encourage creativity rather than perfect formatting. A raw list followed by a short filter step keeps the process fast.

Taking notes is easy. Finding useful information weeks or months later is the real challenge. A good note should answer a question without forcing you to remember when or why you wrote it. As a simple rule, imagine opening one of your notes six months from now — if it still makes sense without additional context, you've probably documented it well.

Organise Notes Around Topics, Not Dates#

Many people create hundreds of notes named after dates. While daily notes are useful, long-term knowledge is easier to manage when notes are organised by topic.

Projects/
├── Website Redesign.md
├── API Documentation.md

Research/
├── Markdown Editors.md
├── Static Site Generators.md

Meetings/
├── Product Planning.md
├── Sprint Review.md

Daily notes can still exist, but important ideas should eventually move into dedicated topic-based notes where they're easier to find and update.

One Idea Per Note#

Smaller notes are often more useful than one large document covering multiple subjects. Instead of creating a note called Programming Notes, split it into focused notes such as Markdown Tables, Markdown Lists, Markdown Links, Markdown Images, and Markdown Code Blocks. Focused notes are easier to search, reference, and expand over time.

Connect Related Notes#

Notes become more valuable when they reference each other. For example, a note about Markdown tables could naturally link to Markdown Formatting, Markdown Documentation, README Examples, and a Markdown Cheat Sheet. Linking related topics creates a network of information instead of a collection of isolated documents.

Record Decisions, Not Just Information#

Good notes explain why something was chosen, not only what happened.

Instead of writing:

Changed the navigation.

Write:

Changed the navigation to reduce the number of clicks required to reach documentation pages.

Future-you, or your teammates, will understand the reasoning without revisiting old discussions.

Review and Refine Your Notes#

Notes don't need to be perfect when they're first written. It's often better to capture ideas quickly and organise them later. During regular reviews you can:

• Merge duplicate notes.
• Add clearer headings.
• Remove outdated information.
• Link related topics.
• Archive notes you no longer need.

A few minutes of maintenance keeps a knowledge base useful as it grows.

Writing Everything in One Note#

Large notes become difficult to search and update. If a document keeps growing, it's usually a sign that it should be divided into smaller, topic-focused notes.

Using Vague Titles#

Titles should describe the content clearly.

Instead of: Meeting

Use: Sprint Planning – Authentication Improvements

Clear titles make searching much easier.

Mixing Tasks with Reference Notes#

Action items and long-term knowledge serve different purposes.

Task: Update homepage copy.

Reference: Brand writing guidelines.

Keeping them separate helps you find the right information at the right time.

Forgetting to Record Sources#

When collecting research, include links, book titles, or article names while the information is still fresh. A useful idea loses value if you can't remember where it came from.

Never Revisiting Old Notes#

Notes become more useful when they're reviewed and improved. Instead of constantly creating new notes, spend time refining existing ones and connecting related ideas.