projectwallace / projectwallace/projectwallace.com
blog: you should lint your dist CSS
Open
Beginner friendly
Nobody has claimed this yet.
page: blog
- Dominant language
- Svelte
- Stars
- 3
- Forks
- 0
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 11
Description
link to our own stylelint plugin, make a convincing point that bundlers/processors are great but you should know what ends up in the browser.
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
Locate the site's blog content area and the project's own stylelint plugin before drafting. The post is done when it makes a convincing case for linting distributed CSS, acknowledges bundlers and processors, links to the plugin, and explains why knowing what reaches the browser matters.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- content
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100