Skip to content

Conversation

bradleycamacho
Copy link
Member

Adds a new footer containing compliance links. This adds custom styling for the future too in case we want to alter it, but I can't seem to figure out how to make the total footer height smaller than it's current height.

@bradleycamacho bradleycamacho requested a review from a team as a code owner January 8, 2025 22:15
Copy link

netlify bot commented Jan 8, 2025

Deploy Preview for docs-optimism ready!

Name Link
🔨 Latest commit f71d4e9
🔍 Latest deploy log https://app.netlify.com/sites/docs-optimism/deploys/677f01421fae980008184736
😎 Deploy Preview https://deploy-preview-1232--docs-optimism.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 site configuration.

Copy link
Contributor

coderabbitai bot commented Jan 8, 2025

📝 Walkthrough

Walkthrough

The pull request introduces changes to the website's footer visibility and content. In the styles/global.css file, a CSS rule that previously hid the footer has been removed, allowing the footer to be displayed on the page. Simultaneously, the theme.config.tsx file has been updated with a more comprehensive footer implementation. The new footer includes multiple anchor links to important pages such as Terms of Service, Community Agreement, and Privacy Policy. Additionally, it features a copyright notice and social media icons. These changes enhance the footer's functionality by making it visible and providing users with quick access to key legal and community resources.

Possibly Related PRs

Suggested Reviewers

  • sbvegan

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.

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

@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

🧹 Nitpick comments (1)
theme.config.tsx (1)

69-72: Remove unnecessary empty lines.

These consecutive empty lines don't serve any purpose and should be removed for better code cleanliness.

  footer: {
    text: (...),
  },
- 
- 
- 
-
  sidebar: {
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 46a3b86 and 99bbeef.

📒 Files selected for processing (2)
  • styles/global.css (0 hunks)
  • theme.config.tsx (1 hunks)
💤 Files with no reviewable changes (1)
  • styles/global.css
⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: Redirect rules - docs-optimism
  • GitHub Check: Header rules - docs-optimism
  • GitHub Check: Pages changed - docs-optimism
  • GitHub Check: pr-workflow

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

🧹 Nitpick comments (1)
theme.config.tsx (1)

57-57: Use dynamic year for copyright notice.

Instead of hardcoding the year, consider using new Date().getFullYear() to automatically keep the copyright year current.

-        <div>© 2025 Optimism Foundation. All rights reserved.</div>
+        <div>© {new Date().getFullYear()} Optimism Foundation. All rights reserved.</div>
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 99bbeef and f71d4e9.

📒 Files selected for processing (2)
  • next-env.d.ts (1 hunks)
  • theme.config.tsx (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • next-env.d.ts
⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: Redirect rules - docs-optimism
  • GitHub Check: Header rules - docs-optimism
  • GitHub Check: Pages changed - docs-optimism
  • GitHub Check: pr-workflow
🔇 Additional comments (2)
theme.config.tsx (2)

48-56: Consider moving inline styles to a CSS module.

The inline styles make the code harder to maintain. A previous review already suggested moving these styles to a CSS module.


59-69: Improve link accessibility.

The links lack hover states and focus indicators, which are important for accessibility. A previous review already suggested these improvements.

@sbvegan sbvegan merged commit 1b30f02 into main Jan 8, 2025
5 of 8 checks passed
@sbvegan sbvegan deleted the enable-footer branch January 8, 2025 23:43
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.

3 participants