[go: up one dir, main page]

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

Ditch PurgeCSS, configure uswds to use only tablet #1112

Merged
merged 2 commits into from
Aug 20, 2024

Conversation

hanbyul-here
Copy link
Collaborator

Description of Changes

  • This PR ditches PurgeCSS - because purgecss cannot be configured in scale with react-uswds now.
  • This PR also configures USWDS design system to use only tablet breakpoints, so we don't end up with multiple screen helper classes

Copy link
netlify bot commented Aug 19, 2024

Deploy Preview for veda-ui ready!

Name Link
🔨 Latest commit 1470c33
🔍 Latest deploy log https://app.netlify.com/sites/veda-ui/deploys/66c38dd246571d00087f643f
😎 Deploy Preview https://deploy-preview-1112--veda-ui.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Collaborator
@dzole0311 dzole0311 left a comment

Choose a reason for hiding this comment

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

Great idea about the breakpoints!

postcss.config.js Show resolved Hide resolved
@hanbyul-here hanbyul-here merged commit 38f6ec6 into main Aug 20, 2024
8 checks passed
@hanbyul-here hanbyul-here deleted the uswds-react-component branch August 20, 2024 12:58
hanbyul-here added a commit to US-GHG-Center/veda-config-ghg that referenced this pull request Aug 22, 2024
Close NASA-IMPACT/veda-ui#1098


I used this PR as a test-bed to figure out how to write a component
using USWDS design system. The rules that I tried to stick is like
below.

1. Use uswds-react whenever possible.
2. Use USWDS helper, utility className whenever possible. 
3. Use Styled components for prop-based dynamic styling. 
4. Use classnames for static custom styles

🤔 I think, as a team, we only agreed on 1. altogether. (And I expressed
my bias towards 2.) - other steps came to be kind of natural, but this
might not be the case for everybody. So let's discuss if anything
doesn't look right!


@faustoperez - I made the whole (- link area) card to be clickable


This PR NASA-IMPACT/veda-ui#1112 needs to be
merged first

@slesaad - 🤔 I am not sure what to do with ui module because this change
does require the update of UI module. Should I let this PR sit until the
next release?
sandrahoang686 added a commit that referenced this pull request Aug 27, 2024
## 🎉 Features
- 🦗 
## 🚀 Improvements
- Adding styles & Configurations for R3
#1104
- Create new raster paint layer module and factor out
BaseTimeseriesProps #1105
- Remove PurgeCSS, configure USWDS to use only tablet breakpoints
#1112
- Open an external link in a new tab
#1116
- Expose USWDS card style
#1119

## 🐛 Fixes
- Do not render exploration component unless urlAtom is on the right
page #1106
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.

2 participants