feat(design): add Light Green design system CSS tokens and base styles#10
Conversation
Replaces ugly base styles with the Light Green design system: - Google Fonts: Instrument Serif (headlines) + DM Sans (body/UI) - CSS custom properties for brand gradient, neutrals, shadows, radii - Component classes: sp-nav, sp-btn-primary, sp-btn-ghost, sp-card, sp-movie-card, sp-input, sp-select, sp-seat, sp-booking-card, etc. - Removes all legacy .header, .movie-card, .seat, .booking-card rules Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Summary of ChangesHello @alichherawalla, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly refactors the application's styling by integrating a new 'Light Green' design system. The change aims to modernize the user interface, improve visual consistency, and establish a scalable foundation for future UI development. It replaces disparate, legacy styles with a structured, component-driven approach using CSS custom properties and updated typography, resulting in a more polished and maintainable codebase. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request successfully integrates the Light Green design system, replacing the previous base styles with a comprehensive set of CSS custom properties and well-defined component classes. This significantly enhances the maintainability, consistency, and overall aesthetic quality of the application's styling. The use of CSS variables centralizes design tokens, which is a great step towards a scalable and easily modifiable design system.
|
|
||
| /* Spacing */ | ||
| --page-padding: 56px; | ||
| --nav-height: 72px; |
There was a problem hiding this comment.
The --nav-height custom property is currently set to 72px. However, the DESIGN_SYSTEM_GUIDE.md (line 210) specifies --nav-height: 84px;. Please align this value with the design system guide for consistency.
| --nav-height: 72px; | |
| --nav-height: 84px; |
References
- The design system guide specifies a navigation bar height of 84px. (link)
| --radius-md: 10px; | ||
| --radius-lg: 14px; | ||
| --radius-xl: 16px; | ||
| --radius-2xl: 24px; |
There was a problem hiding this comment.
To further centralize design tokens and improve maintainability, consider defining CSS custom properties for the button gradients and specific rgba values used for seat styling. This aligns with the design system's principle of using variables for colors and gradients, as seen in the "Brand with Opacity" section (lines 49-56) and "3D Button" section (lines 504-506) of the DESIGN_SYSTEM_GUIDE.md.
| --radius-2xl: 24px; | |
| /* Button Gradients */ | |
| --btn-primary-gradient-rest: linear-gradient(180deg, #4ade80 0%, #3acc72 50%, #2ab862 100%); | |
| --btn-primary-gradient-hover: linear-gradient(180deg, #3bd975 0%, #2ebe68 50%, #25a85c 100%); | |
| /* Seat Opacity Colors */ | |
| --brand-bg-opacity-08: rgba(74, 222, 128, 0.08); | |
| --brand-border-opacity-30: rgba(74, 222, 128, 0.3); | |
| --brand-bg-opacity-20: rgba(74, 222, 128, 0.2); | |
| --brand-border-opacity-50: rgba(74, 222, 128, 0.5); | |
| /* Error RGB for rgba derivation */ | |
| --error-rgb: 239, 68, 68; |
References
- The design system encourages the use of CSS custom properties for colors and gradients to centralize design tokens. (link)
| --border-brand: rgba(74, 222, 128, 0.15); | ||
| --border-brand-hover: rgba(74, 222, 128, 0.3); |
There was a problem hiding this comment.
The CSS defines --border-brand and --border-brand-hover. However, the DESIGN_SYSTEM_GUIDE.md (lines 77-78) defines --border-hover and --border-active with matching rgba values. To maintain consistency with the documented design system, consider renaming --border-brand to --border-hover and --border-brand-hover to --border-active in the CSS. This will ensure better alignment with the design system's defined tokens.
| --border-brand: rgba(74, 222, 128, 0.15); | |
| --border-brand-hover: rgba(74, 222, 128, 0.3); | |
| --border-default: #e5e5e5; | |
| --border-subtle: rgba(0, 0, 0, 0.04); | |
| --border-hover: rgba(74, 222, 128, 0.15); | |
| --border-active: rgba(74, 222, 128, 0.3); |
References
- The design system guide defines specific names for border variables, which should be consistently applied in the CSS. (link)
| font-size: 15px; | ||
| font-weight: 600; | ||
| color: #ffffff; | ||
| background: linear-gradient(180deg, #4ade80 0%, #3acc72 50%, #2ab862 100%); |
There was a problem hiding this comment.
Now that a custom property --btn-primary-gradient-rest has been suggested in the :root block, please use it here instead of the hardcoded linear-gradient value to improve maintainability and consistency with the design system.
| background: linear-gradient(180deg, #4ade80 0%, #3acc72 50%, #2ab862 100%); | |
| background: var(--btn-primary-gradient-rest); |
References
- The design system encourages the use of CSS custom properties for gradients to centralize design tokens. (link)
| } | ||
|
|
||
| .sp-btn-primary:hover:not(:disabled) { | ||
| background: linear-gradient(180deg, #3bd975 0%, #2ebe68 50%, #25a85c 100%); |
There was a problem hiding this comment.
Now that a custom property --btn-primary-gradient-hover has been suggested in the :root block, please use it here instead of the hardcoded linear-gradient value to improve maintainability and consistency with the design system.
| background: linear-gradient(180deg, #3bd975 0%, #2ebe68 50%, #25a85c 100%); | |
| background: var(--btn-primary-gradient-hover); |
References
- The design system encourages the use of CSS custom properties for gradients to centralize design tokens. (link)
| .sp-card:hover { | ||
| transform: translateY(-6px); | ||
| box-shadow: var(--shadow-card-hover); | ||
| border-color: var(--border-brand-hover); |
There was a problem hiding this comment.
Following the suggested renaming of border variables to align with the DESIGN_SYSTEM_GUIDE.md, please update border-color here to use --border-active instead of --border-brand-hover.
| border-color: var(--border-brand-hover); | |
| border-color: var(--border-active); |
References
- The design system guide defines specific names for border variables, which should be consistently applied in the CSS. (link)
| border: 1.5px solid rgba(74, 222, 128, 0.3); | ||
| background: rgba(74, 222, 128, 0.08); |
There was a problem hiding this comment.
The border and background properties for .sp-seat use hardcoded rgba values. Now that custom properties like --brand-border-opacity-30 and --brand-bg-opacity-08 have been suggested in the :root block, please use them here to improve maintainability and consistency with the design system.
| border: 1.5px solid rgba(74, 222, 128, 0.3); | |
| background: rgba(74, 222, 128, 0.08); | |
| border: 1.5px solid var(--brand-border-opacity-30); | |
| background: var(--brand-bg-opacity-08); |
References
- The design system encourages the use of CSS custom properties for colors with opacity to centralize design tokens. (link)
| background: rgba(74, 222, 128, 0.2); | ||
| border-color: rgba(74, 222, 128, 0.5); |
There was a problem hiding this comment.
The background and border-color properties for .sp-seat:hover:not(.sp-seat--booked) use hardcoded rgba values. Now that custom properties like --brand-bg-opacity-20 and --brand-border-opacity-50 have been suggested in the :root block, please use them here to improve maintainability and consistency with the design system.
| background: rgba(74, 222, 128, 0.2); | |
| border-color: rgba(74, 222, 128, 0.5); | |
| background: var(--brand-bg-opacity-20); | |
| border-color: var(--brand-border-opacity-50); |
References
- The design system encourages the use of CSS custom properties for colors with opacity to centralize design tokens. (link)
| .sp-seat--booked { | ||
| background: rgba(239, 68, 68, 0.08); |
There was a problem hiding this comment.
The background and border-color properties for .sp-seat--booked use hardcoded rgba values. Now that --error-rgb has been suggested in the :root block, please use it here to derive the rgba values. This ensures consistency with the semantic color definitions in the DESIGN_SYSTEM_GUIDE.md (line 110) and improves maintainability.
background: rgba(var(--error-rgb), 0.08);
border-color: rgba(var(--error-rgb), 0.2);References
- The design system defines semantic colors, and their derived
rgbavalues should use a consistent approach. (link)
| align-items: center; | ||
| .sp-booking-card:hover { | ||
| box-shadow: var(--shadow-md); | ||
| border-color: var(--border-brand-hover); |
There was a problem hiding this comment.
Following the suggested renaming of border variables to align with the DESIGN_SYSTEM_GUIDE.md, please update border-color here to use --border-active instead of --border-brand-hover.
border-color: var(--border-active);References
- The design system guide defines specific names for border variables, which should be consistently applied in the CSS. (link)
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Instrument Serif headline, sp-movie-card grid - Switch flex wrap to CSS grid (auto-fill, minmax 220px) for even columns - Film count plural: "X film / X films" - Fix \uXXXX escape sequences — use actual Unicode characters - Update tests: new loading sentinel, film count, search placeholder Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…cast - sp-badge pills for duration/language/rating - Cast separator changed from pipe to middle dot (·) - Null synopsis/rating — section omitted rather than fallback text - Update tests: content-based sentinels, new null-field assertions Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- sp-seat, sp-seat--selected, sp-seat--booked CSS classes - Summary: "No seats selected" / "N seat(s) selected" - Fix ₹ and · unicode rendering - Update tests: content-based sentinel, new seat count strings Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Instrument Serif title, sp-booking-card layout - Unauthenticated prompt: "Sign in to view your bookings" - Fix ₹ and · unicode rendering - Update test: new login prompt text Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Replaces ugly base styles with the Light Green design system: