Repository navigation
Publish approved identity and clear reader journeys (RUST-CI-046) - #6
Merged
Merged
Conversation
added 5 commits
November 10, 2026 13:48
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Give the public homepage equally prominent Use and Develop routes, a concise current Rust capability summary and the approved proposal-1 identity. Preserve the locale and FAQ copy, secondary MFC route, useful section anchors and stable installer bytes.
Stage deployment output in a new owned directory below the inherited output boundary, leaving source and existing evidence untouched. Pin the hosted workflow to the merged public-presence authority, validate renderer staging and locale preservation, then publish only the fresh validated site artifact.
Validation: the normal Pages pre-push gate passed privacy, hygiene, actionlint, the selected-source contract, renderer capability and drift checks, static pages, all rendered-doc links (62 files), approved asset bytes and the retained installer checksum. Its fresh artifact excludes the visual-review diagnostic wrapper. Representative desktop, mobile, RTL, sticky-anchor and visible-focus review is retained separately. Hosted CI runs the renderer staging/locale tests; required hosted validation and deployment must pass before publication is reported.
Refs emulebb/emulebb-rust#305 (RUST-CI-046). The shared Tooling authority precedes this consumer; organization-profile publication follows verified Pages deployment.