Refactor(frontend): add all colors

[alcercu]

Summary by CodeRabbit

• New Features

  • Updated the footer's background gradient colors for improved visual appeal.
  • Introduced new color definitions in the Tailwind CSS configuration to enhance the overall theme.

• Bug Fixes

  • Removed outdated color entries to streamline the color palette.

[coderabbitai]

Walkthrough

The changes involve modifications to the styling of the Footer component in the Footer.tsx file and updates to the Tailwind CSS configuration in tailwind.config.ts. The Footer component's background gradient colors have been altered, while the Tailwind configuration has seen several color definitions added, removed, and updated, focusing on refining the color palette without affecting the underlying logic or functionality of the components.

Changes

File	Change Summary
frontend/src/components/Footer.tsx	Updated the class name for the outer <div> to change background gradient colors.
frontend/tailwind.config.ts	Modified color definitions by removing and adding several colors, including updates to "kleros-purple" and "primary-purple."

Poem

In the footer where colors blend,
A gradient change, a stylish trend.
With blues and purples, bright and bold,
A tale of hues, a sight to behold.
Hop along, let’s celebrate,
New colors dance, oh, isn’t it great? 🐇🌈

---

🪧 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 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 or @coderabbitai title 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

🧹 Outside diff range and nitpick comments (1)

frontend/tailwind.config.ts (1)

14-16: Consider renaming "stroke" to follow naming convention.

The color naming follows a clear hierarchical pattern (primary/secondary), but "stroke" deviates from this convention.

Consider renaming to something more descriptive of its purpose, like:

-"stroke": "#42498F",
+"border-primary": "#42498F",

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between ab1333f and b032f01.

📒 Files selected for processing (2)

• frontend/src/components/Footer.tsx (1 hunks)
• frontend/tailwind.config.ts (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• frontend/src/components/Footer.tsx

🔇 Additional comments (2)

frontend/tailwind.config.ts (2)

22-23: LGTM! Background colors create a nice depth effect.

The sequential background colors (#1B003F -> #220050) provide a subtle depth while maintaining readability.

---

17-21: Verify color contrast ratios for accessibility.

The new color palette looks cohesive, but we should ensure it meets WCAG accessibility guidelines for text readability.

Let's verify the contrast ratios: