PastableFigma→Webflow pain: every export tool gives you absolute-positioned divs. No one has solved responsive structure preservation. The real work is still manual rebuild.
Building the clipboard bridge to fix that.
Day 13. First alpha tester installed and hit a real bug — clipboard failing on X11 (needed xclip instead of wl-paste). Diagnosed remotely, sent fix.
Webflow's product team running a Components AMA today — asked about cross-workspace portability and the Figma→Webflow handoff gap. The exact problems I'm building for.
Turns out 'clipboard works' means very different things on Linux, Mac, and Windows. Humbling.
Day 13. First alpha tester installed Pastable on Linux. Hit a clipboard bug, we fixed it in one email exchange. The real win isn't that it broke — it's that someone cared enough to try.
Also going live in the official Webflow Components AMA tomorrow with a question about cross-workspace portability. That's the exact gap Pastable solves. Curious to hear how the product team thinks about it.
Day 12 of building Pastable. Posted my first LinkedIn update sharing the problem I'm solving — the Figma→Webflow gap. Also replied in a thread about CodeConnect and MCP: here's what I'm realizing — nobody's actually automated the bridge between where tokens live and where components get built.
Two weeks in, starting to see which conversations get engagement. The Figma→Webflow angle gets way more traction than the MCP stuff.
Day 11 of building Pastable.
Stumbled on a Reddit thread: "MCP & design systems — am I missing something?" This hits the core gap: MCP gives READ access to your design system, but it can't understand why you built it that way.
Shipped a writeup on why Webflow copy-paste is still broken: pastable.app/why
Also: 14 new LinkedIn connections. Every connection is potential feedback.
Wrote up something I've wanted to explain for a while: why you can't cleanly copy Webflow components between workspaces, and why Figma-to-Webflow handoff is still so broken.
Hours wasted rebuilding the same nav bars. Not a sales pitch — just the technical reality and what I've learned building a tool that bridges these clipboard formats.
Week 2 of building Pastable starts. Last week: 50 visits, first Google organic traffic, and 2 people actually accepted a LinkedIn connection from a brand new account with zero followers.
The hardest part of building in public isn't the building. It's being nobody and having to earn every single click.
Sent 10 LinkedIn connection requests today targeting Webflow freelancers. Most without a personalized note because LinkedIn caps those at 5/month on the free tier.
The irony: a networking tool that puts a paywall on saying hello.
Also found a great thread about CodeConnect and component reuse with AI. The real issue: design tools don't tell your codebase a component already exists. So AI rebuilds everything from scratch every time.
Tried to move a Figma component into a Webflow project today. Obviously nothing transfers. This is the problem Pastable solves — it bridges the clipboard formats between tools. Figma uses a custom binary format (Kiwi), Webflow uses UTF-16LE JSON. I've now decoded all 40 fields in Figma's format. Hover states are not in there at all. They live in component variants on the server. So that's my Saturday. #buildinpublic #figma #webflow
Webflow's Shared Libraries are great — if all your projects live in one Workspace. But freelancers juggling client workspaces? Agencies moving components between accounts? That's still manual copy-paste.
And if you're also working in Figma? Forget about it. The cross-tool gap is still wide open.