-
Notifications
You must be signed in to change notification settings - Fork 0
new conf design — fonts #1
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
base: source
Are you sure you want to change the base?
Conversation
@@ -28,7 +23,7 @@ export default function RootLayout({ | |||
children: ReactNode | |||
}): ReactElement { | |||
return ( | |||
<html lang="en" className={`scroll-smooth ${font.className}`}> | |||
<html lang="en" className="scroll-smooth"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suppose we still need <OldFonts/>
applied to the rest of the pages like the blog
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The blog is in Pages router / Nextra 3, so it still has the font in _app.tsx
.
Uri told me I can spend a moment refactoring this and migrating libraries, but... I just don't wanna do it yet. Let's get this conf website up, and then we can think about bumping Tailwind and unifying the routers, and doing whatever else
I kinda aligned on @kamilkisiela's opinion on SSG metaframeworks after reading some newest changelogs.
efabe54
to
4b08c52
Compare
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Description
Added Commit Mono and Host Grotesk.
This PR touches the older conference websites because there was previously a global on HTML.
I moved to using a custom CSS properties
--font-sans
and--font-mono
, so it's easier to avoid conflicts and usage offont-sans
from Tailwind doesn't override the global font.