Repository navigation
feat(fonts): centralize UI font assets and loading policy in DDS - #127
Merged
Merged
Conversation
jlc488
marked this pull request as ready for review
October 29, 2026 12:26
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.
Consumers currently carry separate font archives and repeat preload/cache choices. Provide one DDS-owned font-only artifact that apps and static sites can pin without coupling their component framework versions.
The private generated package contains the existing 12 DDS UI font faces, three licenses, canonical font/fallback CSS and one manifest. Pure helpers select preloads and validate public font cache paths; the static exporter supplies the same generated files and metadata to Next/MkDocs adapters. The full Korean file, atomic family alias and optional loading policy are retained. Existing legacy font entry points and document/PDF fonts are unchanged.
There is no npm publication or release-version change. Consumers vendor the same integrity-pinned derivative with its DDS source commit and asset hashes. Application adapters retain their own output URLs and HTTP serialization while font selection/policy remains in DDS.
Validation: 15 related artifact/runtime tests pass locally; the file-symlink case is skipped on Windows without symlink privilege and is included in Linux CI. Tests cover deterministic bytes across LF/CRLF source text, all face/license hashes, unsafe/reserved output paths, metadata symlinks (including missing targets), response cache negative guards and bundle matching. Independent archive regeneration and source review are performed separately. Consumer type/build/browser checks remain tracked in the consuming PRs.