I'm a desktop only kind of guy, and have taken to just logging/journaling in markdown via VS Code - which is what I'm most used to for code documentation and th

I'm a desktop only kind of guy, and have taken to just logging/journaling in markdown via VS Code - which is what I'm most used to for code documentation and the like, so why not reuse it? It sounds relatively easy to generate a .md table from a .csv file which could have an annotations column for any additional custom notes to be added to if desired. While I haven't done so for logging/journaling, I'm doing basically this for my rust crate reviews/audits, which have the benefit of being public: https://github.com/MaulingMonkey/rust-reviews https://github.com/MaulingMonkey/rust-reviews . That autogeneration code can be found in 'src', but it's throaway gross badwrong code, so don't expect much ;). It pulls metadata from the yml-ish preambles of reviews/*.md, and from `cargo crev` commands. The .vscode/tasks.json file in the repository means I can just Ctrl+Shift+B to regenerate the index. In a journaling context I could see adding more tasks - perhaps one to, say, create a new journal/log page - pre-populated with whatever auto-injested information you might want. Returning to my journaling - I keep it as simple as: C:\home\notes\journal\old\... C:\home\notes\journal\old\2019-05-26.md C:\home\notes\journal\old\2019-06-07.md C:\home\notes\journal\old\2019-06-13.md C:\home\notes\journal\... C:\home\notes\journal\2019-12-02.md C:\home\notes\journal\2019-12-03.md C:\home\notes\journal\2019-12-21.md C:\home\notes\journal\2019-12-24.md With the old folder serving as a dumping ground to keep the root folder managable at being just the most recent 10-30 entries or so. A page generator could easily create pages in a convention that allows stable linking between them: ... journal\2019\12\21.md journal\2019\12\24.md