Links to documentation are broke

Tiki is great! But, a wiki, even a very good one, just doesn’t solve the problems I need solved.

My priorities are: Markdown that I can edit in a good editor (local vim, but others are welcome to use other lesser editors), revision control of content in git, never have to think about spam in the docs ever again (my attempt to wikify the Webmin docs was a disastrous time sink and I’m still grumpy about it…the web is so completely poisoned by spam today that it just takes all of the joy out of tools like wikis for me), and the ability for people to send us changes via PR at github.

When it comes down to it, wikis (or any other type of CMS) are solving a problem we don’t have, which is how to let somewhat non-technical users easily edit and manage content. But, pretty much everyone that’s really writing a lot of docs for Virtualmin knows how to use git and a text editor and Markdown, and in fact, are more proficient and comfortable with those tools than with any wiki or CMS we could choose.

A static site generator is just a better fit for us. And, it’s hard to argue with the performance/cost benefits of a static site.

So, when I get a few hours of free time (maybe this weekend, though I’m kinda swamped at my other job at the moment, and on a time crunch, so I might not even have a lot of time this weekend) I’m going to write a tool to export from Drupal docs to a Hugo site. I think it’ll solve all of our problems satisfactorily and I’ll never have to think about comment or edit spam again.

1 Like