Skip to content

docs: align docs homepage messaging with revamped README#6431

Merged
thomhurst merged 1 commit into
mainfrom
docs/homepage-align-readme
Jul 16, 2026
Merged

docs: align docs homepage messaging with revamped README#6431
thomhurst merged 1 commit into
mainfrom
docs/homepage-align-readme

Conversation

@thomhurst

Copy link
Copy Markdown
Owner

Follow-up to #6430 (README revamp). Brings the Docusaurus homepage in line with the README's positioning.

What changed

  • Hero subtitle — sharpened from the generic "built with performance in mind" to the README's angle: compile-time discovery (not runtime reflection), source-generated + Native AOT, parallel by default, batteries-included with first-class integrations.
  • WhyTUnit cards — refreshed the six cards to mirror the README's pillars:
    • Compile-Time Discovery · Compile-Time Safety (Roslyn analyzers) · Parallel by Default ([DependsOn]/[NotInParallel]/[ParallelLimiter<T>]) · Batteries Included (source-generated mocking) · First-Class Integrations (ASP.NET Core / Aspire / Playwright) · AOT & Trimming Ready.
  • HomepageFeatures cards — sharpened the three descriptions to surface injectable DI fixtures, self-explaining assertion failures, and the build-time/run-time tradeoff. Code examples left intact (they already use the non-obsolete .And.Count().IsEqualTo(...) pattern).

What was intentionally left alone

  • Benchmark components (BenchmarkHighlight / BenchmarkChart) already fetch latest.json — the same source the README table now consumes — so numbers stay in sync automatically. No hand-editing.

Notes

  • No behavioural/library changes — docs-only.
  • npm run typecheck fails on a pre-existing tsconfig.json baseUrl incompatibility (present on main), unrelated to this diff.

Sharpen the hero subtitle and refresh the WhyTUnit / HomepageFeatures cards
to mirror the README's pillars: compile-time discovery, compile-time safety
(Roslyn analyzers), parallel-by-default with control, batteries-included
(source-generated mocking), and first-class ASP.NET Core / Aspire / Playwright
integrations. Benchmark components untouched (already fed from latest.json).
@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c14ccf6bf1

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/src/pages/index.tsx
Comment on lines +46 to +47
A modern .NET testing framework where tests are discovered at compile time, not
reflected at runtime. Source-generated and Native AOT ready, parallel by default,

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Qualify the no-reflection discovery claim

Projects can explicitly run in reflection mode (--reflection, TUNIT_EXECUTION_MODE=reflection, or [ReflectionMode]; see the existing reference docs and ExecutionModeHelper), and that path performs runtime reflection-based discovery/execution. This copy states unconditionally that TUnit tests are not reflected at runtime, which contradicts supported reflection-mode usage and can mislead users debugging that mode; please qualify it as the default/source-generation path instead.

Useful? React with 👍 / 👎.

@claude

claude Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Code review

No issues found. This is a docs-only copy change to the Docusaurus homepage (hero subtitle, WhyTUnit cards, HomepageFeatures descriptions) to align messaging with the revamped README. No source, logic, or public API changes.

Verified the technical claims referenced in the new copy against the codebase — all check out:

  • Source-generated mocking: TUnit.Mocks.SourceGenerator exists.
  • First-class integrations: TUnit.AspNetCore, TUnit.Aspire, TUnit.Playwright all exist.
  • [DependsOn], [NotInParallel], [ParallelLimiter<T>] attributes all exist as described.
  • Code examples in HomepageFeatures/index.tsx were left untouched and already use the non-obsolete assertion syntax, as noted in the PR description.

No CLAUDE.md compliance issues (this repo's root CLAUDE.md rules target engine/source-generator/reflection code, snapshot testing, and AOT — none apply to this docs-only diff).

@thomhurst
thomhurst merged commit d150416 into main Jul 16, 2026
16 checks passed
@thomhurst
thomhurst deleted the docs/homepage-align-readme branch July 16, 2026 13:27
This was referenced Jul 16, 2026
This was referenced Jul 17, 2026
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.

1 participant