Home

Yada - Yet another docs app

^ link to hosted demo version - the docs are stored in browser window's local storage so data will be lost from deleting cookies.

[TLDR] the idea: a unique/novel paradigm for content management of knowledge bases where individual lines ("blocks") can be tagged with (possibly multiple) annotations to describe how to represent the respective piece of information within separate views of a given doc acting as the single source-of-truth..

Overview (key concepts/core idea)

• Files can be either views or docs.
• The first-class entity within a doc/file/view is a block (each distinct line in a markdown representation of the file's content is a block), which represents the concept a piece of information within an outliner framework.
• Docs can be considered as knowledge bases that consolidate pieces of information (blocks) within a single source-of-truth.
• Curate separate views of the content in docs by allowing each block to be tagged with (possibly multiple) annotations describing how to represent the respective block in an associated view of the given doc.
  • The set of distinct annotation/tag names is mapped 1:1 to a set of generated views which contain only the blocks associated with the respective name/label.
• This paradigm allows for easier management of content in knowledge bases by:
  • reducing manual duplication of pieces of the same content across various files - modifications can be done in a single place, and then propagated to all locations where the block is used (based on its annotations/tags).
  • acting as an api for views & integrations to query for specific relevant pieces of information.

Example use cases

• Project details doc/wiki -> PSA | slidedeck | published wiki | ...
• Project plan -> roadmap | sprint/tasks board | backlog list | ...
• Topic knowledge base -> lesson plans | subset topic section in encapsulating doc | study notes | ...
• Full career history tracker -> resumes with flexible content for targetting different jobs

Analogies/Inspirations

• Decouple modles of data/state/etc. from view layers in software (MVC, etc.)
• Representing views as relations on top of tables in databases
• Tags for posts on social sites, etc.; or for files in filesystems