Components you own.
WHAT THE APPROACH IS
Components copied into your project rather than installed as a dependency.
WHAT THAT PROVIDES
Full control of the code No version upgrades imposed on you Styling entirely yours No runtime dependency
WHAT IT COSTS
Maintenance is yours Fixes and improvements are not received automatically More code in your repository
WHAT IT TYPICALLY BUILDS ON
Unstyled accessible primitives, with styling applied.
WHAT UNSTYLED PRIMITIVES PROVIDE
Correct behaviour and accessibility, with no visual opinion.
WHY THAT COMBINATION IS APPEALING
The hard part is provided, and the appearance is entirely yours.
WHAT IT SUITS
Projects with a specific design Teams wanting control Applications expected to be maintained for a long time
WHAT TO ESTABLISH
That someone will maintain the copied components.
WHAT TO DO WHEN UPSTREAM IMPROVES
Review changes and apply them deliberately.
WHAT TO AVOID
Copying components and then never reviewing them again.
WHAT TO DOCUMENT
Which components came from where, and at what version.
