Feat/update design - #18
Merged
Merged
Conversation
…n using a new `<NpmVersion />` component, ensuring accurate version representation across all documentation. Adjust build scripts to include package builds before documentation generation for consistency.
…i across components This update introduces a new radius scale based on a single `--radius` variable, allowing for easier customization of corner radii. The new scale includes defined multiples for various sizes, enhancing design consistency. The `radiusBase` export is added to facilitate this change, while existing token names remain unchanged to ensure backward compatibility. Documentation has been updated to reflect these changes.
This commit repoints the neutral core to the shadcn/ui palette, replacing rowkit's blue-tinted greys with zero-chroma greys. It introduces new `gray` and `whiteAlpha` scales, ensuring compliance with WCAG standards for contrast. The selected table row is now neutral, removing brand tinting. Additionally, adjustments to semantic colors and tests for translucent tokens have been made to enhance visual consistency and accessibility.
This update repoints the achromatic and destructive status colors to the shadcn/ui palette, introducing a new `red` primitive scale for danger states. The tooltip color is adjusted to `primary-solid` for better visibility, and the `neutral` color is redefined to match shadcn's `--secondary`. The changes enhance visual consistency and accessibility across components while maintaining existing values for success and warning colors.
…ionality This update introduces a blurred scrim for the dialog overlay, improving visual context by allowing the background to remain legible. The blur is conditionally applied based on support for `backdrop-filter`, ensuring a consistent experience across different environments. Additionally, keyboard navigation is enhanced with a focus trap that prevents users from tabbing to the content behind the dialog, ensuring accessibility and usability. A new `blur` token is added to the design system for this purpose.
…onents This update implements shadcn/ui's focus ring and restyles the Button, Badge, and Skeleton components for consistency. The Button now features a `rounded-md` shape across all sizes, with updated padding and disabled states. The Badge adopts a `rounded-md` style with adjusted text sizes, while the Skeleton is unified under a single `rounded-md` shape. Additionally, the focus ring is refined to enhance accessibility, replacing previous outline styles with a more effective visual indicator.
This update implements a comprehensive restyling of the DataTable components, adopting shadcn/ui's design principles. Key changes include a transparent header with a hairline border, updated row hover effects for better pointer indication, and refined padding for a denser layout. The focus ring is now consistently applied across various components, enhancing accessibility. Additionally, selection checkboxes and other interactive elements have been adjusted to match shadcn's specifications, ensuring a cohesive user experience.
This update renames core semantic tokens to match shadcn/ui's naming scheme, enhancing consistency across the design system. Key changes include renaming `--color-surface` to `--color-card`, `--color-text` to `--color-foreground`, and adjusting related utility classes accordingly. Additionally, the design language is further refined with updated color tokens for success and warning states, ensuring a cohesive visual experience. Documentation has been updated to reflect these changes, and the shadcn attribution is now included in all relevant READMEs.
…e design This update refines the terminology across various tokens and UI components to align with the reference design. Key changes include updating comments and documentation to replace "shadcn" with "reference design" for clarity and consistency. Additionally, adjustments to component styles, such as badges and buttons, ensure a cohesive visual experience while maintaining accessibility standards. The focus ring and other design elements have been standardized to reflect the reference design's specifications.
… documentation This commit renames the TablePagination component to Pagination to better reflect its functionality as a standalone pager. The change includes updates to component names, types, and documentation, ensuring consistency across the codebase. Additionally, the pagination controls have been adjusted for improved accessibility and visual clarity, with the current page now outlined rather than filled. Documentation has been updated to reflect the new component name and its props.
…Pagination rename This commit updates the versioning of the `TablePagination` component rename to `Pagination` from major to minor. The change reflects the intent to maintain a 0.x line, ensuring that the transition to version 1.0.0 follows real-world application feedback. The renaming clarifies the component's functionality as a standalone pager, removing misleading implications of coupling with table structures.
…ed visual separation This commit introduces a new `shadow-sticky-header` token to create an inset shadow for sticky table headers, enhancing the visual distinction between the header and scrolling rows. The change addresses limitations of borders under `border-collapse`, ensuring the header remains visually connected to its rows while scrolling. Updates include modifications to DataTable components and tests to validate the new shadow behavior, ensuring it maintains the correct color token through Tailwind's handling.
This commit addresses layout issues in the DataTable component by ensuring consistent row heights for both loaded and loading states, preventing layout shifts during data loading. It also removes a redundant border rule under the header that caused visual inconsistencies. The changes include adjustments to padding and variant selectors to maintain a cohesive design across the table. Additionally, updates to the DataTable stories ensure that action buttons are rendered correctly for regression testing.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…ustomization This commit adds support for a new `xs` size option and an `icon` prop to the Button component, allowing for more flexible button designs. The default button size is adjusted to 32px with reduced padding for a denser layout, catering to data-heavy interfaces. Additionally, the `icon` prop enables square buttons for icon-only labels, improving visual consistency. Documentation and related components are updated to reflect these changes.
…red styles This commit addresses the issue of zebra striping in demo rows caused by VitePress's default styling, which incorrectly applies grey backgrounds to every other row. The fix involves using `all: revert-layer` on the row selectors to restore the intended styles, ensuring that the component's own background and hover utilities are preserved. Additionally, a test is added to verify that the demo rows are styled correctly without the unwanted striping.
…consistency This commit introduces several enhancements to the color tokens and UI components. Key changes include the introduction of softer, cooler color variants for borders and backgrounds, improving visual clarity and reducing glare in light mode. The `gray` token definitions are updated to reflect these changes, with new values for decorative hairlines and backgrounds. Additionally, UI components such as Button, Input, Select, and Pagination are standardized to share a consistent height and rounded style, ensuring a cohesive design across the application. The updates also include adjustments to the Storybook preview for better alignment with the new styles.
…nsistency This commit refines the styles of Badge and Button components, ensuring a cohesive design language across the UI. Key updates include the introduction of a soft tinted chip appearance for badges, aligning with the overall visual theme. Button styles are adjusted to unify height, radius, and padding with other form controls, enhancing usability and visual clarity. Additionally, the hover effects for DataTable rows are updated to maintain distinct interactions, while the pagination component's button sizes are standardized for consistency. Documentation and tests are also updated to reflect these changes.
…ions This commit updates the ROADMAP.md by relocating planning documents to the `docs/phases/` directory and retiring previous phase specifications. The changes clarify the project's current direction and ensure that only relevant documentation is accessible. Additionally, the VitePress configuration is adjusted to exclude internal planning specs from the published site, enhancing the clarity of the documentation available to users.
This commit deletes several outdated changeset files that are no longer relevant to the project. The removal of these files helps streamline the repository and ensures that only current and applicable documentation is maintained. This cleanup contributes to better organization and clarity within the project.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.