I honestly think wiki, static hosting, package registries etc. don’t belong on a git repo. Github has continuously extended their feature-set, but its caused vendor lock-in which I think is the point. How hard is it to spin up a web service to host static content? There are loads of good open source wiki projects, etc.
Depends on the point of the wiki I feel, if it’s project documentation it should be in git alongside the code, if it’s a generic “document store” then yeah there’s better storage backends than git.
I honestly think wiki, static hosting, package registries etc. don’t belong on a git repo. Github has continuously extended their feature-set, but its caused vendor lock-in which I think is the point. How hard is it to spin up a web service to host static content? There are loads of good open source wiki projects, etc.
Depends on the point of the wiki I feel, if it’s project documentation it should be in git alongside the code, if it’s a generic “document store” then yeah there’s better storage backends than git.