Join the waitlist today at getmiyagi.com!
01.07.2025 20:13
👍 0
🔁 0
💬 0
📌 0
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
Excited to announce the newest Webflow app we've been building 🔥
Miyagi: An AI app for Webflow made up of 3 powerful agents:
• Design Agent: Automate tasks in the Webflow Designer
• Code Agent: Vibe code in Webflow
• CMS Agent: Bulk edit and create content in the CMS
Learn more below 👇
I posted this idea back in 2023, and have really been thinking about it a lot recently.
We really need something like this in the Webflow CMS.
Clients really want the ability to add styled content into the rich text in Webflow, and the workarounds we do have are a terrible client UX.
Here’s a unique little Webflow component we created recently!
Multistep quiz that directs users to the best page suited to their needs
Built with superformjs, which is one of my favorite multistep form libraries as of late!
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
Lately, we’ve been diving deep into component first builds, and the overall results have been great! Now that we've implemented this approach multiple times, I’ve noticed some clear advantages—and a few challenges—I wanted to share 🧵
The Webflow Input Enhancer just got better!
You can now add custom property descriptions and tooltips to your Webflow components!
We built this custom component in Webflow
using GSAP for the animations, and the assets for the image sequence and MP3 files are hosted GitHub pages. (This works like a charm, no need to create a custom server)
New Site Launch for whisperroom.com!
We built 95% of the site using Webflow components, and we incorporated component variants, variable modes, and slots more deeply then we have on any other site. It's amazing to see how easy it is for the client to be able to update and customize the site.
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
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 👇
One of the biggest downsides of chrome extensions for Webflow is that every user has to download these on their browser.
Because of that, we've added a pop-up component that you can add to your projects that will let other users know to download the Webflow Input Enhancer for the best experience.
we're just trying to keep up!
create custom dropdown properties for your
Webflow components!
How do dropdown properties work?
• All dropdown lists live in a single component in your project
• Link to a list via an ID in the property name (this get's hidden by the extension)
• That's it!
ah got it. It would be great if slots worked like the custom elements where you could assign any html tag to them
For your use case does the rich text element not work?
Variable breakpoints are finally here!!!
