Add Sphinx documentation site

[pmoutsias-amd]

Summary

• Adds a Sphinx documentation site under docs/rocm-docs/, single-sourced from README.md and CONTRIBUTING.md via MyST {include} directives so the docs and repo content stay in sync automatically
• Covers installation, getting started, command reference, demos, and contributing/license, using the rocm-docs-core theme
• Updates some links in README.md and CONTRIBUTING.md to be absolute so they render correctly when reused via {include}

Test plan

• Build the docs locally (pip install -r docs/rocm-docs/sphinx/requirements.txt && sphinx-build docs/rocm-docs docs/rocm-docs/_build) and spot-check each page renders correctly
• Confirm README.md and CONTRIBUTING.md still render correctly on GitHub with the updated absolute links

[tomastola]

Nice approach — single-sourcing from README.md/CONTRIBUTING.md via MyST {include} avoids the usual drift between the repo and the docs site. I built the site locally (rocm-docs-core resolved to 1.40.0) and it does build; the pages render and the section anchors land where you intended. A few things to resolve before this is mergeable.

Blocking — CI is red

1. License header check (hawkeye) — 7 new files are missing the MIT header:

docs/rocm-docs/conf.py
docs/rocm-docs/commands.md
docs/rocm-docs/demos.md
docs/rocm-docs/getting-started.md
docs/rocm-docs/about/contributing.md
docs/rocm-docs/about/license.md
docs/rocm-docs/install/installation.md

For the .md files that's the HTML-comment block already used across docs/*.md:

<!--
Copyright © Advanced Micro Devices, Inc., or its affiliates.

SPDX-License-Identifier: MIT
-->

and the #-comment equivalent for conf.py. index.rst, _toc.yml.in, and requirements.txt aren't in licenserc.toml's includes, so they're fine as-is. hawkeye check reproduces this locally.

2. Commit signatures + sign-off — both commits are unsigned and carry no Signed-off-by trailer:

065f231 N | signoff:
1f5d607 N | signoff:

Needs a re-sign plus git rebase --signoff (or recommit with -s -S) and a force-push.

Real defect

3. The platform-support table has a dead link on the install page. docs/wsl.md is the one relative link in an included region that wasn't converted, and it's the only one that actually breaks:

README.md:1056: WARNING: 'myst' cross-reference target not found: 'docs/wsl.md' [myst.xref_missing]

It renders as <a href="#docs/wsl.md">docs/wsl.md</a> — an in-page anchor to nothing, so clicking it does nothing on the install page. (docs/vllm.md at README:41 and LICENSE.TXT at README:10 have the same shape but fall outside every include range, so they're currently harmless — worth deciding whether to normalize them too or leave them.)

Gaps worth settling before merge

4. Nothing builds or publishes this site. There's no .readthedocs.yaml at the repo root, so as it stands this adds docs sources that never become a site. Is the RTD project config landing in a follow-up, or should it be part of this PR?

5. No CI job builds the docs, and this design specifically needs one. The includes are anchored on prose strings — :end-before: "See [CONTRIBUTING.md]", :end-before: "<!--", and heading text. Rewording that one sentence in README.md, or adding an HTML comment anywhere inside the Demos section, silently truncates or empties a page with no signal anywhere. That's the cost of single-sourcing, and a sphinx-build -W job is what makes it safe. Related: the build currently emits 16 Non-consecutive header level increase; H1 to H3 warnings (the included chunks start at ### because start-after drops the ##). I checked the rendered output — docutils normalizes them, so pages get correct <h1>/<h2> and the in-page TOCs are right; they're cosmetic. But they'd block -W, so they need suppressing or restructuring as part of adding the job.

Minor

6. rocm-docs-core>=1.7.1 is unpinned — it resolved to 1.40.0 for me. ROCm docs repos generally pin == so a docs build can't break from an upstream release landing.

7. Two different strategies for the same link problem. README.md anchors were rewritten to absolute https://github.com/ROCm/rocm-cli#... URLs, while installation.md solves the same problem the opposite way — cutting at :end-before: "See [CONTRIBUTING.md]" and re-authoring a docs-relative link. The absolute-URL route works, but it has costs on the primary surface: on GitHub, #model-serving and #interactive-interfaces used to be in-page scrolls and are now full page loads that always resolve against main, and they're wrong on a fork or a tag. On the docs site they send the reader off-site entirely. Since installation.md shows the cut-and-re-author pattern works, is it worth using that consistently and leaving the README anchors relative?

[pmoutsias-amd]

@tomastola Thanks for the thorough review — believe I've addressed all 7 items:

1. License headers — added the MIT header block to all 7 flagged files (conf.py, commands.md, demos.md, getting-started.md, about/contributing.md, about/license.md, install/installation.md).
2. Signed/signed-off commits — all commits are now signed (SSH, verified) and carry Signed-off-by.
3. docs/wsl.md dead link — fixed, now points to the absolute GitHub URL. Left vllm.md/LICENSE.TXT as relative links since they fall outside the include ranges and aren't affected the same way — happy to normalize those too if you'd rather.
4. .readthedocs.yaml — added, pointing at docs/rocm-docs/conf.py and the pinned requirements file.
5. CI docs build with -W — added a docs-build job gated on doc-path changes; it's passing clean (also cleaned up the non-consecutive header warnings you flagged).
6. rocm-docs-core pinning — pinned to ==1.40.0 (what it resolved to locally).
7. Link-fix strategy — unified on absolute GitHub URLs throughout.

One heads-up: there's a small follow-on PR (#312) with an editorial pass from Anisha still open against this branch — not touching anything above, but once it merges in, branch protection may dismiss your approval on the new commits. I'll ping you again then if that happens, but it should be a quick recheck.

[pmoutsias-amd]

Added editorial updates from @anisha-amd.

[michaelroy-amd]

Reviewed current head 77ea773c240263b1a1fa609ae9b70959c3fb5644 after the follow-up commits. The prior blockers are addressed: required MIT headers are present, commits/sign-offs validate, .readthedocs.yaml and a pinned rocm-docs-core==1.40.0 requirement exist, Sphinx runs with -W, the included docs/wsl.md reference no longer produces a dead anchor, and the include-boundary/link strategy is internally consistent. All 17 required checks pass, including the Sphinx docs build, DCO, licensing, and link-sensitive build. One non-linked docs/vllm.md code reference is a minor usability follow-up, not a broken link. No blocking finding. Approving.

[pmoutsias-amd]

Pushed 3 README updates on top of the approved changes:

1. Install channel reframing — Linux/WSL and Windows install snippets now default to the release channel, with nightly as the opt-in flag/env var, reflecting that a stable release is now published.
2. New rocm examine reference section — documents --json and --framework auto|pytorch|llama-cpp|skip.
3. Bonus: Configuration section description — added a short lead-in explaining what rocm config covers (default engine/runtime, telemetry opt-in, chat provider setup).

Flagging since this PR was already approved — the push didn't reset that, so no re-review required, just visibility on the new content.