A3a3n·Jun 12, 2017
I use the Catalog feature of my own "miki": Makefile Wiki. https://github.com/a3n/miki#catalog
I also try not to get too "taggy" and organized. If I have something new, I just dump it into the top directory of my catalog, and eventually move it down to its own dir and do the minimal op to connect it into the catalog. No DBMS, just the file system.
When I run make on the (personal) wiki, one of the things it does is generate a sitemap, with links to everything, including the catalog part of the wiki. It also creates a catalog-specific json file, which I view directly from Firefox; the addon JsonView makes the json file fields clickable. https://addons.mozilla.org/en-US/firefox/addon/jsonview
Not at all advocating that you use Miki. Just an observation that its motivation is simplicity, to the point that no software was written, I just use
Read the rest
what Linux already has, and the filesystem.
The reason for the simplicity motivation is that I've found, over the years, that the more complete a system I've used to try to "get organized," the sooner it will be abandoned. What I've devolved to is this: the "system" will be more usable, and more likely to be used, the less of that system there is.
Of course it's loads of fun to write one of these things, and that's more than enough reason to do it, so go ahead! But you might keep simplicity in mind, start from an attitude of minimalism with just enough added on, and when it's good enough, stop.
I guess all bets are off if you want an OSS project that other people are going to use and work on. In that case, "Release the Features!" :)
However:
> ... "designing the system so that the manual will be as short as possible minimizes learning effort."
The above quoted in "Expert C Programming, Deep C Secrets," by Peter Van der Linden. I used my catalog to find it. :)