Repository navigation
Unify Agentic documentation with the Framework family identity - #340
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.
Agentic documentation used a separate violet identity and an older wordmark. It now uses the lowercase Agentic family identity, the original Firefly endorsement, charcoal/ivory/amber surfaces and bundled Manrope. Canonical logo masters are hash-verified before generation, and embedded SVG references are namespaced per placement.
All nine technical diagrams retain their existing text and relationships. Their branding, header logo, banners, favicon and MkDocs presentation are updated together, with identical generated assets in both documentation locations. No framework runtime code changes.
Validation: asset regeneration/check, all 15 asset mirrors and SVG references, text-contrast checks (minimum 5.32:1), strict MkDocs build, 34 pages and 10,250 links, Ruff, formatting, Pyright and 2,510 tests pass (32 nightly tests deselected). Browser review covered desktop/mobile reading, light/dark switching, header fit and the mobile menu. An independent source review found no actionable issues.