The case for a real component library
If you build on Webflow for a living, you already have a component library. It's just spread across a dozen old projects, a Notion page of snippets, and your own memory. Every new build starts with the same archaeology: which past site had that navbar? where's the smooth-scroll setup that didn't fight the page transitions? what was the form markup that actually validated?
Baselumen is that scattered knowledge, collected into one place and made dependable. It's a component library application: browse production-ready Webflow embeds and React components, preview them live, and copy them in a single click.
What's inside
Baselumen ships the building blocks we reach for on nearly every engagement:
- Navigation systems — mega menus, mobile drawers, and sticky bars with the accessibility wiring already done.
- Hero and layout sections — editorial headers, feature grids, and pricing tables that hold up on real content, not just lorem ipsum.
- Motion — smooth-scroll and reveal setups tuned so they cooperate with Webflow's interactions instead of fighting them.
- Forms — field, label, and state treatments that look right and behave right out of the box.
Each component comes with a live preview, the full code, and notes on where it shines and where it doesn't.
Why copy-paste usually breaks — and why this doesn't
The problem with grabbing a snippet off the internet is that it's a coin flip. Does it handle dark mode? Is it keyboard-accessible? Will it blow past a platform character limit the moment you customize it? Most of the time you find out after it's already in production.
Everything in Baselumen is held to the same bar as our client work: accessibility-checked, dark-mode aware, and tuned to stay under platform limits. The goal is simple — paste it, and it works the first time. No copy-paste-and-pray.
Beta, and free early access
Baselumen is in beta today with free early access. We add components on the same cadence we build them for real projects, so the library grows in the direction working studios actually need.
If you ship Webflow sites and you're tired of re-deriving the same patterns, take a look — and tell us which component you'd want to never write from scratch again.
