Skip to content

docs: polish README first screen + repo metadata for discoverability - #8

Merged
staryxchen merged 1 commit into
mainfrom
docs-readme-first-screen
Jul 10, 2026
Merged

docs: polish README first screen + repo metadata for discoverability#8
staryxchen merged 1 commit into
mainfrom
docs-readme-first-screen

Conversation

@staryxchen

Copy link
Copy Markdown
Owner

Summary

Polish the README first screen and repo metadata to improve discoverability and visitor→star conversion. First step of the "get more stars" plan — the README is the landing page for every distribution channel (HN, Reddit, awesome-lists, search).

Repo metadata (set directly via gh repo edit, already live)

  • Description: Real-time per-link NVLink bandwidth monitor + inter-GPU P2P benchmark for NVIDIA multi-GPU systems. Lightweight C++ — the monitor needs no CUDA toolkit.
  • Topics (12): nvidia, nvlink, gpu, cuda, nvml, monitoring, bandwidth, hpc, gpu-monitoring, llm-training, p2p, benchmark

The repo previously had no topics (invisible to GitHub topic/search pages) and a generic description.

README first screen (README.md)

Replaced the thin title + 2-bullet intro with a conversion-oriented landing:

  • Title + tagline with SEO keywords (NVLink, GPU, bandwidth, NVIDIA, multi-GPU, LLM/HPC).
  • Badges: CI, MIT license, stars (social), platform.
  • Why? block positioning against nvidia-smi (no per-link NVLink throughput) and dcgmi (heavyweight) — states the pain point.
  • Features (6 bullets) highlighting recent differentiators: bidir full-duplex, all-pairs sweep, CSV/JSON, GPU filter, 81 tests.
  • Demo block with real output from an 8x H20 run (verbose monitor, bidir 730 GiB/s ≈ 2× unidir, all-pairs summary) + a note inviting a terminal recording.
  • Quick start (3 lines) so visitors can try in seconds.

Also removed the now-redundant later ## Features section (covered and improved by the new first-screen list + per-tool Usage sections).

Verification

Doc-only change — not in clang-format or test scope. make check-format / make test unaffected (source files untouched). README rendered/previewed locally.

Files changed

 README.md | 73 +++++++++++++++++++++++++++++++++++++++++++++++++-----------------------
 1 file changed, 50 insertions(+), 23 deletions(-)

Next (optional, follow-up)

  • Embed a real terminal recording (asciinema/terminalizer) where the placeholder note is.
  • Distribution: Show HN post, Reddit r/MachineLearning / r/HPC / r/CUDA, Chinese channels (V2EX/掘金/知乎/B站), awesome-list PRs.

Rewrite the top of the README (above Project Structure) to give the
project a stronger first impression for visitors arriving from search /
social / awesome-lists:

- Title + one-line tagline with SEO keywords (NVLink, GPU, bandwidth,
  NVIDIA, multi-GPU, LLM/HPC clusters).
- Badges: CI, MIT license, stars, platform — signals the project is
  alive and legit.
- A 'Why?' block positioning against nvidia-smi (no per-link NVLink
  throughput) and dcgmi (heavyweight), framing the pain point.
- A concise Features list highlighting the differentiators added
  recently (bidir full-duplex, all-pairs sweep, CSV/JSON, GPU filter,
  81 tests).
- A Demo block with real output from an 8x H20 run (verbose monitor,
  bidir 730 GiB/s, all-pairs summary) plus a note inviting a terminal
  recording.
- A 3-line Quick start (install-deps, make monitor, run) so visitors
  can try in seconds.

Removed the now-redundant later '## Features' section (its content is
covered and improved by the new first-screen list and the per-tool
Usage sections).

Repo metadata (description + 12 topics) set separately via gh repo edit
so the project shows up in GitHub topic/search pages.

Signed-off-by: staryxchen <staryxchen@tencent.com>
@staryxchen
staryxchen merged commit 6dcb6c2 into main Jul 10, 2026
2 checks passed
@staryxchen
staryxchen deleted the docs-readme-first-screen branch July 10, 2026 10:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants