Knowledge Base

██ ██ ███ ██ ██████ ██ ██ ██ ███████ ██████ ██████ ███████

██ ██ ████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██

█████ ██ ██ ██ ██ ██ ██ █ ██ ██ █████ ██ ██ ██ ███ █████

██ ██ ██ ██ ██ ██ ██ ██ ███ ██ ██ ██ ██ ██ ██ ██ ██

██ ██ ██ ████ ██████ ███ ███ ███████ ███████ ██████ ██████ ███████

knowledge

knowledge is a personal knowledge base. Its genesis lies in my desire to capture almost everything I know in one place, structured and searchable for easy retrieval.

Principles

• Typed — every note carries at least one kind (application, concept, operating-system, format, …) with structured frontmatter defined by schema.json and described in Meta.md. The kind is implicit: whichever kind-object is present is the note's type.

• Derivable — index and overview pages ("meta views") are meant to be generated from that frontmatter rather than hand-maintained. Add a note with the right data and the rollups follow.

• Plain & portable — notes are plain-text markdown with relative links between them. No editor lock-in; any markdown editor works.

• Published — the repository is rendered to a static website with noita (noita export).

Topics

• 🔬 Science

• 🧬 Biology

• ⚗️ Chemistry

• 📊 Math

• 🤔 Philosophy

• 🌌 Physics

• 💻 Technology

• 🗣️ Languages

• 🇯🇵 Japanese

Workflow

• Tooling: noita is the workspace — open the repo as a vault to edit, query and browse it, and noita check validates frontmatter against the schema and finds dead links. jsaw queries notes as a table (jsaw db), renders meta views from data (jsaw render), and patches frontmatter (jsaw patch). The dev environment is declared in flake.nix; run nix develop to get both.

• Search:

• ripgrep — full-text search across note content.

• jsaw db — query notes by their frontmatter metadata.

• Editing: noita, or any markdown editor. Obsidian and VSCode work, but nothing relies on editor-specific features — the repo stands on its own.

• Browsing: the published site, or online via Gitea.

Contributing

If you want to contribute or fix some notes, take a look at these files:

• Guide.md — a guide and checklist for adding and maintaining notes consistently.

• Meta.md — describes schema.json, the frontmatter format every note follows.