Zato VS abna

Yes, the article is correct, there is a market for Markdown sites and related products.

Our Zato website is in Markdown: https://zato.io

We have a purpose-built static site generator, which makes sense in our case because:

* The resulting site is very fast, seeing as there is no need for runtime generation of any assets / HTML / any kind of resources

* It is easier for developers to work on documentation because they already know Markdown

* It is easy to statically apply filters such as spell checkers for multiple languages during the build

* Various optimizations can be applied, e.g. incremental builds or on-demand builds

The drawbacks are:

* Non-technical translators may have a difficult time working with anything but either their own specialized tools or MS Word and they consider Markdown to be "advanced"

* Sometimes you work with writers who are not technical at all and who will not understand what a build system is even if they are open to the idea of learning Markdown itself

Thus, there is a market for a lightweight CMS that would enable non-technical people to author Markdown in their browsers, without a need for any command line usage.

It's extremely hacky and there is barely any automation at all. Everyday at 0500 a cronjob uses https://github.com/djc/abna to fetch the bank balance and makes no effort at all to automatically parse more than the balance. It then compares that with what the balance "should" be according to hledger and sets up a todo item if there is any difference. Somewhere during the day I manually reconcile the two and check off the todo item.

I'm sure it could be smarter with automatic parsing and whatnot, but I actually kinda like the manual action. It makes sure I'm aware of everything happening to my bank account. Time spent per day is actually quite low because it's kept updated and there is never any big backlog of transactions. I would say it takes 2-3 minutes if there are any transactions, or zero ofc if I didn't spend anything.