Skip to content

feat(docs): preview Source Sans 3 on marketing pages - #1078

Open
goldflag wants to merge 1 commit into
masterfrom
font-preview/source-sans-3
Open

feat(docs): preview Source Sans 3 on marketing pages#1078
goldflag wants to merge 1 commit into
masterfrom
font-preview/source-sans-3

Conversation

@goldflag

@goldflag goldflag commented Jul 18, 2026

Copy link
Copy Markdown
Collaborator

Summary by CodeRabbit

  • Style
    • Updated the home page layout with the Source Sans 3 font.
    • Improved page structure and alignment using a flexible container while preserving the existing header, content, and footer.

@vercel

vercel Bot commented Jul 18, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
rybbit Ready Ready Preview, Comment Jul 18, 2026 10:27pm

Request Review

@coderabbitai

coderabbitai Bot commented Jul 18, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

The home locale layout now wraps its header, main content, and footer in a flex container with minimum-height styling and applies the Source_Sans_3 font class.

Changes

Home layout styling

Layer / File(s) Summary
Layout container and font
docs/src/app/[locale]/(home)/layout.tsx
Layout replaces its fragment with a styled div, applies Source_Sans_3, and preserves the existing header, main, and footer structure.

Estimated code review effort: 2 (Simple) | ~5 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately reflects the main change: previewing Source Sans 3 on marketing pages.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch font-preview/source-sans-3

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/src/app/`[locale]/(home)/layout.tsx:
- Around line 1-4: Reorder the imports in the layout module so external
dependencies from next/font/google and react appear first, alphabetized within
the external group, followed by the internal `@/components` imports in
alphabetical order.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a32cd44e-8951-47d5-81cb-ee2ec0e197cb

📥 Commits

Reviewing files that changed from the base of the PR and between e1dda9b and e11b28f.

📒 Files selected for processing (1)
  • docs/src/app/[locale]/(home)/layout.tsx

Comment on lines 1 to 4
import { CustomHeader } from "@/components/CustomHeader";
import { Footer } from "@/components/Footer";
import { Source_Sans_3 } from "next/font/google";
import type { ReactNode } from "react";

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Group external imports before internal imports.

The newly added external imports for next/font/google and react are placed after the internal @/components/ imports. As per coding guidelines, imports must be grouped by external first, then internal (alphabetical within groups).

♻️ Proposed fix
-import { CustomHeader } from "`@/components/CustomHeader`";
-import { Footer } from "`@/components/Footer`";
-import { Source_Sans_3 } from "next/font/google";
-import type { ReactNode } from "react";
+import { Source_Sans_3 } from "next/font/google";
+import type { ReactNode } from "react";
+
+import { CustomHeader } from "`@/components/CustomHeader`";
+import { Footer } from "`@/components/Footer`";
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
import { CustomHeader } from "@/components/CustomHeader";
import { Footer } from "@/components/Footer";
import { Source_Sans_3 } from "next/font/google";
import type { ReactNode } from "react";
import { Source_Sans_3 } from "next/font/google";
import type { ReactNode } from "react";
import { CustomHeader } from "`@/components/CustomHeader`";
import { Footer } from "`@/components/Footer`";
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/src/app/`[locale]/(home)/layout.tsx around lines 1 - 4, Reorder the
imports in the layout module so external dependencies from next/font/google and
react appear first, alphabetized within the external group, followed by the
internal `@/components` imports in alphabetical order.

Source: Coding guidelines

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.

1 participant