Interesting observation from digging into clipboard formats:
Everyone talks about Figma MCP as the design-to-code bridge. But MCP only gives you API access — it can't touch your clipboard.
When you copy in Figma, it's Kiwi (proprietary binary). Webflow uses XscpData. These carry the real component data and they're invisible to MCP.
The gap between "AI reads your Figma file" and "you can move components between tools" is bigger than people think.
Week 1 of real user testing.
First Webflow veteran is trying Pastable today — someone who's been building sites for 13 years. They want to use it on a real client project.
I spent yesterday fixing preview rendering so components actually look right in the library. Small thing, but it's the difference between "this feels broken" and "oh I can actually see what I saved."
Nervous but excited. If it works for someone at that level, we're onto something.
Fixed a frustrating rendering bug today — components pasted from Webflow were showing up blank in the preview.
Turns out: the iframe was too narrow, triggering mobile breakpoints. Now I render at desktop width (1440px) and scale down with CSS transform. Looks exactly like the original.
Small win but it makes the whole app feel real.
Had an interesting exchange on LinkedIn about Finsweet Client-First and reusing components across Webflow projects. The consensus: even with standardized naming, components only "mostly" snap into place.
That gap between "mostly works" and "actually works" is exactly what I'm trying to close with Pastable.
I keep rebuilding component systems when I switch tools. Webflow to Figma, Figma to Webflow. The friction is brutal.
How do you handle it? Copy-paste and rebuild every time? I'm trying to build something to fix this — genuinely curious what the workflow looks like for others.
I'm pretty sure the "staging" environment is usually non-public, but I guess good enough to hand to an HOA. Seems unprofessional, but maybe not a huge deal.
And hey, look at #WebFlow getting those panopticon bucks.
Genuine question for designers and front-end devs:
When you start a new project, how do you handle components you've already built before? (navbars, forms, cards, footers...)
Do you:
- Copy from an old project?
- Rebuild from scratch?
- Use a component library?
- Something else?
Curious what the real workflow looks like. No wrong answers.
🚀 Milestone: Pastable UIs now builds on Linux, macOS, AND Windows!
First alpha binaries shipping to early access testers this week.
Copy components from Figma or Webflow → save to your local library → paste back anytime. No cloud, no account.
Sign up for early access: https://pastable.app
#buildinpublic #indiedev #webdev #figma #webflow #opensource
Building a desktop app to save and reuse UI components across design tools.
Today's progress: rebuilt the component library with 13 professional items — navbars, footers, forms, badges, alerts, and more.
The goal: copy a component from Figma or Webflow, save it, paste it into any project. No plugins needed.
pastable.app
Question for designers who work across multiple tools:
When you copy a component from Figma and need it in Webflow (or vice versa), what's your workflow?
Do you rebuild from scratch every time? Use screenshots as reference? Something else?
Genuinely curious how people handle this — it's a problem I think about a lot.
👋 Hello Fediverse!
We're building Pastable — a desktop app that lets you save UI components from Figma, Webflow, or any website and reuse them anywhere.
Copy a component, it lands in your local library. Paste it back into any project — as a real, editable component. Not a screenshot.
Early access is open: https://pastable.app
Built for designers and no-code builders who are tired of rebuilding the same UI from scratch.
#design #webflow #figma #nocode #ux #buildinpublic #opensource
Webflow permet-il de créer des sites web accessibles ?
Cet article liste les fonctionnalités d'accessibilité de Webflow et propose des solutions concrètes pour rendre les sites web conformes au RGAA :
https://a42.fr/webflow-accessibilite
Bravo à notre stagiaire de la formation « Auditer l’accessibilité » qui applique brillamment ses nouvelles compétences !
Why Webflow Isn’t the Future—Yet, by @webdesignerdepot.bsky.social:
https://webdesignerdepot.com/why-webflow-isnt-the-future-yet/
"Chuyển đổi thiết kế thành sản phẩm trên Webflow: Bạn nên làm gì? Câu hỏi từ cộng đồng Reddit. #Webflow #ThiếtKếWeb #Workflow #DesignToBuild"
https://www.reddit.com/r/SaaS/comments/1qqclkt/hey_everyone_can_i_know_what_is_the_workflow_in/
Tăng traffic từ 10 lên 10.700 chỉ trong 3 tháng! Bí quyết là tìm và thêm "từ khóa ma" mà Search Console đã chỉ ra vào nội dung trên Webflow. Thủ thuật SEO đơn giản, không cần viết code.
Waht an amazing intro to web design
https://www.youtube.com/watch?v=PcFXt8o7uGg
The whole webflow video series works perfectly for @silex too 🙏
Người xây dựng sản phẩm số lần đầu được hỗ trợ với hệ thống 4 giai đoạn (Khám phá, Phát triển, Marketing, Bảo trì), 60+ trang hướng dẫn, tìm kiếm AI & 1,800 nguồn đã lọc qua 4,000 giờ xây dựng. #DigitalProduct #Startup #SảnPhẩmSố #UXUI #Figma #Webflow
https://www.reddit.com/r/SaaS/comments/1pqwhna/i_built_a_navigation_system_for_anyone_building/
Webflow → Next.js без фронтендеров: как мы перенесли 500+ страниц сайта через Cursor
Всем привет, я сооснователь мессенджера Пачка и отвечаю, в том числе, за маркетинговую инфраструктуру. Нам нужно было оперативно увезти наш сайт с Webflow: 500+ страниц, блог и база знаний. При этом возвращать фронтенд-разработку в режим постоянной поддержки сайта мы не хотели. Поэтому рассматривали конструкторы и CMS, но быстро поняли, что это будет работа в минус. Все усилия на переезд лишь вернули бы сайт в рабочее состояние, не дав новых возможностей. В итоге мы решили вести разработку и поддержку сайта в Cursor. То есть переписать его на NextJS с помощью AI агентов. Такая связка дала понятную модель страниц, быструю доставку статики и ISR для контента, а также возможность отказаться от отдельной CMS за счёт MDX. В спокойном режиме за два месяца удалось полностью переписать сайт и запустить его в прод. Ниже делимся практическим опытом этого переезда.
https://habr.com/ru/articles/977198/
#nextjs #webflow #вайбкодинг #cursor #aiагенты #миграция_сайта #отказ_от_cms
