Overview
Optional capabilities that ship with OpenKnowledge, most of them off until you turn them on. Linters, OKF portability, themes, and presentations.
A plugin is an optional capability that ships with OpenKnowledge. Most stay off until you turn them on (Themes is the exception: it ships enabled). Each one belongs to a scope, and the scope decides who else gets it:
- Project plugins are saved to the project's
config.yml. Commit it and every collaborator gets the same setting. - User plugins are personal to your device. They live in your user config and are never committed.
Turning one on gives it its own page in the settings sidebar, under Plugins.
Turning a plugin on
Open Settings. There is one manage page per scope:
- This project ▸ Plugins
- User ▸ Plugins
Flip the switch. Open editors react live; there is no restart and no Save button.
What ships today
| Plugin | Scope | What it does |
|---|---|---|
| markdownlint | Project | Flags markdown style problems as you write — hard tabs, heading increments, list markers, and the rest of the standard rule set. |
| Frontmatter schemas | Project | Validates document frontmatter against standard JSON Schema files. |
| OKF | Project | Checks portability to Open Knowledge Format v0.2, recommends agent guidance, and can maintain generated indexes. Beta. |
| Slidev | User | Presents a document as a slide deck in its own window. Desktop only; needs the Slidev CLI installed separately. Beta. |
| Themes | User | A personal color-theme picker: one palette per light mode and one per dark, built-in or your own base16 schemes. |
markdownlint, Frontmatter schemas, and OKF all use the content rules layer. What they have in common — where problems appear, the Problems panel, ok lint, agent advisories — is on the content rules overview.