Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: first pass at updating the documentation #399

Merged
merged 1 commit into from
Mar 12, 2024

Conversation

aversini
Copy link
Collaborator

@aversini aversini commented Mar 12, 2024

Summary by CodeRabbit

  • Documentation Updates
    • Updated styling logic based on story prefixes in the documentation.
    • Enhanced the documentation structure with the addition of "Styles*" section and improved Google Fonts loading.
    • Revised Getting Started section to reflect changes in button properties, installation instructions, and configuration steps for integrating TailwindCSS.
    • Updated Styles documentation to better align with the new structure, including changes in story titles and instructions for installing and configuring style packages.

Copy link

coderabbitai bot commented Mar 12, 2024

Walkthrough

The overarching change focuses on refining the documentation and component configuration for a UI library. This includes updating story prefixes from "system" to "styles," enhancing the installation guide with split packages for better management, revising TailwindCSS integration instructions, and adjusting UI elements for consistency. These modifications aim to improve user experience, streamline styling logic, and facilitate easier adoption of the library components.

Changes

Files Change Summary
.../.ladle/components.tsx, .../DarkMode.stories.tsx, .../Typography.stories.tsx Updated story prefixes from "system--" to "styles--" and adjusted component properties for consistency.
.../.ladle/config.mjs Added "Styles*" section, removed commented-out style block, and added preconnect links for Google Fonts.
.../GettingStarted/1-overview.stories.tsx, .../4-usage.stories.mdx, .../5-alpha-beta.stories.tsx Removed noBorder property from ButtonIcon in various components.
.../GettingStarted/2-Installation.stories.tsx Expanded functionality to display multiple npm packages in a table format and updated installation command.
.../GettingStarted/3-configuration.stories.tsx Revised CSS usage instructions for TailwindCSS integration and introduced a TailwindCSS plugin.

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.
    • 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 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 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.

Copy link

Bundle Size (components)

Status File Size (Gzip) Limits
style.css 6.42 KB 8 KB
index.js 7.75 KB 20 KB
vendor.js 65.07 KB 67 KB

Overall bundle size: 79.24 KB
Overall status: ✅

Bundle Size (form components)

Status File Size (Gzip) Limits
index.js 4.66 KB (+1 B +0.02%) 20 KB
vendor.js 44.49 KB 67 KB

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

Bundle Size (system)

Status File Size (Gzip) Limits
style.css 6.7 KB 8 KB
index.js 1.74 KB 3 KB
vendor.js 44.49 KB 46 KB

Overall bundle size: 52.93 KB
Overall status: ✅

Copy link

@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.

Review Status

Actionable comments generated: 3

Configuration used: .coderabbit.yaml

Commits Files that changed from the base of the PR and between 9df2dcc and 59afefa.
Files selected for processing (9)
  • packages/documentation/.ladle/components.tsx (1 hunks)
  • packages/documentation/.ladle/config.mjs (1 hunks)
  • packages/documentation/src/GettingStarted/1-overview.stories.tsx (1 hunks)
  • packages/documentation/src/GettingStarted/2-Installation.stories.tsx (3 hunks)
  • packages/documentation/src/GettingStarted/3-configuration.stories.tsx (3 hunks)
  • packages/documentation/src/GettingStarted/4-usage.stories.mdx (2 hunks)
  • packages/documentation/src/GettingStarted/5-alpha-beta.stories.tsx (1 hunks)
  • packages/documentation/src/Styles/DarkMode.stories.tsx (2 hunks)
  • packages/documentation/src/Styles/Typography.stories.tsx (3 hunks)
Files skipped from review due to trivial changes (1)
  • packages/documentation/src/Styles/DarkMode.stories.tsx
Additional comments: 11
packages/documentation/.ladle/config.mjs (2)
  • 14-14: Adding the "Styles*" entry to the list of sections is a good step towards reorganizing the documentation content to better categorize styling-related documentation. This aligns with the PR's objective of improving content organization.
  • 14-14: The addition of preconnect links for Google Fonts is a performance optimization that can improve the loading times of fonts in the documentation. This is a good practice for enhancing user experience.
packages/documentation/src/GettingStarted/3-configuration.stories.tsx (2)
  • 42-44: The updated CSS usage instructions clearly emphasize the requirement of TailwindCSS for styling the components within the UI-Components library. This clarification is beneficial for users integrating the library into their projects.
  • 52-52: Introducing the TailwindCSS plugin from @versini/ui-styles to optimize unused styles is a significant improvement. It aligns with the goal of enhancing performance and user experience by reducing the final bundle size.
packages/documentation/.ladle/components.tsx (1)
  • 67-67: Updating the condition check from "system--typography" to "styles--typography" within the Provider component is a necessary change to reflect the shift in naming conventions from "System" to "Styles". This ensures that the correct styling logic is applied based on the story prefix.
packages/documentation/src/GettingStarted/2-Installation.stories.tsx (2)
  • 17-44: The introduction of a table format to display information about multiple npm packages is a clear and organized way to present the division of the UI-Components library into separate packages. This approach makes it easier for users to understand the structure and dependencies of the library.
  • 88-88: Updating the installation command to include @versini/ui-styles along with @versini/ui-components reflects the need for both core components and styling capabilities provided by these packages. This change ensures users are aware of the necessary dependencies for optimal library usage.
packages/documentation/src/Styles/Typography.stories.tsx (4)
  • 5-5: Updating the title from "System/Typography" to "Styles/Typography" accurately reflects the shift in naming conventions and reclassification within the project's design system. This change ensures consistency and clarity in the documentation.
  • 217-217: Renaming the story from "Basic" to "QuickStart" provides a clearer indication of the purpose of the story, guiding users more effectively through the initial setup and usage of typography styles.
  • 226-229: Modifying the installation instructions to specify installing the @versini/ui-styles package aligns with the emphasis on TailwindCSS for styling. This change clarifies the necessary dependencies for users.
  • 234-242: Updating the configuration to import from @versini/ui-styles instead of @versini/ui-components is a crucial change that reflects the division of the UI-Components library into separate packages. This ensures users correctly integrate TailwindCSS and the provided plugin for styling.

Comment on lines 23 to 28
<ButtonIcon
spacing={{ t: 8 }}
labelLeft="Installation"
noBorder
onClick={linkTo("getting-started--installation")}
>
<IconNext monotone />
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 NOTE
This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [17-17]

The removal of the noBorder property from the ButtonIcon component in the "Installation" button aligns with the broader effort to standardize component properties and appearances. Ensure this change is consistently applied across all relevant components for visual consistency.

@aversini aversini merged commit d6c8e82 into main Mar 12, 2024
5 checks passed
@aversini aversini deleted the docs-first-pass-at-updating-the-documentation branch March 12, 2024 00:08
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.

1 participant