2 Matching Annotations
  1. Nov 2023
    1. Heptabase is only able to offer both ease of creation and administratin on the same note because it breaks with both Zettlr and Obsidian in having the version of the markdown note safe for a human (as opposed to a computer) to edit be an export only format. But that of course breaks with a fundamental paradigm in Obsidian that your notes are always just a bunch of markdown files importable and exportable to anything. In Heptabase they aren't. Heptabase simplifies the workflow by making the data structure of notes too exacting for a human.

      Sounds like the Heptabase markdown export content isn't easily readable and editable? Would be a huge concern for Heptabase-and-Obsidian interoperability, or Heptabase with any other markdown-compatible tools.

    2. when you export from Heptabase the export filename is the current card name, while in the actual production local directory Heptabase uses the card/filename is the guid. The card "Synology pricing" can be renamed "Synology 2022/3 systems retail pricing" if I discover I do want to also look at the used market, and on my "Which NAS to buy card" updates the name in the text automatically. That doesn't happen in Obsidian.