Thanks for this - interesting that you focused the postmortem on technical lessons (other than #1).
I'm super curious around what the sales strategy was.
I'd imagine for devs, it would have to be around productivity (time saved by exporting vs. manually coding, adherence to consistent CSS standards, etc.).
For designers, I would imagine it would be around taking more of the software dev lifecycle - e.g. designers can now eat up part of the value that front-end dev provides. Based on that, designers should be more in demand, paid more, and so on.
Those seem like huge levers to pull from a PMF perspective, but to your point, maybe it all sounds great until you get into that conversation, and it's really not something that teams are looking for (at least right now).
All credit for the monaco editor to our awesome friends at Stackblitz (stackblitz.com). Gonna announce the depth of that partnership soon ;)
Native VS Code integration is already here! The “3 screens” you see (design, code, preview) are just there for the demo— only the design editor on top is part of Pagedraw. You get to use your regular text editor (VS Code included), and localhost env if you use the full version and install the CLI https://documentation.pagedraw.io/cli/
> Design -> Code is definitely a big problem. Creation time is one, but updating should be easy too.
Updating is super easy if you do the updates in Pagedraw. Since everything is component based, you should never touch the generated code. All the code you write goes in adjacent components that import and are imported by Pagedrawn components. You never need to roundtrip, because you never need to edit the generated code
Right now our compiler has 4 different targets: JSX, CoffeeScript, Javascript (React.createElement), and Typescript. Support for React Native, Angular, and others is coming soon.