Skip to content
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

feat: update fonts and homepage image #1851

Merged
merged 5 commits into from
Jan 9, 2025
Merged

feat: update fonts and homepage image #1851

merged 5 commits into from
Jan 9, 2025

Conversation

lukecd
Copy link
Contributor

@lukecd lukecd commented Jan 9, 2025

Description

This PR includes two updates to the docs site:

  1. Updates typography to match brand guidelines

    • Replaces Ruberoid with Youth font for headings
    • Replaces Inter with Untitled Sans for body text
    • Improves font loading performance with font-display: swap
    • Adds specific font family classes for better consistency
  2. Updates homepage messaging and visuals

    • Updates hero text to "Build whatever"
    • Updates tagline to "Build any blockchain stack with modular components for security, scaling, and data availability"
    • Replaces modular.svg with Blobspace.png for hero image

Related Issues

Testing

  • Verified font loading and appearance
  • Checked homepage layout with new hero image
  • Tested responsive behavior on different screen sizes

Summary by CodeRabbit

Summary by CodeRabbit

Release Notes

  • New Features

    • Updated website hero section with new messaging and imagery.
    • Introduced new font styles across the site.
  • Style

    • Replaced existing font families with "Youth" and "Unititled-Sans".
    • Updated primary and body font variables.
  • Documentation

    • Refreshed site branding and visual communication.

The release focuses on modernizing the site's typography and visual identity, providing a more contemporary and assertive presentation of the platform.

lukecd added 2 commits January 8, 2025 11:30
…g + visuals

#1848

Update index.md: Revise hero section with new text and tagline, and change image source
Addresses #1850

- Replace Ruberoid with Youth for titles
- Replace Inter with Untitled Sans for body text
- Update font paths and formats in style.css and config.ts
- Add font-display: swap for better loading performance
- Add specific font family classes for VPDoc and VPHome components

Youth is now used for titles (h1-h6) and Untitled Sans for regular text,
following the typography guidelines.
@lukecd lukecd requested a review from jcstein January 9, 2025 05:40
Copy link
Contributor

coderabbitai bot commented Jan 9, 2025

Warning

Rate limit exceeded

@jcstein has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 18 minutes and 56 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between d910c55 and 7ae8677.

📒 Files selected for processing (1)
  • .vitepress/theme/style.css (2 hunks)

Walkthrough

The pull request introduces comprehensive changes to the Celestia.org documentation website, focusing on font styling and homepage messaging. The modifications include updating the VitePress configuration to use new font assets, revising the CSS to incorporate new font families, and redesigning the homepage's hero section with updated text and imagery. These changes aim to refresh the visual identity and communication strategy of the website.

Changes

File Changes
.vitepress/config.ts - Replaced font asset variables (ruberoidLightFontyouthRegularFont, ruberoidRegularFontuntitledSansRegularFont, ruberoidBoldFont removed, new untitledSansMediumFont added)
- Updated font preload link type from "font/opentype" to "font/woff2"
.vitepress/theme/style.css - Removed "RuberoidBold" font family
- Added "Unititled-Sans" (regular and medium) and "Youth" font families
- Updated --font-primary to use "Youth"
- Added new --font-body variable using "Unititled-Sans"
index.md - Changed hero text from "The first modular blockchain network" to "Build whatever"
- Updated tagline to emphasize "unstoppable applications" and "full-stack customizability"
- Replaced hero image from /modular.svg to /Blobspace.png

Assessment against linked issues

Objective Addressed Explanation
Add new font types [#1850]
Update homepage messaging [#1848]
Replace homepage graphic [#1848]

Poem

🐰 Fonts dancing, pixels bright,
Celestia's message takes new flight!
From Ruberoid's old, to Youth's new grace,
A website leaps with rabbit-like pace! 🚀
Build whatever, the mantra sings! 🌈

Finishing Touches

  • 📝 Generate Docstrings

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

github-actions bot commented Jan 9, 2025

PR Preview Action v1.5.0
🚀 Deployed preview to https://celestiaorg.github.io/docs-preview/pr-1851/
on branch main at 2025-01-09 15:05 UTC

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5c630b4 and 1373fdf.

⛔ Files ignored due to path filters (6)
  • public/Blobspace.png is excluded by !**/*.png
  • public/fonts/Ruberoid/Ruberoid-Bold.otf is excluded by !**/*.otf
  • public/fonts/untitled-sans/untitled-sans-medium.woff2 is excluded by !**/*.woff2
  • public/fonts/untitled-sans/untitled-sans-regular.woff2 is excluded by !**/*.woff2
  • public/fonts/youth/Youth-Regular.woff is excluded by !**/*.woff
  • public/fonts/youth/Youth-Regular.woff2 is excluded by !**/*.woff2
📒 Files selected for processing (3)
  • .vitepress/config.ts (1 hunks)
  • .vitepress/theme/style.css (2 hunks)
  • index.md (1 hunks)
🔇 Additional comments (3)
.vitepress/config.ts (1)

153-203: LGTM! Font loading configuration is well-structured.

The font preloading configuration is correctly implemented with:

  • Appropriate font type for woff2 files
  • Preload directive for optimal loading performance
  • Crossorigin attribute for CORS compliance
index.md (1)

8-11: LGTM! Homepage content updates are clear and aligned with objectives.

The hero section changes successfully implement the new messaging direction as specified in the PR objectives.

.vitepress/theme/style.css (1)

Line range hint 119-160: LGTM! Font implementation follows best practices.

The implementation:

  • Defines clear font variables
  • Applies fonts consistently across components
  • Uses font-display: swap for optimal loading

.vitepress/config.ts Outdated Show resolved Hide resolved
.vitepress/theme/style.css Outdated Show resolved Hide resolved
@jcstein
Copy link
Member

jcstein commented Jan 9, 2025

Screenshot 2025-01-09 at 09 50 38 It doesn't look like Untitled Sans worked as expected 👀

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
@jcstein jcstein changed the title Luke/visualupgrades feat: update fonts and homepage image Jan 9, 2025
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1373fdf and 9c1f944.

📒 Files selected for processing (2)
  • .vitepress/config.ts (1 hunks)
  • .vitepress/theme/style.css (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • .vitepress/config.ts
🔇 Additional comments (3)
.vitepress/theme/style.css (3)

150-160: LGTM! Font family applications are well-structured.

The font family variables are consistently applied across different elements and components, maintaining a clear typography hierarchy between headings and body text.


96-96: Verify font file availability.

Let's ensure all referenced font files exist in the correct locations.

Also applies to: 104-104, 112-112

✅ Verification successful

Font files are correctly placed and available.

All referenced font files exist in their expected locations under the public/fonts/ directory.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check if all font files exist in the correct locations

# List of font files to check
fonts=(
  "public/fonts/untitled-sans/untitled-sans-regular.woff2"
  "public/fonts/untitled-sans/untitled-sans-medium.woff2"
  "public/fonts/youth/Youth-Regular.woff2"
)

# Check each font file
for font in "${fonts[@]}"; do
  if [ -f "$font" ]; then
    echo "✓ Found: $font"
  else
    echo "✗ Missing: $font"
  fi
done

Length of output: 811


95-115: ⚠️ Potential issue

Fix font family name and path inconsistencies.

There are naming inconsistencies that will cause font loading issues:

  1. Font family name has a typo: "Unititled-Sans" should be "Untitled-Sans"
  2. Medium font path has a typo: "unititled-sans" should be "untitled-sans"

These issues likely explain the font rendering problems reported in PR comments.

Apply these fixes:

-  font-family: "Unititled-Sans";
+  font-family: "Untitled-Sans";
   src: url("/fonts/untitled-sans/untitled-sans-regular.woff2") format("woff2");

-  font-family: "Unititled-Sans";
-  src: url("/fonts/unititled-sans/untitled-sans-medium.woff2") format("woff2");
+  font-family: "Untitled-Sans";
+  src: url("/fonts/untitled-sans/untitled-sans-medium.woff2") format("woff2");

Likely invalid or redundant comment.

.vitepress/theme/style.css Outdated Show resolved Hide resolved
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
@jcstein
Copy link
Member

jcstein commented Jan 9, 2025

Screenshot 2025-01-09 at 10 04 54 gottem

@jcstein jcstein merged commit a089fbc into main Jan 9, 2025
5 of 6 checks passed
@jcstein jcstein deleted the luke/visualupgrades branch January 9, 2025 15:06
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.

feature request: add new font types Update homepage messaging + visuals
2 participants