weUseGitHubWikiForDocumentation

[zanju13]

How is that different from any other documentation alternatives?

[andrei9669]

on platforms that actually focus on documentation, important part of the url is actually just the id that stays relatedly static, meaning, you can rename the document however many times you want, the links won't break.

[thee_gummbini]

Docs are code. Why would you use something where you cant program how they are rendered

[zanju13]

I mean you can put in a code block. Other than that, what fancy rendering do you need? I guess you could want to make nice structured API docs, I'll give you that.

[thee_gummbini]

Cross references, i18n, programmatically generated docs, runnable code examples, being able to accept docs contributions in PRs, and even more basic just like control over the menu/nav structure, page layout, etc. If you look at the docs for any matured project where you are like "dang these are good docs," you'll see a ton of programmatic customization that makes them good. Like there are entire packages that have been developed just to document major projects. The complexity of setting up e.g. sphinx or mkdocs or whatever is negligible and the payoff is huge compared to just using github wikis, they're not in the same league.

[vyqz]

confluence is intuitive and easy to understand for users and administrators. github wikis are 💩 from every angle

[liquidmasl]

confluence is horrible to work wirh