Join the waitlist today at getmiyagi.com!

CMS Agent: Perform actions in the CMS like:
- Creating Collections
- Creating Collection Items
- Bulk edits across CMS
- Content Migration

Code Agent - think Cursor built for Webflow. Can code, host & deploy files on your behalf and can also interact with your project to pull class names or even add attributes to elements.

Design Agent - has access to Webflow's designer API & your site context and can perform actions on your behalf like:
- Bulk add Alt Text
- Export/Import all SEO meta data via CSV
- add Aria labels
- Importing Variables
- Building Layouts
- Class Renaming

Nice!

Awesome. What framework are you using btw?

Also this allows a client to unlink the component and be able have more flexibility while still being able to work with that component in build mode.

The benefit here is that it's faster then creating multiple components all from scratch. You can pass over properties in 1 click rather than creating each prop from scratch.

is going to repeat exactly the same on multiple pages (ex. a specifc header layout), you can wrap that component in another component and pass over only the relevant props. (headings, text) You now have global control over that layout and can always unlink it to get back to the Master component

I've run into this challenge - it's basically the line between global control and instance specific flexibility. What I've realized is a great solution though is creating wrapped components.

Essentially you can have your master, flexible component, and then when you notice a section that

Overall, I think the pros outweigh the cons when executed properly. But there are still cases where a component-first approach might be overkill or not the best choice for a particular client.

Have you built with a component first approach? What’s your experience been like? 🚀

Cons
↳ More time & thought must go into it to ensure it's built in a scaleable way
↳ More Timely QA/Post Launch: Once clients start using the project they may need adjustments to the properties
↳ If the client has development background/webflow experience, a standard build may be preferred

Pros:
↳ Easy for clients to edit without having to understand webflow
↳ Makes it difficult for clients to break their site
↳ Speeds up dev time if the project is big enough
↳ Easy to maintain consistency when working a team of devs
↳ Maintain global control over large projects if built correctly

Haven't heard of the Webflow Input Enhancer? Here's a brief summary of what it can do 👉
• Auto suggest css properties, classes, and variables in component props
• Enhance and expand style properties to write instance specific css
• Create dropdown properties for easy editing for clients

webflow.com/made-in-webf...

If the extension is installed, this component will be hidden by default as the page loads. 🚀

The component also includes some code to make sure that the pop up is only ever visible inside the designer, not on the published site.

You can grab the cloneable below 👇

we're just trying to keep up!