feat(site): web-site-management doc, persona CSS & banners, jinja partial#36
Merged
ShawnMcKee merged 1 commit intomasterfrom Dec 7, 2025
Merged
Conversation
… persona Jinja partial
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.
This PR adds a web-site-management doc, persona banner CSS, and persona banner insertion in the persona landing pages. It also adds a Jinja partial for persona banners under the custom theme (osgthedocs). The goal is to improve persona UX and provide a path to move away from a checked-in site by using CI for generation and deployment.\n\nFiles:\n- docs/web-site-management.md\n- docs/css/extra.css (person banner CSS)\n- docs/personas/*/landing.md (inserts persona banner HTML)\n- osgthedocs/partials/persona-banner.html (new Jinja partial)\n\nThis is the first step; the next step is to migrate site generation to CI and remove checked-in site/ once the deploy has been validated.,