Skip to content

crimson pro font #488

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

crimson pro font #488

wants to merge 1 commit into from

Conversation

dummdidumm
Copy link
Member

let's see how this looks

Copy link

vercel bot commented Oct 21, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
omnisite ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 21, 2024 9:38am

Comment on lines +1 to +2
@import '@fontsource/crimson-pro/400.css';
@import '@fontsource/crimson-pro/500.css';
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why is it using both by the way? isn't one overriding the other?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That should not be the case, each defines the font files to use for a specific font-weight that may be set for a given element.

Though 500 is an odd choice, normal corresponds to 400 and bold is 700.
Also don't see the weight 500 being used in the codebase.

@Rich-Harris
Copy link
Member

closing before we open the repo so that we don't attract the peanut gallery

@Rich-Harris Rich-Harris mentioned this pull request Oct 22, 2024
@Conduitry Conduitry deleted the crimson-pro branch October 23, 2024 01:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants