I like what you’ve done so far. It’s quick and simple to use. The one bugbear I’ve come across so far is it converting tables to html, rather than storing them as proper markdown.
I read the reasoning in the documentation, and certainly for my usecases, maintaining it as markdown is more important than trying to perfectly preserve the visual formating, especially as I use multiple devices with different sized screens, so I need different fornatting on each! That’s one of markdowns main strengths, it doesn’t preserve formatting so you don’t need to think about it and it’ll be displayed in a reasonable manner anywhere.
Is there any reasonable chance that there could be an option, at the server level rather than per page, to store tables as markdown?
This is so very important. Snapshots are very helpful tools, and most if the time they’re exactly what you need to recover. Unfortunately they don’t help when the drive fails, or the machine is destroyed by flooding, or myriad other failure modes (human error nit being the least of them). Remote backups are vital if you want your data to survive those events.
Remote copies of the snapshots are a start, but leave you at the mercy of and bugs in the snapshot system, and usually more critically, you have to transfer the whole snapshot or delta, and can’t exclude data without first rearanging your mountpoints.
Lical snapshots and remote file backups give you the best of both worlds, making it easy to recover your data from pretty much any event.