Knowledge Packs 📦

Drop a ready-made set — a bookshelf, a ledger, PARA — straight into your vault. No building tables from scratch: one install and you're going.

← Home: ObsiKO 101 · Parent: Bases (Data Tables)

"I'd love a bookshelf, but where do I even start with Bases…?" 🤔

That's what Knowledge Packs are for. A well-built table and its templates arrive as one set, and all you have to do is fill in the content.

Press the New… menu 📁 above the explorer and pick Add knowledge pack at the bottom. Or open the command palette (⌘P / Ctrl+P) and look for 'Knowledge packs'. → Search & Navigation

Four packs, ready to go 🎁

✍️ Web novel — the folders come too

Where the other packs hand you one table, this one sets up the whole drawer for a serial.

Web novel/
  Web novel.base   ← your progress dashboard
  Story/            ← where episodes go (Episode 1 is already there)
  Lore/
    Character/ Event/ Faction/ Place/ Item/ World/ System/ Unsorted/

Each of the eight lore folders holds one starter note — a short page of blanks like - Name: and - What they want:. Rename it and it becomes your first character, your first place. ✏️

💡 The folder is the kind. The dashboard's 'Lore' table gathers whatever sits under Lore/, by folder. There is no property to memorize — put a note in Lore/Place/ and you're done. 😌

When you want a character in the Character Codex, add type: character to its properties then. (The starter notes are left bare on purpose — they aren't anybody yet, and empty cards shouldn't fill your codex.)

Give each episode a status: property and the progress bar and donut chart at the top fill themselves in. Episode 1 starts at draft — switch a finished one to done! 📈

Need a skeleton for a character or a world? The Structure tab in Writing Helper drops a full sheet into the note you're in.

Once installed, they're just ordinary files of yours. Open them up, change the columns, add views — ObsiKO won't say a word. 😄

💡 The result is the same as building it yourself from the sidebar ＋ menu, as described in those chapters. The difference is that a pack brings the templates along too. Take whichever route you prefer!

You see what will be created — before it is 👀

Hit install and nothing is written yet. First you get a list: "these files will be created."

• Existing files are never overwritten. If the name is taken, the pack steps aside and creates Library (1).base instead — and says so right in the list. Your original file isn't touched.
• It changes no settings and uses no internet. A few files appear; that's the whole story.

Removal is even more careful 🧹

Remove a pack and only the files that are still exactly as the pack made them get deleted.

Any file you edited — even by one character — stays. It would be awful if a template full of your reading notes vanished with one click! (You'll be told how many were kept.)

Importing a pack file 📥

Got a pack file (.opack) someone made? Open it with 'Import a pack file…'. It installs the same way as everything above — preview → install → safe removal.

🔒 There's nothing in a pack that runs. All a pack can hold is text files destined for your vault (.md · .base · .canvas). Programs, commands, internet access — none of it can even be put in there.

That's why ObsiKO never asks you "do you want to grant these permissions?" when you open a pack. There's nothing to ask about. The only thing you need to check is: "are these the files I want?" 😌

There will be no pack store 🙅

ObsiKO has no marketplace where anyone can upload code — and it never will.

When there are thousands of things to choose from, you get tired before you even start, and finding the one that fits you is a job in itself. On top of that, things built outside the app tend to break with every update. Getting rid of that fatigue is exactly why ObsiKO exists.

So ObsiKO's features live inside the app. A pack doesn't add a feature — it sets the table so you can use one that's already there. 🍽️

At a glance 📋

← Previous: Ledger · Home · Next: Calendar →