Component Hygiene Quick Reference
Use component rules without overbuilding the library.
“This is only used twice. Do we need a component?” “Only if the two uses should update together or represent the same product pattern.” Frequency alone is not the rule. It separates reuse governance from visual repetition. Main component vs instance override Do not put local content decisions into the main component. What is a component boundary? The smallest reusable unit that should change as one pattern. Too small creates assembly work; too large blocks useful overrides. What should be named in a component set? The purpose, property, and state a teammate needs to search or inspect. Names are part…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in