Website publishing - tools and options

Issues with maintaining notes without publishing

1. With pure emacs approach, working with notes has become a one-way street. Notes are going into the repo. But they are not being revisited, revised, reviewed, remembered. Publishing gives more value to the notes.
2. The org documents are dependent on emacs. Without emacs, it is difficult to get value out of them. This goes against the principle of not needing “special software” to view notes. The value of notes should not be detracted by a particular software. The notes should be accessible (at least, in a Read only way) no matter where you are in the world. If you have a browser, you should be able to view the notes. This is where publishing comes in.

Things to consider when considering a publishing option for the org pages

1. The content needs to look good
2. Has to support table of contents
3. Has to work with images
4. Has to work with code snippets
5. Automatic publishing into markdown files (nice to have)
6. Automatic publishing of the markdown files into public (nice to have)
7. Automatic publishing of the markdown or the public folder to a website
8. Must support search feature
   1. Search by text (exact match)
   2. Seach by node names
9. Must support Tag and Backlink features
   1. Must show Tags
   2. Must show backlinks
10. Must show big tables (with differences, etc.) properly
11. Showing the Tags and Backlinks in a graphical view is an added advantage.

Static Sites and Generators

TODO

1. Build a full graph of the mindmap from org-roam-db. https://hugocisneros.com/blog/my-org-roam-notes-workflow/#publishing

Tags

1. Hosting platforms