Your platform

The admin, the content model and the theme system of your platform: what a client will see every day and what you will customise.

What: The visual canvas where you build with real HTML elements and CSS properties: the Navigator shows the element tree, the Style panel sets CSS.
Why: Webflow writes the code for you, but every panel maps to HTML and CSS, so web basics transfer directly.

Watch out

Dragging elements around like a design tool without understanding the element tree they create.

Also called margin, padding, display, box model

What: Every element is a box with content, padding, border and margin. The Style panel sets them, and display (block, flex, grid) decides how children are arranged.
Why: Almost every layout bug comes from a box you did not expect: extra margin, a fixed width, or the wrong display setting.

Also called global class, class naming, Client-First, combo class

What: Classes hold styles you reuse across elements. A combo class adds a variation on top of a base class, such as button plus is-secondary.
Why: A small, well named class system makes a site consistent and quick to change. Frameworks such as Client-First give naming rules.

Watch out

Styling each element with its own new class, which leaves hundreds of near duplicate classes.

Also called flexbox, breakpoint

What: Flexbox and grid arrange children. Styles set on the base breakpoint cascade down to tablet and phone, where you override only what changes.
Why: Designing on the base breakpoint first and adjusting smaller ones keeps responsive work small.

Watch out

Fixing a phone layout on the desktop breakpoint, which then breaks every larger screen.

Also called symbols, component properties

What: Reusable pieces such as a navbar or a card, edited once and updated everywhere. Properties expose text, images or links that change per use.
Why: Components keep repeated elements consistent and let a client or teammate change content without breaking the structure.

Also called collection list, collection template page, reference field

What: A collection is a content type (Blog posts, Team, Projects) with fields. Collection lists show items on any page; a template page renders each item at its own URL.
Why: Structured collections let a client add a case study or a job without touching design, and give each item a clean, indexable page.

Watch out

Building each blog post as a static page, which the client cannot add to without the Designer.

Also called Site plan, Workspace plan

What: A Site plan (per site) sets hosting, CMS item limits and features. A Workspace plan (per team) sets how many people can build and how many unhosted sites you keep.
Why: Quoting a client means choosing the right Site plan for their content and traffic, and deciding whose Workspace the site lives in.

Watch out

Launching on a plan whose CMS item limit the client will hit within months.

Go deeper