Skip to content

Conversation

@Scotchester
Copy link
Member

Closes #532

Once we get a thumbs up from @cmajel, time to ship it!

@Scotchester Scotchester requested a review from cmajel December 9, 2025 22:26
@Scotchester Scotchester requested review from a team as code owners December 9, 2025 22:26
@netlify
Copy link

netlify bot commented Dec 9, 2025

Deploy Preview for cal-itp-website ready!

Name Link
🔨 Latest commit be97761
🔍 Latest deploy log https://app.netlify.com/projects/cal-itp-website/deploys/693c415519008900079268dc
😎 Deploy Preview https://deploy-preview-547--cal-itp-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

cmajel
cmajel previously requested changes Dec 11, 2025
Copy link
Member

@cmajel cmajel left a comment

Choose a reason for hiding this comment

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

So exciting!

I did a review of the typography per our earlier conversation about the challenges with Space Grotesk, since it does not come with italicized fonts. Here's what I'm proposing:

  • Use Space Grotesk (current) for all headings and display copy (H1-H6, .text-title and .text-display
  • Use Noto Sans for body copy (body, p, captions, .small, and .footnote
    • This has the added benefit of making body copy appear slightly larger, which may help with readability
    • This also is the base font for Benefits to encourage continuity/easier maintenance

With this change, I'd also recommend adjusting the default bold in body copy down from 700 to 600.

@Scotchester
Copy link
Member Author

  • Use Space Grotesk (current) for all headings and display copy (H1-H6, .text-title and .text-display

Double-checking this, @cmajel:

  • .text-headline is the category between .text-title and .text-display. Presumably that should also use Space Grotesk?
  • What about .text-subtitle, which is between .text-body and .text-title?

@cmajel
Copy link
Member

cmajel commented Dec 11, 2025

@Scotchester yes!

Copy link
Member

@jgravois jgravois left a comment

Choose a reason for hiding this comment

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

Once we get a thumbs up from @cmajel, time to ship it!

@cmajel blessed this in #554 (comment) 📿

@jgravois jgravois dismissed cmajel’s stale review December 12, 2025 17:09

feedback was addressed via #554

@jgravois jgravois requested a review from a team December 12, 2025 17:14
Copy link
Member

@thekaveman thekaveman left a comment

Choose a reason for hiding this comment

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

It looks great! I was pleasantly surprised at how much more readable the new fonts, weights, spacing, etc. make the site feel.

✨ Nice work y'all!! ✨

@thekaveman
Copy link
Member

Just noting that #553 targets this branch, so should probably be merged ahead of this one.

@jgravois
Copy link
Member

jgravois commented Dec 12, 2025

Just noting that #553 targets this branch

good catch, but nothing in that PR affects the live site. i'll confirm that the base branch is updated to main automatically after this one is merged.

note: the reason i'm keen on clearing the runway today is so that we can finally put #537 to bed too. 👼

@jgravois jgravois merged commit 8884871 into main Dec 12, 2025
5 checks passed
@jgravois jgravois deleted the feature/dsdl branch December 12, 2025 20:01
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.

Deploy DSDL updates to production

5 participants