docs: adopt shared documentation theme - #1
Merged
Merged
Conversation
- Share the PyPTO header, project switcher, typography, and reading layout across the English and Chinese Toolkit documentation. - Replace the independent palette with the shared system, light, and dark preference used across the PyPTO documentation sites. - Pin the merged shared theme and its MkDocs 1.6.1 / Material 9.7.7 constraints while retaining the existing bilingual navigation, search, and deployment workflow.
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.
The Toolkit documentation now uses the shared PyPTO header, project switcher, reading layout, and system/light/dark preference. English and Chinese navigation and search retain their existing configuration.
The build checks out a fixed, merged theme revision and applies its MkDocs 1.6.1 / Material 9.7.7 constraints. Theme updates remain covered by the existing
docs/**workflow trigger; fetched theme sources and build inputs are excluded from publication.Validation:
mkdocs build --strictpasses for both languages; all 20 documentation pages have the expected canonical URLs and bundled theme assets. The original configuration also builds with the shared renderer versions, and the final requirements resolve successfully.Browser validation covers both languages at 1440/768/390/320 px, article-preserving language switching, same-language search result navigation, code copy, mobile menus, wide-content containment, and theme persistence across the other PyPTO sites. Material's optional article-level sitemap probes also occur with the original configuration; shared assets and page requests remain checked strictly.