Developer Office Hours: October 👂

Developers
1

Hey everyone! Vic from Webflow here!

The Developer Relations team is hosting our next Developer Office Hours on Tuesday, October 28 at 10 AM Eastern.

We’ll cover what’s new and coming soon for developers building on Webflow:

  • :cloud: Webflow Cloud
  • :brick: Code Components (Including some very cool demos)
  • :robot: MCP Server
  • :electric_plug: APIs & Apps

After that, we’ll open the floor for questions, feedback, and discussion. Can’t make it? No worries. Drop your questions below and we’ll cover them in the session. Afterwards, we’ll share a recording so you can catch up.

Join us if you’re:

  • Building integrations or Apps with the Webflow APIs
  • Experimenting with the MCP Server
  • Getting started with Code Components or Webflow Cloud

(If your focus is site/page custom code, GSAP, or IX3, this session might not be the most relevant — but stay tuned for upcoming events tailored to those areas!)

We’re planning to make this a monthly series, so come help shape the future of development at Webflow.

Click this link to sign up! and drop your questions below.

3 Likes
3

Great to see this will be a monthly series :partying_face:

I won’t be able to join live, but I have a question about Code Components:

Do you plan to create a marketplace or community hub where people can share their Code Components?

If so, what are the best practices regarding the styling of Code Components? Since CCs are isolated elements in the DOM, it is not easy to change the styles inside Webflow after importing the component into a project. Currently, the only way to change colours, sizes, etc. in Webflow is to define variables in the Code Component outside of Webflow, which can then be overridden in Webflow by creating all the variables manually. This is, of course, not a user-friendly way. If Code Components can be shared in a marketplace, how do you plan to manage the styling of the components?

I’m looking forward to hearing your answers. Enjoy your live session!

3 Likes
4

Hi Vic! I totally missed this, but would love to know where the link to the recording is once it’s available. I’m doing a lot of work with the MCP server and am interested to see what others are doing with it!

1 Like
5

Hey, we couldn’t make it and I would love to know where you have shared the recording?

6

@victoriaplummer can you share the recording?

7

Hey there! Thank you for all your questions!

Here’s the recording to our first Developer Office Hours
https://www.youtube.com/watch?v=e3lAuf44lfA

Tune in to watch Julian Galluzzo from Memberstack join the Webflow DevRel team where we show off:

Missed the last one? Sign up for our next office hours :backhand_index_pointing_down:
:date: Next Office Hours: Nov 20 @ 3PM ET
:link: Register here

We’ll answer questions, share updates, and spotlight your builds — don’t miss it! :flexed_biceps:

1 Like
8

Didn’t forget about you @Schuschi_Eyes

:puzzle_piece: Community Hub for Code Components

We’re still exploring what a Webflow hub for code components could look like, but our goal is definitely to make it easier for developers to share components with teams and clients, much like templates and libraries today. Stay tuned for updates!

:artist_palette: Best Practices for Design

Definitely check out @viratpatel’s demo from our recent Developer Office Hours for tips on styling code components. He shows how to inherit Webflow styles inside a CMS Slider.

In the demo, he shows a React hook he built that brings global styles into the Shadow DOM , which is a great reference for maintaining consistency between Webflow and custom code components. We’re working on a full guide explaining how and why he did this. I’ll follow up here once that’s published.

In the meantime, we recommend letting your Code Components inherit styling from the site using the applyTagSelectors property. It’s the easiest way to make sure your components feel native to each project.

I hope that helps and hope you can make the next one!