Description
RE Guideline 3.5 Redundancy and duplication in code should be avoided: https://w3c.github.io/sustainableweb-wsg/#redundancy-and-duplication-in-code-should-be-avoided and criterion https://w3c.github.io/sustainableweb-wsg/star.html#WD05-3 .
My suggestion is that we do not need to name a specific methodology in the guideline
Within CSS and JavaScript, use methodologies (like BEM) and systems like DRY and WET to optimize the arrangement and output of your source code.
Could become:
Within CSS and JavaScript, use an organizing methodology and systems like DRY and WET to optimize the arrangement and output of your source code.
Or "use organizing methodologies" alternatively.
This change suggestion was inspired to me from a few observations:
- It seems more appropriate for the success criterion and as an example rather than given full guideline weight
- There is some reasonable debate about BEM in some places. I know of variations to BEM, and considerable back and forth discussion about BEM and other methodologies. Even if its featured strongly as an example it might make sense to change the guideline and leave the success criterion as an example with BEM rather than specific guideline to be "like BEM".
- Per @andreadavanzo - It makes sense to be agnostic to specific methodologies, generally speaking
Metadata
Metadata
Assignees
Type
Projects
Status