docs: better release tags information

[aversini]

Summary by CodeRabbit

• New Features

  • Introduced a component variant and release tag rendering based on the stage parameter.
  • Added support for light and dark mode styling.
  • Enhanced the Getting Started documentation with a new section explaining component stages, including visual indicators.

• Documentation

  • Updated the Getting Started guide with examples and explanations of component stages using a new layout and visual components.

[coderabbitai]

Walkthrough

The recent updates enhance the documentation and UI components by introducing a switch statement for dynamic rendering based on component stages, improving visual themes with light and dark mode support, and refining the presentation of component stages with a new layout and the addition of a "pill" indicator. These changes collectively aim to improve user experience and clarity in the documentation interface.

Changes

File Path	Change Summary
.../.ladle/components.tsx	Introduced a switch statement for determining variant and releaseTag in renderImportLine.
.../.ladle/styles.css	Added light and dark mode styling for .ladle-background.
.../src/GettingStarted/5-alpha-beta.stories.tsx	- Imported Pill component. - Added paragraph on component stage indicator. - Implemented Flexgrid layout with headings and Pill components for stage indication.

---

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>.
  • Generate unit-tests for this file.
• 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 tests 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 generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[github-actions]

Bundle Size (components)

Status	File	Size (Gzip)	Limits
✅	style.css	7.12 KB	8 KB
✅	index.js	16.22 KB	20 KB
✅	vendor.js	65.07 KB	67 KB

Overall bundle size: 88.41 KB
Overall status: ✅

Bundle Size (system)

Status	File	Size (Gzip)	Limits
✅	style.css	2.83 KB	4 KB
✅	index.js	1.74 KB (+1 B +0.06%)	3 KB
✅	vendor.js	44.49 KB	46 KB

Overall bundle size: 49.06 KB (+1 B 0.00%)
Overall status: ✅

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: .coderabbit.yaml

Commits

Files that changed from the base of the PR and between ce92875 and c9fc2a9.

Files selected for processing (3)

• packages/documentation/.ladle/components.tsx (1 hunks)
• packages/documentation/.ladle/styles.css (1 hunks)
• packages/documentation/src/GettingStarted/5-alpha-beta.stories.tsx (4 hunks)

Additional comments: 5

packages/documentation/.ladle/styles.css (1)

• 11-23: The addition of media queries for light and dark color schemes is a good practice for enhancing user experience across different preferences. Ensure the chosen colors align with the project's design system and meet accessibility standards for contrast and readability.

packages/documentation/.ladle/components.tsx (1)

• 11-26: The switch statement for determining variant and releaseTag based on the stage parameter is well-implemented. Consider adding comments to explain the logic, especially the choice of "alpha" as the default case. Also, ensure that all potential stage values are accounted for and align with project requirements.

packages/documentation/src/GettingStarted/5-alpha-beta.stories.tsx (3)

• 4-4: The import of the Pill component is correctly added to support the new functionality introduced in the documentation.
• 22-25: Adding a paragraph to explain the component stage indicator using a "pill" is a helpful addition for user clarity.
• 46-59: > 📝 NOTE

This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [27-80]

Replacing <h2> headings with a Flexgrid layout that incorporates both headings and the corresponding Pill components is a significant improvement for visually representing component stages. Ensure the Flexgrid layout is used consistently and effectively throughout the documentation.