[encryptluks2]

There is nothing really preventing GitHub and others from implementing a AsciiDoc/tor converter. AsciiDoctor is already written in Ruby, which is probably what they use on the backend for Markdown conversion. Hugo supports it as well, and I'm sure there are other static site generators. I agree 100% about documentation on Confluence or Sharepoint. Seriously, will not even work at a company that is heavily invested in either at this point.

[toastal]

GitLab also support AsciiDoc.

SourceHut unfortunately does not. You can go through the hoops of POSTing to its GraphQL API from CI a new README from any format to HTML.

[dnsmichi]

You can also embed diagrams and flowcharts with Mermaid into Asciidoc, not only in Markdown.

https://docs.gitlab.com/ee/user/asciidoc.html#mermaid

Examples for Mermaid layouts in the GitLab handbook: https://about.gitlab.com/handbook/tools-and-tips/mermaid/

[miohtama]

Github already supports Restructured Text (reST) in READMEs, and some other markdown flavours. Do not know about AsciiDoc but looks interesting.

[ygra]

As can be seen here, GitHub renders Asciidoc just fine: https://github.com/asciidoctor/asciidoctor.js

[conaclos]

According to GitHub Docs [1], GitHub supports several markup languages, including Markdown, AsciiDoc, Textile, ReStructuredText, Rdoc, Org, Creole, MediaWiki, and Pod.

[1] https://docs.github.com/en/github/managing-files-in-a-reposi...

[stock_toaster]

Alas, no support[1] for include.

[1]: https://github.com/github/markup/issues/1095

[dragonwriter]

> There is nothing really preventing GitHub and others from implementing a AsciiDoc/tor converter

Github already supports AsciiDoc via AsciiDoctor.