Docs / Design

Components

A component is a block you can reuse. Change it once and every synchronized copy updates, or insert it as an independent starting point.

Last updated

Use components for things that repeat: a header, a footer, a call to action, a testimonial card, a pricing table.

Create a component

  1. Select a single block. It can contain other blocks inside it, such as a whole section or card.

  2. Open the block action menu and choose Create component.

  3. Give it a name.

  4. Decide whether it should synchronize.

The component is saved to the project and appears in the slash menu under Components.

A component must start from one block. If you need several blocks to move together, group them first.

Synchronized components

A synchronized component stays linked to its source. When you edit one instance, every other instance changes too.

This is the right choice for:

  • A header or footer used on many pages.

  • A call to action that should stay consistent.

  • A card design used in several places.

If you want one instance to differ, do not edit it in place. Create a separate component or use a non-synchronized copy.

Non-synchronized components

A non-synchronized component is a reusable starting point. Each time you insert it, you get an independent copy that you can edit freely.

This is useful for:

  • A card layout you want to reuse with small differences.

  • A section you often start from but rarely keep identical.

  • A design you want to adapt per page.

Later inserts still start from the saved component, so updating the source changes future copies, not the ones already placed.

Insert a component

Type / on an empty line and open the Components group. Pick the component.

You can place a component inside a page, a section, a column, or another component.

Edit a component

Double-click a synchronized component instance to edit its source. The editor opens the component on its own, with the same tools as a page.

When you close it, every instance updates in the working copy. Publish the site to send the change live.

Components and pages

A component belongs to the project, not to one page. The same header can appear on every page, and editing it once updates all of them.

If you delete a component, instances that still point at it show as missing. Remove or replace those instances before deleting the source.

Components and translations

Components can be translated like pages. The structure is shared across languages, and the text is translated in the Translations area.

Read Translations for the workflow.

When not to use a component

Do not use a component for something that appears once. A normal block is easier to edit.

Do not use a synchronized component for content that must differ on every page. Use a non-synchronized copy or a repeater instead.

Do not nest a component inside itself. Remake prevents circular references, but the result is confusing to edit.

A simple starting recipe

For a site header:

  1. Build the header on the home page: logo, menu, and a call to action.

  2. Select the whole header block.

  3. Create a synchronized component named "Header".

  4. Insert it on the other pages.

  5. Edit the header component when you need to change the navigation.

Then check the menu on mobile, where it may collapse or change layout.

Remake

A website builder that works like a document. CMS, forms and EU hosting included.

Resources

© 2026 Remake. All rights reserved.