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.
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.
You are correct regarding CMS. Same story with e-commerce and other things.
In fact fundamentally the architecture is built around the idea of not having those things built-in but rather providing APIs for others to create integrations with any data source: CMSs, Databases, E-commerce etc.
Webflow and others with built-in CMS have a massive amount of problems, because there is no one CMS that fits all.
Even harder is e-commerce.
So yeah, we are not going to compete on that because we are not building any of it, but instead focusing on architecture to support integrations.
Pro webflow developers use keyboard a lot. In fact with Webstudio we took the keyboard accessibility very seriously, still A LOT to improve.
Visual development is a mixture of mouse and keyboard. Some things are faster with the mouse, some with the keyboard.
The reason some people prefer mouse is not just that they are used to, even though it is true. Its because they know how to be efficient with it very well.
"code is like that but on steroids" - again it can be true in certain use cases, but there is a massive amount of use cases where this is not actually true.
Most of them are around layouts, styling and configuring components.
Visual development is basically declarative programming - its configuring things.
We are actually thinking deeply about the gap between typing and visually manipulating stuff at Webstudio and the plan is to allow a lot of the same UX patterns that you have with text-based coding: copy/pasting things like styles, box shadows, gradients, instances of components etc.
Ability to paste gradients is already there, box shadows comes soon. Writing component code inline will most likely come at some point as well. Linked CSS editor - similar to chrome dev tools for css is also planned.
As you can see there are ways to close the gap and when needed write code.
The most frustrating thing with code is the build tools, compilers etc. These days nobody writes just simple html and css, things are complex. So the benefits of writing code are often completely destroyed by the amount of complexity to deploy the site.
There is a serious knowledge gap between what you just wrote and the actual reality out there. I don't want to convince you of anything, just share the knowledge of what's actually happening. Why tools like Webflow have $4bln valuation and why there are millions of webflow developers.
1. You are looking at it in black/white. Coder vs nocoder. That's not how it is in reality. There is a seriously big amount of people who understand enough of coding to use webflow comfortably but not enough to write code by hand and/or wanting to do so.
2. Designers are used to visual tools. They find their way when tool allows to experiment without first studying how to code and then gradually learn css/html basics if they need to.
3. Building layouts, styling, html structure etc is actually faster with webflow once you understand how it works and learn all the shortcuts.
If you actually care to learn about it, go talk to some pro webflow devs. Some of them will tell you they actualy know how to code, but its less efficient for a lot of use cases.
4. Handoff. A huge problem with building websites is wasted time between a designer and a developer. There is just too many things to consider and a static design in figma is never complete. Webstudio and Webflow aims at solving or at least reducing the handoff by either building directly in Webstudio/Webflow or by keeping figma design low-fidelity just for initial communication with the customer and then moving on to building.
5. This industry has come a long way and these days several tools are also integrating with git-based developer workflows. The goal is to let designers and visual developers to build visual components and design systems in the builder ui and provide those components to developers for further integration.
6. There is a clearly steep learning curve with Webflow. Lots of things are not easy to get. Its not a tool to build a website in 5 minutes, its a tool to learn html/css visually and become pro visual developer. Once you are there, the typical landing sites and marketing pages, even large one are built significantly faster and more presize from design perspective than with coding. I am saying this as an engineer who started building for the web in 2004.
This is not meant to start an argument. Just pointing out a lot of stuff that is understandably not clear to many.
This is true. There are standard use cases like landing/marketing sites, blogs etc that can be done fully visually, and there are custom once where coding is not avoidable.
We have designed it to work for both by providing API and CLI to integrate with the custom app and git-based workflow.