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] guidance on optimizing css for production #3376

Open
davidsainez opened this issue Nov 7, 2024 · 0 comments
Open

[docs] guidance on optimizing css for production #3376

davidsainez opened this issue Nov 7, 2024 · 0 comments
Assignees
Labels
documentation Because documentation is important and shouldn't be broken question Further information is requested sync to jira These will be pushed into adobe internal jira

Comments

@davidsainez
Copy link

Hello, I'm looking for guidance on optimizing payload sizes for production.

I see a short section in the README, but a more detailed starting point would be useful.

My main concern is any caveats to watch for when minimizing and tree-shaking. Ideally, I would like my includes to be fairly general (for ease of development) and then prune any unused styles when building for production. I assume this guidance would also help other consumers of this library. Thanks all for the wonderful code.

@davidsainez davidsainez added the question Further information is requested label Nov 7, 2024
@castastrophe castastrophe added sync to jira These will be pushed into adobe internal jira documentation Because documentation is important and shouldn't be broken labels Dec 11, 2024
@castastrophe castastrophe changed the title Guidance on optimizing css for production [docs] guidance on optimizing css for production Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Because documentation is important and shouldn't be broken question Further information is requested sync to jira These will be pushed into adobe internal jira
Projects
None yet
Development

No branches or pull requests

3 participants