Skip to content

Export

Making components

HTFlow deliberately does not decide what should be a component. You do, once the site is in Webflow and you can see what actually repeats.

Why HTFlow does not do this for you

Whether a card should be a Component depends on how the site will be maintained, who edits it, and what is going to be driven by the CMS instead. That is a decision with context HTFlow does not have, and guessing wrong is more work to undo than to do.

Creating one

  1. Find the repeated block
    Navigation, footers, cards and testimonial blocks are the usual candidates. The consistent class names make them easy to spot in the Navigator.
  2. Select its outermost element
    Pick the wrapper that carries the BEM block class, not an element inside it.
  3. Create the component
    Right-click and choose Create Component, then name it after the block.
  4. Add properties for what varies
    Text, links and images that differ between instances become component properties.
  5. Replace the other instances
    Swap the remaining copies for the component so a future change lands once.

A practical order

Componentise the shell first — navigation and footer — because those are the blocks that appear on every page and cost the most to fix later. Cards and sections can wait until the content is settled.