Markdown notes can be extended without compromising simplicity

It is important to keep your notebook as simple as possible. This means no elaborate features from the start. The “core” syntax of your notebook should be as simple as possible. This enables them to be used for decades of your lives (see Ka is future-proof).

All features are implemented on top of this simple syntax, as Plugins.

Blog plugin
- The blog plugin should enable a timeline of posts, but implement it using backlinks as much as possible for simplicity (see Markdown notes can be extended without compromising simplicity).
Introducing filesystem hierarchy support in Ka
- Staying simple from the start, is a core tenet of the Ka project. See also: Markdown notes can be extended without compromising simplicity.
- My initial idea was a complicated one: write a specialized archive plugin. However, because I now strongly believe that software should be simple with a simple but functional UX,¹ I decided to take a more general approach: if ka supported reading notes from the whole directory tree, then I can move note files to any sub-directory, and write a small plugin that will treat any pre-defined directory as containing archived notes (the UI can then hide these notes by default from sidebar listing).
  1. Staying simple from the start, is a core tenet of the Ka project. See also: Markdown notes can be extended without compromising simplicity.
    ↩︎
Ka
- Markdown notes can be extended without compromising simplicity