Yes, I've recently started building a system to store journal entries among other types. They're markdown files in a Git repo which can then be processed (using

Yes, I've recently started building a system to store journal entries among other types. They're markdown files in a Git repo which can then be processed (using Hugo) to make a browsable static site. I'm storing four types of content: - J, journal entries, one file per day with a summary of what I've done that day. Already proving useful, I forget what I did three days ago. - N, notes, working notes on a topic. I treat this like a half neat half messy notebook. I write things in topic files while working through a problem. - T, thoughts, similar to notes but much neater. Often longer form and drafted and rewritten a few times these are small 'articles' on my thoughts on a particular topic. One or two may get converted into blog posts. - Q, quotes, if I find a quote in a book or online I find interesting it gets a file in here. The output is a linear weblog style currently. I've only had this running for a few weeks and it's rather cumbersome at the moment. What I hope to improve on: - Improve onboarding, hugo has a nice tool which sets up new documents and opens the editor: `hugo new n/topic.md`. I want to build on top of this to reduce friction when writing. - Away from PC. This system works very well when I'm in front of a computer. When I'm not I have read-only view on mobile. I take notes on paper, the best of these get transcribed into the system. I'd like a way to write on mobile and have that automagically get added into the system. The backend would probably be an AWS lambda function, frontend, perhaps a web app? - Frontend, I want search and better browsing, tagging &c. But this will come later, when I have more content. I'm trying to stay detached from any 'app' and maintain control of my data. The 'solution' I'm building will hopefully serve me for a long long time.