Building a Plain Text Knowledge Base in Plainpad

Jul 8, 2026

Note-taking apps keep getting heavier. Graph views, bidirectional links, nested databases, plugin marketplaces, an AI assistant in every corner. Each feature promises to help you think, and each one adds a little more between you and the words on the page.

This post makes the opposite bet. You can build a genuinely useful personal knowledge base — the kind you actually return to for years — using nothing but plain text. No styling. No Markdown. No formatting decisions at all. Just sentences you type into a note.

Plainpad is built for exactly this. There are no folders, no tags, no boards, no rich-text toolbar demanding your attention. Just a flat list of notes and a fast search box. That apparent lack of features is the feature.

Why Plain Text Wins

Before the how, the why. A knowledge base is a long-term investment, and plain text is the only format that respects that timeline:

• It outlives every app. Formats come and go; plain text has been readable on every computer for fifty years and will be readable on every computer for the next fifty. Your notes are never trapped.
• It removes friction. There is no decision about heading levels, no bold-or-italic, no toolbar to reach for. You open a note and you type. Capture speed is what determines whether a knowledge base actually gets used.
• It forces clarity. When you can’t lean on visual hierarchy to fake structure, you have to write in real sentences. That constraint quietly makes you understand what you’re recording instead of just filing it.
• It is perfectly searchable. Plain text is nothing but content — no markup to trip over. Full-text search reads every word, which, as you’ll see, becomes your entire navigation system.

The System

Here is a complete method you can set up in a few minutes.

One Note, One Idea

Give each idea, concept, or reference its own note. Keep them small — a few sentences to a few paragraphs. A note about sourdough hydration is not the same note as your bread-baking schedule. Small notes are easy to write, easy to find, and easy to recombine later.

Let Names Do the Filing

Plainpad’s sidebar sorts by name, so the note title is your only organising tool — and it’s enough. Prefix related notes with a common word and they cluster together automatically:

Cooking — Sourdough hydration
Cooking — Starter maintenance
Cooking — Oven spring notes
Spanish — Ser vs estar
Spanish — Common irregular verbs

No folders to maintain, no note that lives in the wrong place. The prefix is the folder, and you can regroup anything just by renaming it.

Link by Searching

Without Markdown you have no clickable links — and it turns out you don’t need them. To connect two notes, just mention the other note’s title in plain text:

This depends on the starter being active — see: Cooking — Starter maintenance

When you want to follow that thread, type part of the title into search and jump straight there. Search is your graph. It’s faster than clicking, and it never breaks when you rename something.

Keep a Map Note

Create one note called something like _ Index (a leading symbol pins it to the top of the sorted list). Treat it as a hand-written table of contents — a few lines pointing to the areas of your knowledge base and their entry points. Unlike an auto-generated graph, a map you write yourself reflects how you actually think about the material.

Tag With Words, Not Tags

Miss tags? Just write them as plain text. Drop a line at the bottom of a note:

keywords: sourdough, fermentation, hydration

Searching for hydration now surfaces every related note. You’ve reinvented tags with zero features and no lock-in.

Living In It

The habits matter more than the structure. A knowledge base grows through small, repeated actions:

• Capture first, tidy later. When an idea arrives, make a note and write it down in whatever words come. Rename and prune when you next pass by.
• Review by wandering. Once a week, open your index note and follow a thread through search. You’ll rediscover things and spot connections you’d forgotten.
• Rewrite, don’t hoard. When two notes overlap, merge them. When a note is wrong, fix it. The base is a living surface, not an archive.

The Honest Trade-offs

Plain text asks something of you in return. There’s no visual hierarchy, so long notes can look flat — the answer is to keep notes short. There are no automatic backlinks, so connections only exist if you write them down. And it takes a little discipline to name things consistently. None of these are dealbreakers; they’re the price of a system that will still work in a decade, and most people find the constraints clarifying rather than limiting.

Why It Belongs on Your Own Server

Your knowledge base is a map of how you think. That’s about as personal as data gets. Because Plainpad is self-hosted, those notes live on a server you control — no analytics, no AI training on your ideas, no terms-of-service update that quietly changes the deal. And since everything is plain text, you can walk away at any moment and open every note in any editor on earth.

Start Small

Don’t try to import your whole life on day one. Open Plainpad, create three notes about something you’re actively learning, and let the system grow from real use. If you haven’t set it up yet, the Getting Started guide has you running in a few minutes.

Give it a month. The best knowledge base isn’t the one with the most features — it’s the one you’re still writing in next year.