fix: global css apply layer base

[andostronaut]

This is an automated pull request for branch develop

Summary by CodeRabbit

• New Features

  • Introduced new CSS variables for improved UI element styling, including colors for cards, popovers, and charts.
  • Added new shadow classes for light and dark themes.

• Bug Fixes

  • Removed outdated background and foreground variables to enhance theme consistency.

• Refactor

  • Updated the theme configuration by removing the dark mode property, streamlining the documentation theme settings.

[coderabbitai]

Walkthrough

The pull request introduces significant modifications to the styling and theme configuration of the project. In globals.css, previous CSS variable definitions for background and foreground colors are removed and replaced with a new set of color variables under the @layer base directive, utilizing HSL color representation. Additionally, the body selector is removed, and a new html selector is added. In theme.config.tsx, the darkMode property is removed from the theme configuration, indicating a shift in theme options.

Changes

File	Change Summary
src/styles/globals.css	- Removed root CSS variables --background and --foreground. - Added new color variables under @layer base. - Removed body selector; added html selector for scroll-behavior. - Introduced new classes: .shadow-light and .shadow-dark.
theme.config.tsx	- Removed darkMode property from the theme configuration.

Possibly related PRs

• feat: create docs folder page and set use dark mode to false in theme config #7: The changes in theme.config.tsx regarding the removal of the darkMode property are directly related to the main PR's modifications in the same file, indicating a consistent approach to theme configuration.

Poem

🐰 In the land of styles, bright and bold,
New colors emerge, a story told.
Shadows dance in light and dark,
A theme reborn, igniting a spark.
With HSL hues, we paint the day,
A rabbit's cheer for the CSS way! 🌈

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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 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: 2

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 041080e and a08380c.

📒 Files selected for processing (2)

• src/styles/globals.css (3 hunks)
• theme.config.tsx (0 hunks)

💤 Files with no reviewable changes (1)

• theme.config.tsx

🧰 Additional context used

🔇 Additional comments (2)

src/styles/globals.css (2)

Line range hint 9-36: Well-structured theme variables with semantic naming.

The use of HSL colors and semantic variable names improves maintainability. The organization under @layer base follows best practices for CSS architecture.

---

Line range hint 38-64: Verify color contrast ratios for dark theme.

While the dark theme implementation looks good, it's important to verify that all color combinations meet WCAG contrast requirements, especially for chart colors.

Consider using a color contrast checker tool during development to ensure all combinations meet WCAG 2.1 Level AA standards (4.5:1 for normal text, 3:1 for large text).