Repository navigation
refactor(docs): use the common DDS font source - #11
Merged
Merged
Conversation
jlc488
marked this pull request as ready for review
October 29, 2026 13:13
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.
Use the single DDS font artifact and its generated CSS, licenses, preload metadata and cache descriptors instead of independently maintained documentation font binaries and font-face definitions. A small integrity-checking build adapter exports the pinned DDS artifact before MkDocs discovers files. The existing publisher integration and application code are unchanged.
Validation: strict build and the adapter integrity/extraction tests pass. The final archive is identical to the shared DDS source 49baacb and all 12 font files, three licenses and generated CSS pass byte/hash checks. Local desktop/320/375px cold/warm/slow replay covers nine conditions for this site; the final first-paint evidence is tracked with the shared documentation audit. No service-specific font stacks or preload lists remain. Actual GitHub Pages cache policy remains provider-controlled; the DDS descriptors are not claimed as hosting configuration changes.
Generated site output and unrelated Gradle files are excluded. No npm release, credential, security policy or framework change.