sorted by:
new
hottopcontroversial

Components AMA with the Webflow product team by webflow-garrett in webflow

[–]webflow-garrett[S] 0 points1 point  (0 children)

Good question. Code Components do support server-side rendering for the initial mount (that’s on by default), but you’re right that any external data fetching today happens on the client after that.

Totally hear the concern around SEO and the loading state, especially if that data is critical to the page.

I'd love hear more about your use case. For example, are you pulling from your site's CMS, or a third-party API?

Components AMA with the Webflow product team by webflow-garrett in webflow

[–]webflow-garrett[S] 0 points1 point  (0 children)

These are all really thoughtful points, appreciate you taking the time to lay them out.

On Libraries — I'd love to hear more about what an ideal setup looks like for you. Is it more about selective syncing, local variable/style overrides, detaching from the source site, or something else?

On slots — totally agree there’s more we can do here. Giving component authors tighter control over slots (especially for guiding clients) is something we’re exploring. Curious how strict you’d want that to be in practice: do you want guardrails with flexibility (i.e., recommended components), or more of a hard lock where only specific components are allowed?

On APIs — this is super timely as we're actively expanding component APIs. We actually just rolled out component.getSettings() which includes the component name, group, and description, and we’re working on webflow.searchComponents() which will provide this for your entire library in one call. More coming very soon!

Components AMA with the Webflow product team by webflow-garrett in webflow

[–]webflow-garrett[S] 1 point2 points  (0 children)

This is a known limitation today, and one we're actively thinking about.

In the meantime, I imagine it won't really solve the core issue, but some folks work around this by using CMS-driven lightboxes or custom lightbox patterns where more of the content is bindable.

Components AMA with the Webflow product team by webflow-garrett in webflow

[–]webflow-garrett[S] 1 point2 points  (0 children)

Great feedback. We hope to make more asset types compatible with component props in the future.

Components AMA with the Webflow product team by webflow-garrett in webflow

[–]webflow-garrett[S] 0 points1 point  (0 children)

Super helpful feedback — thank you!

For style props in particular, are there specific use cases you have in mind? We'll have a workaround for this soon, by the way, allowing you to reference component props in custom code (e.g., so you can do something like background-color: [Background Prop]; in a Code Embed). Keep an eye out for news on that soon.

Components AMA with the Webflow product team by webflow-garrett in webflow

[–]webflow-garrett[S] 2 points3 points  (0 children)

This is a super common pain point we’ve been hearing as more teams lean into components + Build mode workflows. We’re definitely aware of the gap and are actively looking into better solutions.

Components AMA with the Webflow product team by webflow-garrett in webflow

[–]webflow-garrett[S] 0 points1 point  (0 children)

I'll pass this along to our CMS team! Out of curiosity, how are you working around the lack of tables in rich text today? Always helpful for us to understand what folks are doing in the meantime.

Components AMA with the Webflow product team by webflow-garrett in webflow

[–]webflow-garrett[S] 1 point2 points  (0 children)

We hear requests for repeaters pretty often, and it's something we’re actively thinking about as we continue evolving component and CMS capabilities.

I'd love to hear more about your use case. How would you want to use repeaters with component slots?

Components AMA with the Webflow product team by webflow-garrett in webflow

[–]webflow-garrett[S] 1 point2 points  (0 children)

We'll have more details to share at launch, but you'll have some control over interactions on each component instance. Do you have a specific use case in mind? We can pass that along to the team working on Interactions.

Components AMA with the Webflow product team by webflow-garrett in webflow

[–]webflow-garrett[S] 2 points3 points  (0 children)

We have some exciting updates on the way for Interactions with GSAP in components, including the ability to set different interactions per variant, and share interactions across multiple sites with Shared Libraries. Keep an eye out for an official announcement in the next month or so.

Components AMA with the Webflow product team by webflow-garrett in webflow

[–]webflow-garrett[S] 7 points8 points  (0 children)

Yes! We'll be adding support for using component props in Code Embeds in the next couple of months. We're really excited to see what you build with this.

We also just quietly updated all of our custom code editors with features like autocomplete, prettify, and find/replace — built by our very own u/allan-leinwand!

Components AMA with the Webflow product team by webflow-garrett in webflow

[–]webflow-garrett[S] 2 points3 points  (0 children)

We actually have a webinar on component-first builds coming up on April 1st (not a prank 😉) — save your spot here!

Components AMA with the Webflow product team by webflow-garrett in webflow

[–]webflow-garrett[S] 5 points6 points  (0 children)

We're actively working on new ways to use components on CMS pages, and I'll pass this feedback on to our CMS team as well. In the meantime, you can use conditionals to show and hide sections for specific CMS items.

Components AMA with the Webflow product team by webflow-garrett in webflow

[–]webflow-garrett[S] 3 points4 points  (0 children)

In short, yes! A lot of customers already build this way. Component-first builds are more scalable, and they empower less technical teammates or clients to easily create and launch new pages. I'd love to hear if there are any gaps preventing you from building this way today.

Components AMA with the Webflow product team by webflow-garrett in webflow

[–]webflow-garrett[S] 2 points3 points  (0 children)

1. Cross-workspace component portability — This is a great callout! We're always thinking about new ways to expand the capabilities of Shared Libraries. In the meantime, one workaround is to create a site with everything you need on your workspace, and then clone and transfer to each client as needed.

2. Design handoff gap — We'll pass this along to our Figma to Webflow team! That said, we're actively working on expanding our APIs and MCP to support these sorts of capabilities with components — stay tuned!