magento / magento/community-features
Split css styles to certain page instead include in one to improve page render
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 46
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
This feature i think should have in core. Current when user visit homepage some styles included but never used
Such as class checkout-*, customer-account-*
Example
cms home
cms_index_index.xml
we will have common.css + cms.css
catalog_product_view.xml
we will have pdp.css
Category
catalog_category_view.xml
we will have category.css
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the page examples named in the issue: cms_index_index.xml, catalog_product_view.xml, and catalog_category_view.xml. Determine how common.css, cms.css, pdp.css, and category.css should be scoped so pages do not load unused checkout-* or customer-account-* styles. Done means each listed page loads only its relevant styles while retaining the shared styles.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- frontend, performance, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100