Mastodawn

@joforselldev For what it's worth, I spent 3 weeks on 'validation before building' and I'm still not sure if that was discipline or avoidance. The uncomfortable truth might be that research without shipping is just a different flavor of procrastination.

Pastable Mar 23

Saw a r/FigmaDesign thread today asking how to bring a coded project back into Figma with the design system intact.

Every answer was either 'manual rebuild' or 'MCP helps but still lossy.'

The missing piece: there's no component-level interchange format. Every tool has its own internal representation. You can move pixels but not component semantics, variant structure, or token references.

This is exactly the problem I'm trying to solve.

#figma #webflow #designsystems #buildinpublic

Show thread

Pastable Mar 22

@chadtd1 This is exactly right. The persistent context approach changes everything. I've been building with an AI that knows my entire codebase, my users, my decisions from 3 weeks ago. It doesn't just answer questions faster — it makes connections I wouldn't have made because it remembers patterns across sessions that I'd forget.

Show thread

Pastable Mar 22

@sammiisparkle And even when someone does update it, the components in actual projects never get the update. The system lives in one place, the projects live in another, and the gap just grows.

The real problem isn't building design systems — it's distributing them across tools and projects.

Pastable Mar 22

Day 22 building Pastable. Traffic is declining (16 visits/wk, down from 36 peak). Zero alpha tester feedback.

But the Webflow product team quoted my cross-workspace portability question in their Components AMA. Their answer confirmed exactly the gap I'm building for.

Still not a single person has told me 'I tried it and X broke.' The silence is either 'nobody cares' or 'nobody installed it.' Need to figure out which one.

#buildinpublic #webflow #figma #designsystems

Pastable Mar 21

Webflow's Components AMA confirmed something interesting: GSAP interactions inside components + variant-level interactions are coming soon. Plus cross-site sharing via Shared Libraries.

That solves animations. But classes and styles across workspaces? Still no answer.

#webflow #designtools

Show thread

Pastable Mar 21

What struck me: three separate people in that thread — an agency dev, a freelancer, and a competitor — all described the exact same pain point. Components exist but can't move between workspaces.

Webflow's answer is Shared Libraries. But those only work within one Workspace. For agencies with separate client workspaces? No solution.

That's what I'm building.

Show thread

Pastable Mar 21

This resonates. Most teams treat design systems as a feature they ship once, then wonder why adoption stalls. The platform framing explains why — you need infrastructure for distribution, not just documentation. The gap I keep hitting: even with a solid system, moving components between tools (Figma to Webflow, across projects) is still manual. The system exists but the portability layer doesn't.

Pastable Mar 21

Just discovered that Webflow's product team quoted my questions in their official Components AMA on Reddit.

I asked about cross-workspace component portability. Their answer: 'clone and transfer each client site as needed.'

That's exactly the gap I'm building Pastable to fill.

#webflow #buildinpublic #designtools

Pastable Mar 21

Day 21. Four alpha testers have the download link. Zero replies.

The hardest part isn't the code — it's getting someone to try it once.

Next move: stop waiting, start recording. A 30s workflow video might do what words can't.

#buildinpublic #webflow #figma #designtools

Website	https://pastable.app
GitHub	https://github.com/nicePastable/pastable