Closed jhuntwork closed 1 year ago
It seems musl's wiki is using tool called makedown. I've also found few other solutions that look somewhat more advanced that makedown:
And there are also full blown wikis like those:
Awesome, thanks for the research!
Here's my thoughts on each of the above:
Not really going to dive into the pros/cons on this one, I'm sure it has some good features, but my impression is that it's overkill for what I'm looking for and, again, it's Node.js.
And one final one that wasn't mentioned:
From the above list, the ones I'm most interested in looking at are makedown and gitit. But obviously, that's my personal opinion, and most of the above list is very subjective. I'm happy to consider other people's views though, especially since I hope to not be the only one creating content.
I have used DokuWiki
www.dokuwiki.org/dokuwiki at Obarun wiki.obarun.org for a couple of years, no problems, I can't say I love it or have much of a reference frame. You can mix and blend html code together with its pretty standard md language to edit documents, so if you have groups at html and want to just break out the headers for indexing in md it is pretty straight forward.
You would think that by now there would be easy tools to go from md to html to pdf and back ... as I found out, md --> html is pretty simple, the other way is very unreliable ... I couldn't believe it, and I am talking about really plain jane html documents, like those found at skarnet for s6. (by the way there is someone who has taken the project personally and has produced the entire s6 documentation in .md so one can make man pages if they choose to out of it.).
I should be partial to mychorrhiza due to the name, and it does look very interesting, I've never heard of it before.
Another decision for design, should there or shouldn't be support for man pages and man software?
It is hard to believe yet another polarization between lovers and haters of % man
Truly fungal activity in FOSS
I have used DokuWiki in the past and have similar feelings. It's usable.
As for man pages, I've been a little uncertain about policy on that one. Originally I was leaving them out to try to keep things small. But the more I used the system without them, the more I missed them. Right now the reader, mandoc is an optional install, but the pages themselves I've been shipping with the packages.
Added a "wiki" of sorts here: https://github.com/merelinux/wiki - Anyone is free to make pull requests and upon merging to the main branch, a github action will publish it to https://merelinux.org
Originally posted by @lufv in https://github.com/jhuntwork/merelinux/issues/362#issuecomment-921624063
--
It would be very helpful to have others contributing to documentation, a wiki of some kind should make this easier.
I really like musl's wiki. It is backed by a git repo where people make pull requests and is just simple Markdown that is then published as static html.