chore: fix footer size/colors

[arcoraven]

Summary by CodeRabbit

• Style

  • Updated footer background to light grey and reduced its minimum height.
  • Adjusted icon and link colors to darker shades and refined hover effects.
  • Improved logo link appearance with new opacity and sizing styles.

• Documentation

  • Updated footer text to reflect new copyright and license information.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
web3-onboard-docs	🛑 Canceled (Inspect)			Jul 23, 2025 6:09am

[coderabbitai]

Walkthrough

The footer component was updated to revise copyright and license text, combine them into a single div, and update branding references. Visual styles were changed, including background color, icon link colors, and sizing. A new style for the logo link was added. No changes were made to the component's structure or exported entities.

Changes

File(s)	Change Summary
docs/src/lib/components/Footer.svelte	Updated copyright/license text, combined text divs, changed branding, revised styles/colors.

Estimated code review effort

1 (~2 minutes)

---

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

docs/src/lib/components/Footer.svelte (2)

45-46: Consider moving inline style to CSS class for better maintainability.

While the functionality is correct, the inline style="max-height: 20px;" could be moved to the .logo-link CSS class for better separation of concerns.

-      <img src={PoweredByTw} alt="Powered by thirdweb" style="max-height: 20px;" />
+      <img src={PoweredByTw} alt="Powered by thirdweb" />

And update the CSS:

  a.logo-link {
    opacity: 0.8;
+   max-height: 20px;
  }

---

90-95: Logo link opacity styling looks good.

The opacity transition provides appropriate visual feedback. If you decide to move the inline max-height style to CSS (as suggested earlier), consider targeting the img element within the logo-link for the height constraint.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 0e1e2a3 and 23fdbe4.

📒 Files selected for processing (1)

• docs/src/lib/components/Footer.svelte (3 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Checks

🔇 Additional comments (4)

docs/src/lib/components/Footer.svelte (4)

13-14: LGTM! Text updates are consistent and appropriate.

The copyright year update to 2025 and rebranding from Blocknative to thirdweb align with the PR objectives. The punctuation consistency (removing periods) is a good touch.

---

52-52: Good consolidation of license and copyright text.

Combining the license and copyright into a single div simplifies the markup while maintaining readability.

---

72-73: Verify color contrast compliance with the new light background.

The background color change from dark to light grey and reduced height align with the PR objectives. Ensure the dark icon colors (#242835 region text and rgba(20,20,20) icons) provide sufficient contrast against the new light background (#ebebed).

---

79-79: Icon styling updates are consistent with the light theme.

The dark icon colors and reduced hover scale work well with the new light background. The opacity transition (0.8 → 1.0) provides appropriate visual feedback.

Also applies to: 83-84