Workflows

Building a Personal Knowledge Hub

Most people have tried some version of a second brain. A folder of saved articles. A notes app full of disconnected thoughts. A paper journal that got too unwieldy to search. Something that worked for a while, then quietly stopped.

The problem is usually one of two failure modes: too simple, and the system can’t hold the complexity of what you’re actually thinking about; too rigid, and maintaining the structure takes more energy than the knowledge is worth.

Inklings offers a middle path. Structure exists where it’s useful — types, properties, wiki-links — and disappears where it isn’t. You can write a free-form daily note with no structure at all, and still find it months later because search works on everything. The knowledge hub grows alongside your thinking, not as a separate maintenance burden.

Capture Everything in One Place

The first principle of a personal knowledge hub: one workspace for everything. Not one workspace for books and another for work and another for personal projects. One workspace, full stop.

The reason is navigation. When your notes are fragmented across apps and services, every search is partial — you’re never sure whether the thing you’re looking for is in the app you’re currently searching. One workspace means one search covers everything you’ve ever written here.

A working personal knowledge hub might look like this:

Personal Knowledge Hub
├── Journal
│   ├── 2026 Week 09
│   ├── 2026 Week 10
│   └── ...
├── Books
│   ├── Thinking, Fast and Slow
│   ├── The Design of Everyday Things
│   └── How to Take Smart Notes
├── People
│   ├── Alex Chen (colleague)
│   └── Dr. Rivera (advisor)
├── Projects
│   ├── Kitchen Renovation
│   └── Learn Rust
├── Ideas
│   └── Spaced Repetition for Meeting Notes
└── Weekly Reviews
    ├── Week 09 Review
    └── Week 10 Review

Journal entries are the capture layer — write in them throughout the week, without worrying too much about linking or tagging. The discipline is just: write it down, in here. Weekly pages work better than daily ones; a day is usually too short to notice patterns, but a week gives you enough signal.

Weekly reviews are where you look back at the week’s notes and pull out what mattered. What did you read? What are you thinking about? What patterns appeared that you want to carry forward? A weekly review is also where you create more structured pages — moving a rough idea from a journal entry into its own page, linking a person you mentioned three times to their proper page.

This rhythm — capture weekly, synthesize weekly — keeps the system from requiring constant maintenance. The journal is fast and unstructured; the review is where you invest attention.

Connect Across Sources

The difference between a notes pile and a knowledge hub is connection. Individual notes capture information; connections build understanding.

Wiki-links are how Inklings makes connection explicit. In any page, type [[ to open the link autocomplete and link to any other page by name. The linked page records the incoming connection in its backlinks panel — so the connection is navigable from both ends.

In practice, this looks like:

In a daily note: “Reading Thinking in Systems — the concept of feedback loops is exactly what I was thinking about in [[The Velocity Problem]]”
In a book page: “Donella Meadows arguing for delayed intervention — connects to [[Slow Hunch]] and what [[Austin Kleon]] says about creative incubation”
In an idea page: “Three sources now pointing at this: [[Thinking in Systems]], [[The Shallows]], [[conversation with Marcus]]”

The connection web that forms over months of use is genuinely different from what any individual note contains. A book page connected to fifteen idea pages means the book became part of your thinking in fifteen ways. The idea pages connected back to multiple sources show you where your most durable ideas came from.

Ghost links work here too: type [[a book you haven't read yet]] before you’ve created that page. The link appears with a dimmed style — a placeholder, not an error. When you create the page later, the link resolves and the connection is already there.

Type Your Knowledge

Not all knowledge is the same shape. Books have authors and reading status. People have context — where you know them from, what you collaborate on. Projects have status and next actions.

Go to Settings → Types and create types that match the knowledge you actually have:

Book

author (text)
status (select: Want to Read / Reading / Read)
rating (number, 1–5)

Person

role (text) — colleague, friend, mentor, author you’ve read
context (text) — where you know them from or what connects you to them

Project

status (select: Active / On Hold / Done)
next-action (text) — the single next thing to move this forward

Assign types to pages in the relevant folders. Your Books folder becomes queryable: filter by status: Reading to see what’s in progress, by rating: 5 to see what to recommend, by author: Ursula K. Le Guin to see everything you’ve read by her.

The types aren’t required to get value from Inklings. Plain pages with no type structure are fully searchable and linkable. Types become worth the setup cost when you have enough of a particular kind of entity that you want to query across them — a dozen books, twenty projects, a hundred people you’ve written about. Before that threshold, a flat page works fine.

Search as Your Memory

The practical test of any knowledge system is: can you find the thing you only half-remember?

That article about distributed systems you saved two years ago. The note about the conversation where someone explained why generalists are undervalued. The book that had the argument about compounding creative work — what was it called?

Full-text search in Inklings covers everything: page titles, page bodies, tags, property values. You only need one word from a note to surface it. Type “distributed” and find the article. Type “generalists” and find the conversation note. Type “compounding” and find the book.

This matters because it changes what you need to do when capturing. You don’t need a perfect filing system. You don’t need to tag everything. You don’t need to worry about whether a note is in the right folder. Write it down, write it in your own words, and trust that search will find it when you need it.

The corollary: write notes in your own words, not as quotes. Quotes from a book will surface when you search for the book. Your synthesis of an idea will surface when you search for any of the concepts you used to describe it. The note that says “Meadows on feedback loops — the delay between action and consequence is where most system interventions fail” is more findable than a clean quote, because it contains your vocabulary.

The Agent as Thinking Partner

Pro+Agent

A personal knowledge hub accumulates over time — and over time, patterns emerge that are hard to see from inside the accumulation. You’ve been reading and thinking about the same things in different contexts without realizing the thread connects them.

The agent can read your workspace and find those threads.

Ask it to synthesize across your notes:

“What themes appear most frequently across my book notes from the last three months?”
“I’ve linked to [[Flow States]] from several places — what are the different contexts where I’ve thought about this concept?”
“Which of my current projects share underlying concerns? Am I working on the same problem in multiple forms?”
“What ideas in my workspace have no connections to anything else? Are there isolated thoughts I haven’t integrated?”

This isn’t a replacement for your own synthesis — the agent doesn’t know what these connections mean to you, or which ones are worth pursuing. But it can surface the raw patterns quickly, and pattern recognition is often the slow bottleneck in personal knowledge work.

The agent reads what you’ve written. Write more specifically than you would for an app you’re using as a dump; write as if you might ask someone to find the interesting threads later. That practice improves both the notes and what the agent can do with them.

Connecting External Systems

Pro

Where Inklings is heading: external tools that can read and write your workspace directly. A browser extension that saves an article with its highlights and connects to your existing notes. A tool that adds meeting notes from your calendar app. An integration that brings research from external sources into the workspace and links it to pages already there.

This works through the MCP server — a local interface that external tools can connect to and query your workspace data. It’s not a cloud sync; it’s a local connection between Inklings and whatever other tools you’re using.

This is in progress, not released. The MCP server exists as a feature for agent use; the broader external integration story is where that infrastructure leads. If you’re building a workflow around this now, know that the foundation is real and the use cases are the roadmap.

What to Build Toward

The honest answer about personal knowledge hubs: the value is slow to accumulate and hard to see in the first month. A workspace with twenty notes doesn’t feel meaningfully different from a notes app. At two hundred notes, connected and typed, it starts to feel like a real repository of your thinking.

The compounding happens through consistent small additions:

Start with a daily notes habit. One entry per day, write what you’re thinking about.
When you finish a book, create a book page. Link it to the ideas it connects to.
When you meet someone new or have a significant conversation, create a page. Link it to relevant projects or ideas.
Once a week, review and connect. Spend twenty minutes pulling threads from the week’s daily notes.

The links accumulate. The types become useful once you have enough pages to sort. The search surface grows. Two years from now, your workspace contains a navigable map of what you’ve read, thought about, and connected — and you can actually search it.

That’s what a personal knowledge hub is supposed to do. Inklings is built for it.