feat: update mirage blog logo lockup - #16
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.
This updates the Mirage Blog branding to use the horizontal Mirage lockup in the site chrome and homepage hero while preserving readability in both themes.
It switches the Vocs nav logo to the provided lockup, adds theme-aware dark and light lockup assets for the landing page hero, and introduces responsive sizing so the new branding scales cleanly across screen sizes. The favicon/icon remains the existing square mark.
The change is meant to align the blog with the latest brand assets without altering post content or layout structure beyond the header treatment.
Validation:
npm run build