4 ms·
Well, for one, it's a bit of a hassle. Constantly thinking of commit messages and stuff, but maybe I'm overly dramatic there. On top of that, it would be nice t
by fhd2 2y ago
Well, for one, it's a bit of a hassle. Constantly thinking of commit messages and stuff, but maybe I'm overly dramatic there. On top of that, it would be nice to at least navigate the contents read-only without Emacs. We use GitLab, it does render org files, but not even links to other files work.
- setopt 2y agoFor read-only access, I’ve heard that Hugo can be used with Org. It’s perhaps more used for blogs than wikis, but it should give you a clean and lightweight website of linked HTML files generated from the Org files, which might be sufficient. Presumably, this can be integrated with Gitlab CI to regenerate the website on push. I guess one question though is how this will scale as the company grows, assuming that more non-Emacs users might join the team after a while?
- fhd2 2y agoYeah exactly, it's a bit like chasing a local maximum. The sibling suggestion, gollum, looks very promising for this, a git backed web based wiki with org support.