daisy.laflamme

Learning · November 15, 2026

Webflow through a React/Angular developer’s eyes

A React and Angular developer’s notes on learning Webflow: classes, components, CMS, variables, and adapting to desktop-first breakpoints.

  • webflow
  • react
  • angular
  • css
  • accessibility

I spent nearly a decade building Angular and TypeScript interfaces: shared UI libraries and configuration-driven layouts for many brands on one platform. Lately I’ve been working in React and Next.js. To learn Webflow properly, I built a blog in it. Here’s how its mental model mapped to mine, and where it didn’t.

What felt familiar

Classes are a design system in disguise. A Webflow class works like a utility or BEM class. Combo classes work like modifiers: .card plus .is-featured. Name them with intent and you get a reusable system. Skip that and you end up with div-block-47.

Components are components. Webflow Components with properties and slots feel close to React props and children, or Angular @Input() and <ng-content>. Build one once, use it everywhere, and change it in one place.

The CMS is your data layer. A Collection works like a typed data source. A Collection List is basically .map() in React or @for in Angular, with fields bound to elements instead of passed as props or inputs.

Variables are design tokens. Color, spacing, and type variables, with modes for light and dark, felt like the CSS custom properties and theme files I already maintain.

What took adjusting

Breakpoints cascade down, not up. I design mobile first. Webflow’s base breakpoint is desktop, and styles cascade down to tablet and phone, while larger breakpoints cascade up. Once I stopped fighting it and checked every element at each breakpoint, it clicked. It also made me more deliberate about what each screen size really needs.

No state, just interactions. There’s no useState, no signals, no services, no RxJS streams. Interactions handle the visual states, such as hover, scroll, and open or closed. That’s enough for marketing sites, and anything more complex is where custom code or DevLink comes in.

The visual editor is the source of truth. In React or Angular, the code is the design. In Webflow, the canvas is. My habits still apply: semantic tags, one H1, labelled links, alt text, and checking contrast. I just set them in a panel instead of writing them in code.

Takeaway

Webflow doesn’t replace engineering thinking. It rewards it. The same principles that keep a React or Angular codebase maintainable keep a Webflow site maintainable: reusable components, consistent naming, tokens over hard-coded values, and accessibility from the start.

Where I learned: Learning Webflow – Adapting our design for mobile (LinkedIn Learning) (opens in a new tab)

All notes