I love #joplin so much. I find myself using it to publish long documents that I want others to read that are well formatted, but in plain HTML so can't be edited, and live on my server. Better than a PDF by far, and markdown makes including tables and other complicated layout easy. The only improvement I'd love is the ability to see how many visits a published note got. I don't need browser and IP and location and all that stuff. Just a number, so I can know if a link I shared with a single person was viewed by them.
Right now, I'm using #shlink to generate a unique URL for this purpose. So I publish a #joplin note, then put that URL into shlink, and give my person the shlink url. Then I can see if they clicked it or not. In theory, Joplin allows plugins and I could automate this workflow somehow but I have no idea how Joplin plugins actually work.
@fastfinge I've tried Obsidian, Silverbullet and Trilium Next, all of which had very significant accessibility issues I discovered within the first minute that made them not viable.
#Joplin was such a delight in comparison. There are minor bugs I've noticed, but nothing that prevents me from being productive. Thanks (@joplinapp for the amazing work.
The main thing I'm trying to figure out is setting up a build pipeline to export my public notes to .md and publishing it as a static site.
