Repository navigation
Use banner destinations and named profile navigation - #23
Merged
Merged
Conversation
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
1 participant
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.
README and guide navigation now lands on the destination banner. Named repository and SNode.C organization buttons use their respective icons, and a person button links to the approved Volker Christian account banner. Section-specific and download links retain their destinations.
Updates cover both maintainer pages and the authoritative Packages site templates. The existing publisher emits banner links for generated project tables, status pages and installation routes, so later publications retain the change.
Validation: all 78 publisher tests executed against the committed candidate shared renderer using a test-only local dependency transport; 77 passed and the existing OpenWrt-signing test skipped because signing tools were unavailable. Shared header drift and docs-audit checks pass for maintainer sources and the staged Packages snapshot. Production Python: +6/-6; test Python: +3/-3.
Depends on SNodeC/.github#30. After both PRs merge, run the existing documentation-only publication workflow to refresh Packages. No package builds, signing inputs or release tags change.