12-4 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.
Open the command palette (βP / Ctrl+P) and look for 'Knowledge packs'. β Search & Navigation
Three packs, ready to go π
| Pack | What you get | More about it |
|---|---|---|
| π Bookshelf | Library.base + Template/Reading note.md |
[[12-2 Library & Reading Log |
| ποΈ PARA | PARA Board.base + Template/Project.md |
[[17 Structuring Knowledge |
| π° Ledger | Ledger.base |
[[12-3 Ledger |
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).baseinstead β 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 π
| What you want | How to do it |
|---|---|
| Start a bookshelf or ledger fast | βP β Knowledge packs β Install |
| See what installing will create | The file list in the confirmation dialog |
| Remove a pack | Remove (files you edited stay) |
I have an .opack file |
Import a pack file⦠|