Tech Collectives · Tutorials

Markdown & Folders: Build a Knowledge Base You Actually Own

Plain text files and simple folders are the most durable, portable way to capture what you know. They're also the perfect fuel for any AI tool you choose. Let's learn the whole system in one sitting.

A hands-on tutorial · No software to install to start · Try every example live

1What is a Markdown file?

A Markdown file is just a plain text file, the same kind Notepad or TextEdit makes, with one small superpower: a handful of everyday symbols quietly mean "formatting." A # becomes a heading. A - becomes a bullet. Wrapping a word in **stars** makes it bold.

You write in readable text. Markdown apps render it as clean, formatted pages. But the file underneath stays simple, and that's the whole point. These files end in .md (short for Markdown) instead of .docx or .pdf.

The mental model: a .md file is to a Word document what a recipe card is to a plated meal. Lightweight, easy to copy, easy to hand to anyone, and it works the same whether you're cooking today or ten years from now.

Here's the same content, side by side. What you type on the left, what you see on the right:

You type this
You see this
# My Meeting Notes ## Decisions - Launch in **September** - Pilot with *3 student teams* > Remember: start before you feel ready.

My Meeting Notes

Decisions

  • Launch in September
  • Pilot with 3 student teams
Remember: start before you feel ready.

Notice you can read the left side perfectly well even without rendering. That readability is what makes Markdown last.

2Why bother? Five reasons.

You already have Word, Google Docs, Notion. Why learn another way to write? Because Markdown optimizes for something those tools don't: durability and freedom.

It outlives software

A .md file opens in anything, on any device, forever. No subscription, no "this format is no longer supported."

You own it

The file lives on your computer, not in someone's cloud. Back it up, move it, sync it however you like.

It's AI-ready

Clean text with light structure is exactly what language models read best. Your notes become reusable context.

It's fast

No menus, no mouse. Hands stay on the keyboard, so capturing a thought takes seconds, not a launch screen.

It's searchable

Plain text means Spotlight, grep, and your editor can all find any word instantly across thousands of notes.

It plays well with others

Markdown is the shared language of GitHub, Obsidian, Notion, Slack, and most AI tools. Learn it once, use it everywhere.

3The syntax, by example

Here's the honest truth: you can learn 90% of Markdown in five minutes, and you'll use the same six or seven symbols every day. Below is everything most people ever need.

Headings

Add # signs before a line. One for the biggest, more for smaller, like outline levels.

# Heading 1  (the title)
## Heading 2  (a section)
### Heading 3  (a sub-section)

Emphasis

**bold text**
*italic text*
~~strikethrough~~

Lists

Bullets use -. Numbered lists use 1.. Indent with spaces to nest.

- First idea
- Second idea
  - A supporting detail
1. Step one
2. Step two

Checklists for tasks

- [ ] Draft the pitch
- [x] Book the room
- [ ] Email the team

Links

Square brackets for the words, parentheses for the address.

[Tech Collectives](https://techcollectives.com)

Quotes & dividers

> A quote or a callout worth remembering.

---  (three dashes make a horizontal line)

Code or exact text

Wrap in backticks `like this` to keep text literal. Handy for file names, commands, or anything that shouldn't be "prettified."

# TitleHeading level 1
## SectionHeading level 2
**word**Bold
*word*Italic
- itemBullet list
1. itemNumbered list
- [ ] taskCheckbox (unchecked)
- [x] taskCheckbox (checked)
[text](url)Link
> textQuote / callout
---Horizontal divider
`text`Inline code / literal text

Keep this cheat sheet handy. Within a week, you won't need it.

4Live playground: try it now

This is the best way to learn: type on the left, watch it render on the right. Nothing leaves this page, and there's nothing to install. Tap a button to load an example, then edit it freely.

my-note.md · live preview
Markdown (edit me)
Preview
Try this: change a # heading, check a box by turning [ ] into [x], or add a bullet. The preview updates as you type. That instant feedback is exactly how Markdown apps feel.

5Organizing with folders

One note is useful. A thousand notes you can't find is a junk drawer. The magic of a Markdown system isn't any single file. It's how folders turn a pile of files into a place you can think.

A folder is just a labeled container. Folders can hold files and other folders, so you build a tree: broad at the top, specific as you go down. The goal is simple: future-you should be able to guess where something lives.

A few organizing principles

One proven starter structure

A popular, low-effort approach sorts everything by how actionable it is rather than by topic:

My Knowledge Base/ ├── 1-Projects/ # active, has a deadline & goal │ ├── launch-fall-cohort/ │ │ ├── plan.md │ │ └── meeting-notes.md │ └── nist-grant/ │ └── draft.md ├── 2-Areas/ # ongoing responsibilities │ ├── teaching.md │ └── health.md ├── 3-Resources/ # topics & references you collect │ ├── ai-tools.md │ └── reading-notes.md └── 4-Archive/ # done or dormant, out of the way └── spring-cohort.md

This four-bucket pattern, sometimes called "PARA" for Projects, Areas, Resources, Archive, is just one option. The numbers keep folders in a sensible order. Use it, tweak it, or invent your own. The system should serve your thinking.

The rule that matters most: when you create a note, the only question is "where will I look for this later?" Put it there. If two answers feel equally right, pick one and move on. You can always search.

6From folders to a second brain

Here's where it gets exciting. Once your notes live in plain Markdown files inside sensible folders, you have something bigger than storage. You have a system for thinking, doing, and synthesizing. A few habits turn the folder into a living tool:

  1. Capture fast, organize later. Keep one inbox.md or an Inbox/ folder. Dump thoughts there the moment they arrive. Sort them into the right folder weekly.
  2. One note per idea. Give each meeting, project, book, or person its own file. Small notes are easy to link, move, and reuse.
  3. Use consistent note shapes. A meeting note always has Attendees / Decisions / Next steps. Predictable structure makes notes scannable, and easy for AI to parse.
  4. Connect ideas. Link related notes together. Over time the links reveal patterns you'd never have spotted in separate documents.
  5. Review and synthesize. Once a week, skim your folders and write one note that connects the dots. That's where real thinking happens.
A note on Obsidian: tools like Obsidian sit on top of exactly this: a folder of Markdown files on your computer. They add live linking between notes, a visual map of how ideas connect, search, and tags, without locking your files away. Because the underlying files stay plain .md, you can adopt Obsidian later (or leave it) without redoing anything. The folder is the database. That's the beauty of starting with Markdown: you're never trapped.

7Why this is the perfect fuel for AI

This is the part that makes the whole effort pay off twice. An AI tool needs context about your work, your projects, your preferences, and it has no way to know any of it unless you tell it. Markdown files are the cleanest way to capture that context once and reuse it everywhere.

The big idea: build a comprehensive set of Markdown notes about how you work and what you know, and you've created a reusable "context library." Point any AI tool at it and you get help that's grounded in your reality, not generic advice.

8Your first 15 minutes

Don't wait until you feel ready. Here's the smallest possible start that still teaches you everything:

  1. Make a folder. On your computer, create a folder called Knowledge Base anywhere you like. Documents is fine.
  2. Open a plain text editor. TextEdit (Mac, set to plain text) or Notepad (Windows) works. Or download a free Markdown app later.
  3. Write one note. Type a heading, a few bullets, a checkbox. Save it as first-note.md. Be sure the extension is .md, not .txt.
  4. Add three more notes this week. One per meeting, idea, or thing you read. Don't organize yet, just capture.
  5. When you have ~10 notes, make folders. Now you'll see the natural categories. Sort them. That's your system, born from real use.
  6. Try the payoff. Paste a note into your favorite AI tool and ask it to summarize, expand, or connect it to another. Feel the leverage.
That's it. You don't need the perfect app, the perfect structure, or a finished plan. You need one folder and one note. Start there, and let the system grow with you.

Common questions

Do I have to memorize all the symbols?

No. You'll use #, -, **bold**, and [links](url) constantly and the rest rarely. Keep the cheat sheet in section 3 nearby for the first week. Muscle memory takes over fast.

What app should I use?

To start, none beyond a plain text editor. When you want live preview and linking, popular free choices include Obsidian, and most code editors. The point of Markdown is that you're never locked to one. Your files work in all of them.

Is my .md file safe if the app disappears?

Yes. That's the core promise. The file is plain text on your computer. Any app, any operating system, today or decades from now, can open it. No app owns your words.

How is this different from Google Docs or Word?

Those are great for polished, final documents. Markdown is built for the thinking before and around that: fast capture, easy organizing, and reuse across tools (including AI). Many people use both: Markdown to think, Word to deliver.

How do I turn .txt into .md?

Just rename the file and change the ending from .txt to .md. The contents don't change at all. Markdown is plain text. The extension simply tells Markdown apps to render the formatting.