Create and reuse a component
These instructions are reviewed against the app source. Final-installer walkthroughs are still pending. Check platform availability and requirements before installing. Windows is an updates list, outside the 1,000 beta places.
Turn a repeated element into a main component, then place linked instances on a page. Changes to the main component reach its instances while respecting their overrides.
Before you start
Work on Primary in a local page. Have a small frame or stack containing text, such as a card, ready to reuse. Select that element rather than the outer page root.
Create and insert
- Select the element in Layers. Give it a descriptive name, such as
Info card. - Open Components and choose Create component from selection. MODO uses the selected element to create the main component and leaves an instance in its place.
- Open the component with Open Info card in Components. Confirm the Main component indicator before editing.
- Change the main component's padding or text color. Return to the page through Pages and inspect the instance.
- Select the page container where another card should go. In Components, choose Insert Info card. You now have another linked instance.
Customize an instance with a prop
A prop is a field the main component exposes for each instance to customize.
- Open the main component. In Components → Props, choose Add prop. Set Prop name to
label, keep Type as Text, and enter a Default such asA thoughtful detail. - Select the main component's text layer. In Design, open the ring-shaped Link control beside Text and select
labelunder Component props. The text now reads from that prop. - Return to the page and select one card instance. In Design, find its Instance properties and change
label. - Check the other instance. It should keep its own value or the component default.
Use the reset control for a prop to return to its default. Detach instance converts an instance to ordinary nodes, ending its link to the component.
Check your result
A shared design change appears in both cards, while a customized text prop affects only the selected instance.
Common problems
- An internal layer cannot be edited directly: edit the main component or expose the field as a prop.
- Component creation is blocked on Mobile: return to Primary for component-definition changes.
- A component cannot be inserted: check that you are not inserting it into itself.
- Deleting the main component warns about instances: the listed instances become plain nodes. Review the effect before confirming.
Related guides
Need a correction? Tell us