The 5-Minute Wiki Folder Setup That Actually Scales

You don't need a complex tool to build a knowledge base. You need three folders, two templates, and a text editor.

This is the exact folder structure I use. It works in Obsidian, VS Code, or any markdown editor. It scales from 10 notes to 10,000 notes. And you can set it up in five minutes.

Table of Contents

1. Why This Structure Works
2. The Folder Tree
3. The Index Template
4. The Log Template
5. The .gitignore File
6. How to Actually Use This

Why This Structure Works

Most people start a wiki and abandon it within a week. The problem isn't discipline. It's friction.

Every extra decision is a place to quit. Where does this note go? What should I call it? Do I need a new category?

This setup removes those decisions. You have three folders. You always know where things go. You never wonder how to start a new note.

Analogy: Think of your wiki like a kitchen. You could organize your silverware by manufacturer, year purchased, and frequency of use. Or you could have three drawers: forks, knives, spoons. The second option works because you never have to think about it.

The Folder Tree

Here's the complete structure:

wiki/
├── areas/
│   ├── coding/
│   │   └── index.md
│   ├── productivity/
│   │   └── index.md
│   └── writing/
│       └── index.md
├── logs/
│   ├── 2025-01.md
│   └── 2025-02.md
├── scratch/
│   ├── draft-ideas.md
│   └── quick-notes.md
├── index.md
└── .gitignore

That's it. No nested hierarchies. No elaborate taxonomies. Three top-level folders with clear purposes.

areas/: Organized knowledge. Each subfolder is a topic. Each topic has an index.md that links to everything in that area.

logs/: Time-based entries. Monthly files where you dump daily thoughts, meeting notes, and work-in-progress ideas.

scratch/: Temporary files. Anything that doesn't have a home yet. You clean this folder once a month.

The Index Template

Every area folder needs an index.md. This is your table of contents for that topic.

Copy this template:

# Topic Name

Last updated: 2025-01-15

## Overview

[2-3 sentences about what this area covers]

## Key Concepts

- [[concept-one]]
- [[concept-two]]
- [[concept-three]]

## Resources

| Resource | Type | Status |
| --- | --- | --- |
| [Resource Name](url) | article | read |
| [Resource Name](url) | video | queued |
| [Resource Name](url) | course | in progress |

## Questions

- Open question 1?
- Open question 2?

## Related Areas

- [[other-area-name]]

The template does three things:

1. Key Concepts gives you a quick scan of what you know about this topic.
2. Resources tracks what you've consumed and what's queued.
3. Questions captures what you don't understand yet.

When you learn something new, you add a concept. When you finish a resource, you update the status. When you figure out an answer, you move it from Questions to Key Concepts.

The Log Template

Logs are monthly files. You append to them daily. They're chronological brain dumps.

Copy this template for each month:

# January 2025

## 2025-01-15

**Work**
- Thing I learned today
- Problem I'm stuck on
- Decision I made

**Notes**
- Random thought worth capturing
- Link to something interesting: [title](url)

**Links**
- [[area/coding]] for the thing about Python generators, -

## 2025-01-14

[same structure]

The log is where most of your writing happens. You don't overthink it. You just append today's date and dump what's in your head.

Once a week, you review your log. Anything worth keeping gets moved to an area. Everything else stays in the log as a historical record.

The .gitignore File

If you sync your wiki to GitHub or any version control, you need a .gitignore.

Copy this:

# OS files
.DS_Store
Thumbs.db

# Editor files
.obsidian/
.vscode/
*.swp
*.swo
*~

# Personal files
scratch/personal-*
logs/*-private.md

# Temporary files
*.tmp
*.bak

This keeps your editor settings, OS junk, and personal notes out of version control. Everything in scratch/ that starts with "personal" stays local. Any log file ending in "-private.md" stays local.

You can write private thoughts without worrying about accidentally pushing them.

How to Actually Use This

Here's the daily workflow:

Morning: Open today's log file. Add the date. Write three bullets about what you're working on.

During the day: When you learn something, add it to the log. When you find a good resource, add it to the log. When you have a question, add it to the log.

End of day: Read today's log. If anything is worth keeping, move it to an area index.

End of week: Review the week's logs. Clean up your scratch folder. Update area indexes with new concepts.

That's the entire system.

Starting Your First Area

1. Create a folder in areas/: mkdir areas/coding
2. Copy the index template: cp index-template.md areas/coding/index.md
3. Fill in the Overview section with 2-3 sentences
4. Start adding concepts as you learn them

Dealing with Growth

When an area gets too big (more than 20-30 concepts), you split it.

Don't create nested folders. Create sibling folders.

Instead of:

areas/
└── coding/
    ├── python/
    └── javascript/

Do this:

areas/
├── coding-python/
└── coding-javascript/

Flat structures scale better. You can always search. You can't always remember where you nested something three levels deep.

The Weekly Review

Set a 15-minute timer every Sunday. Ask these questions:

This keeps the system clean without requiring daily maintenance.

What You Don't Need

You don't need:

• Tags (folders are enough)
• Templates for every note type (two templates is plenty)
• Elaborate linking schemes (link when it's useful, not because you can)
• Daily note automation (a monthly log is simpler)
• Plugins (start with markdown, add tools later)

The best knowledge system is the one you actually use. Simple beats clever every time.

Common Questions

Q: What if I want to track tasks?
Add a ## Tasks section to your daily log. Copy incomplete tasks to the next day. That's it.

Q: Should I use wikilinks or regular markdown links?
Wikilinks ([[note-name]]) if your editor supports them. Regular links otherwise. Doesn't matter much.

Q: How do I handle images?
Create an assets/ folder at the root. Reference images with ![](../assets/image.png). Keep images separate from text.

Q: What about mobile?
Sync your wiki folder to Dropbox or iCloud. Use any markdown editor on your phone. I use iA Writer.

Conclusion

You now have everything you need. Three folders. Two templates. One .gitignore file.

Create the folders. Copy the templates. Start writing in today's log.

The system will grow with you. It works for 100 notes. It works for 10,000 notes. The structure stays the same.

Stop planning your perfect knowledge system. Start writing in an imperfect one. You can always reorganize later, but you can't reorganize notes you never wrote.