Open Knowledge Format support

Mark It Down can read, write, and review OKF bundles
without turning your knowledge into a private database.

Markdown knowledge that can travel.

Open Knowledge Format is a lightweight way to package knowledge as ordinary Markdown files with YAML frontmatter. A bundle can include concept documents, optional index.md files for navigation, and optional log.md files for history.

The format is intentionally small: readable by people, diffable in Git, and tolerant when a bundle is incomplete or evolving. The official OKF v0.1 draft defines the basic rules, including the required type field for concept files.

Read the OKF spec or Google Cloud's introduction.

A review layer for portable knowledge.

  • Export OKF bundlesWrite notes out as .okf.zip with generated frontmatter, flat concept layout, folder indexes, and a self-contained static viewer. Source URLs are preserved as OKF resources. The activity log groups entries by date and labels each item as Creation or Update.
  • Static viewerEach export includes a single index.html you can open directly — no server needed. Three-column layout with concept list, Markdown body, TOC, and a concept graph. Use the [+][−] buttons to zoom in on dense clusters or pull back for an overview.
  • Citations round-tripFrontmatter citations fields survive export and import unchanged. The viewer renders them as a dedicated section per concept.
  • Edit on-rampThe viewer footer shows how to edit the bundle in any text editor or Markdown app. No lock-in.
  • Import OKF bundlesImport a bundle explicitly from the Entry menu, including bundles without a version marker. Relative links are restored as wikilinks, and original concept paths are preserved for lossless re-export.
  • Keep bundle shapeConcept files export flat at the bundle root. Folder information travels as _folder frontmatter and restores on re-import.
  • Preview conformanceUse Portability Hub to see OKF-related findings before a note leaves the workspace.
  • Sync through GitPush OKF-compatible note files and generated indexes as plain repository content.

No hostages means no hidden format.

Mark It Down is built around the idea that notes should graduate. OKF points in the same direction: knowledge remains visible as Markdown, metadata remains visible as frontmatter, and history remains visible in Git.

That makes Mark It Down a good place to inspect and rewrite OKF content. It is not a managed catalog, enrichment agent, or hosted integration. It is the human review step between an incoming bundle and the next place that bundle needs to go.

Bring knowledge in. Rewrite it. Let it leave.