Problem: I write reStructuredText notes and essays to myself (and run rst2html) about things I'm learning, exploring or have learned, e.g "Cool shell tricks" or "How to manage my diabetes." Managing lots of rst and html files becomes a mess, especially links to other pages if you refactor, or just finding your stuff.
Project: Miki - Makefile Wiki. A small, personal wiki to manage the above. No software written, just a makefile that coordinates tools you already have or are easy to install. The README emphasizes using the navigation features that your browser already has, rather than writing navigation pages.
You can use any or each of reStructuredText, Markdown or AsciiDoc.
It produces any or all of .html, .pdf and .txt.
Also produces a bare-bones book/media catalog in .json format. Because I sometimes link to my books in my wiki pages.
The refactor problem is "solved" by "make badlinks", which prints out any bad internal links it finds.
In your markup pages, you end your links in the markup suffix of the link's destination (if it's to an internal page). This way you can easily use your text editor's "go to file under cursor" feature to open the destination's source (who wants to open a pdf in Vim?); Miki transforms that into a .html, or .pdf or .txt suffix during output generation, as appropriate
Coincidentally, yesterday I decided that it's "done enough," barring bugs or feature suggestions, and I recorded that observation in the Journal page in my local Miki-based wiki. That feels very slightly like a self-hosting compiler.
Project: Miki - Makefile Wiki. A small, personal wiki to manage the above. No software written, just a makefile that coordinates tools you already have or are easy to install. The README emphasizes using the navigation features that your browser already has, rather than writing navigation pages.
https://github.com/a3n/miki
You can use any or each of reStructuredText, Markdown or AsciiDoc.
It produces any or all of .html, .pdf and .txt.
Also produces a bare-bones book/media catalog in .json format. Because I sometimes link to my books in my wiki pages.
The refactor problem is "solved" by "make badlinks", which prints out any bad internal links it finds.
In your markup pages, you end your links in the markup suffix of the link's destination (if it's to an internal page). This way you can easily use your text editor's "go to file under cursor" feature to open the destination's source (who wants to open a pdf in Vim?); Miki transforms that into a .html, or .pdf or .txt suffix during output generation, as appropriate
Coincidentally, yesterday I decided that it's "done enough," barring bugs or feature suggestions, and I recorded that observation in the Journal page in my local Miki-based wiki. That feels very slightly like a self-hosting compiler.