The point of this question is why we can't start using it now with a fallback that does the same thing but with JS.
Why should chromium users wait? very soon majority of the users will have that feature, why should they keep getting less performant and often stuttering animations via JS libraries?
We are generating React/Remix app atm, but our architecture is designed to support other frameworks as well.
It is achieved by using data as a source of truth, not the code. Web tooling is very fragmented. People have too many opinions on how to write components and that makes it nearly impossible to have components written by hand and then synced back into the UI without enforcing a huge amount of constraints. You will end up writing code in such a way that the UI can handle.
Notion: data should work, we are going to record a demo, but Rich Text is not supported yet for every CMS, only those who have an HTML option, see compatibility: https://docs.webstudio.is/university/foundations/cms
We will add them one by one, with full Rich Text support.
Standard compliance, especially in something like a website builder should be a top priority. If the builder doesn't work in major browsers, why there be any confidence that the sites it produces will?
So, you are saying that there is no plan for it to work outside of Chrom(ium) browsers? It doesn't solve the problem of forcing someone to use a specific browser to use the platform.
It does not inspire confidence in an end product will work everywhere and be of high quality when the product to create it is buggy and limited.
It is a privacy leak to tell Github about what other websites or products you are using, that you otherwise wouldn't if you just used normal email/password signup.
GDPR only has a tangental relation to privacy. It might be "GDPR compliant" for me to publish my nudes to twitter, but I've still (voluntarily) lost some privacy for doing so.
Syncing and publishing what? What's so difficult about `git push` which pushes to GitHub and automatically deploys to Vercel? This doesn't look cool, but those two features are not going to be the ones I'll seek after.
Syncing the site data from builder to local fs and then building everything and configuring the app for publishing to vercel.
Just pushing to github only helps you if you only have static html/css if you wanted to publish a site as gh-page ... I guess you need to clarify your use case
Webflow actually helps with all those things. Webstudio doesn't have much yet accessibility features on canvas, because this comes next, but the performance - man it feels like a lifetime spent on optimizing it with the help of lots of different tools. we hit 100% on lighthouse score consistently, the webstudio.is landing is built with webstudio.
I am confused, we only have a download button at the bottom of the page, but "Get early access" button everywhere else. It is much harder to find download than to open the browser version ...
Similarity to Webflow is not a bug, its a feature. It's designed to feel familiar for Webflow developers. This product is built for them.
Check out this video to learn how Design Tokens work in Webstudio. It's built with full knowledge of Webflow Style selector. You are talking to an ex style system engineer from Webflow lol.
Oh! I probably shouldn't write comments before coffee. What happened was that I saw the sign-up page and assumed it was just for creating an account, rather than accessing the web builder. I should have realized what was going on when the same login screen appeared in the downloaded app.
I'm familiar with Webflow and the design tokens make sense to me, but I don't think it's a natural abstraction for non-web developers. I saw that you're ex-Webflow, I just meant to express a general frustration with how existing builders deal with reusable styles - it totally makes sense in the context of targeting devs who already know the Webflow UX. For what it's worth, I've been working on a site builder for the past few months and ended up with a similar solution, so this criticism is partly a projection of my own struggles.
Anyway, thanks for replying! The project looks great, I look forward to see what you end up with wrt versioning and animations.
