[raphael-gold]

great question! From my perspective, stackbit is made for large corporates willing to add a no-code layer above an existing Jamstack site. This provides additional customization option to marketers compared to a headless CMS only.

Our approach is different because you would build your site from scratch using weweb, which gives you much more customization possibilities on the front-end than a stackbit, but it would not be possible to add weweb "on-top" of an existing react or vue website.

[winkelvoss]

huh, that's totally off. Stackbit enables visual editing from a Jamstack site built from scratch too. Their visual editor seems like it's better. And you could do a site from scratch, with a theme or even just add it to your existing site. Neat product. But don't see any value add to the ecosystem in it.

[raphael-gold]

To start with Stackbit I believe you need to start with one of their themes and stackbit would be added on top of it. While you can start from a blank page in our tool. In their editor, the customization possibilities are limited in no-code compared to a comprehensive no-code website builder.

[winkelvoss]

Nope. lol Can start from a blank slate, one of their 500+ themes, a starter repo of your own or from your existing website. Stackbit's honestly pretty dope.

And they have a full online code editor in their visual editor. Nothing no-code about it.

It looks to me like you guys are just TinaCMS for Vue instead of React.

Not trying to be a dick. Just trying to share the truth.

TinaCMS import { InlineForm, InlineText } from 'react-tinacms-inline' return ( <InlineForm form={form}> <h1> <InlineText name="title" /> </h1> </InlineForm> )

weweb <wwLayout path="cards" direction="row" class="cards"> <template v-slot="{ item }"> <wwLayoutItem class="card"> <wwObject v-bind="item"> </wwLayoutItem> </template> </wwLayout>

[raphael-gold]

Agreed, they are building a really great product.

We are (at this stage) still very different though: with weweb, you can build full layouts with various elements and manage the CSS of every single element directly from a GUI in a no-code editor, just like in a Webflow.

In Stackbit's no-code editor, you can change the position of ready-made sections and change some of the props of these sections (text, links, etc.). You cannot however build a section from scratch 100% in no-code like you would do in a Webflow (or weweb) using grids/flexboxes, drag & dropping elements into these containers, updating all the CSS parameters visually, etc. You'd have to do it in the code in Stackbit today.

Same goes with Tina CMS. They do not offer a comprehensive no-code editor like weweb or Webflow and we are very different for that reason.

The cool thing that Tina and Stackbit manage very well (and that we don't), is the ability to add a in-line visual editor in an existing react project to change the content and some of the properties visually, but it is limited to these properties.

What we do on the contrary is offering a comprehensive no-code site builder where marketers would build 90% of a custom website and developers would add custom coded vue components in the drag & drop editor for the extra 10% that cannot be built in no-code (+ make some of the properties of these components editable from the GUI).

Hope this makes sense?