Evidence review
What to inspect before changing anything
Start with the delivered website and the real user journey. Record the current state so the team can distinguish an observed problem from an assumption and compare the same surface after deployment.
- 01Inventory similar components and prop combinations
- 02Find copy-pasted markup with small differences
- 03Review conditional branches inside universal components
Implementation
A practical improvement plan
Make the smallest coherent change that solves the observed problem. Keep normal code review, accessibility, security and product checks in the loop instead of optimizing for the scan alone.
- 01Extract stable behavior and tokens
- 02Keep distinct content models separate
- 03Document the intended extension points
Verification
How to verify the result
Verification should test the intended outcome and the most likely regression. Use the production delivery path whenever headers, caching, rendering or third-party services affect the result.
- 01Test representative variants and edge content
- 02Compare bundle and maintenance impact
- 03Review visual and semantic consistency
Common pitfall
A shortcut to avoid
Combining every similar surface into one configurable super-component can make change slower and less predictable.
Further reading
Primary guidance and references
These sources provide standards, security guidance or the interpretation framework used to keep this guide bounded. Product-specific implementation still requires review in the actual codebase.