Choose the right reuse method
A few moving parts are involved here. The points below cover each of them, so you can see the full scope before deciding where to start.
- Use a component for repeated structure within a project.
- Use a shared library when several projects need the same maintained source.
- Use a template when you want its project-level setup and page architecture.
- Copy a section when it is a one-off starting point that will be redesigned.
A safe transfer workflow
Here is the process broken into clear steps. Take them one at a time and check each off before continuing.
- Duplicate or copy the source item without changing the original.
- Move it into the destination project and inspect missing fonts, assets and variables.
- Map colours, type styles and spacing to the destination system.
- Check responsive breakpoints and component variants at real content lengths.
- Publish a test page before replacing the production section.
A visually identical copy can still carry hidden interactions or overrides. Inspect the layers and test every state after moving it.
When to unlink
Unlink when the destination needs a genuinely different lifecycle. Keep it linked when improvements should flow from one source. Unlinking too early creates maintenance drift.
Post-transfer verification checklist
This comes down to a handful of concrete details. Work through the list below and flag the ones you have not covered yet.
- Fonts render as intended rather than falling back to a system font.
- Colour and spacing tokens match the destination project's style set.
- Interactions such as scroll effects and hover states still trigger correctly.
- Images and assets load from the destination project, not the source link.
- Page load performance has not regressed after the addition.
Handover notes for a new team member
Use the list below as a working checklist. Each item is something you can verify or action directly on your own site.
- Record which sections were copied from Marketplace assets and their source.
- Note any component that remains linked to an external library.
- List style tokens that were remapped during the transfer.
- Flag any section that was copied as a one-off and will not receive updates.
- Include the test page URL used to validate the transfer, if kept.