that's interesting, we actually have a real difficulty here because our buyers are either marketers or developers. As the problem we are trying to solve is shared between them, both are looking out for solution and we are having a hard time positioning our marketing website's communication because of this. Also, thanks for sharing your impression on the video! When you say "if their site is not set up in just the right way to fit weweb", do you mean that it feels like the editor won't allow you to build custom layouts that fit with any design? Your feedback is most welcomed!

> When you say "if their site is not set up in just the right way to fit weweb", do you mean that it feels like the editor won't allow you to build custom layouts that fit with any design?

I find it a little hard to put this succinctly, but basically as a dev I get a little nervous seeing all the features in the UI. In my experience any complex editor like that has to be designed around a bunch of assumptions about what kind of site you’re editing, and almost every slightly complex real world site will have aspects that break those assumptions. It could something subtle, like confusion around terminology (imagine being a non-technical editor for a book binding website, and seeing terminology about “bindings”), or features that look like they should do something but for whatever reason don’t have any effect on the components in use. The more complex the editor is, the more likely that certain things will cause confusion when they meet the real world.

these are definitely real life example we experience every day. It is hard to draw the line between simplicity and customisability. For this our biggest inspiration is Figma. It's amazing to see non-designers drawing things in Figma without getting too many frustration together with designers doing complex and very precise designs & design systems without feeling limited.

Their interface feels easy to start with but can take you very far if you need customization and scalability.

We are far from what they achieve, but that's where we'd love the end up. :D

Have you explored the simplest option: separate "Weweb for devs" and "We web for marketers" landing pages, videos and homepage subsections/columns/tags?

On the video: first impression is that it's heavily Weweb-built template driven like another Squarespace (especially if I stop watching in the first couple of mins before the bit about design systems) whereas I assume from the description in this thread that the design elements marketers can add and what layouts/colours etc they can choose can be fully configured by devs (and the target audience is teams that want to do this) Ultimately I assume you plan on replacing the tutorial on the home page with a video that's snappier, more benefit-focused and more selective about UI examples anyway?

On the previous version of our website we actually dedicated the home page to marketers and had a link in the nav called "For Developers". The for developers page started to rank on google on some requests like "visual builder for react". We are revamping this page now and we'll add it again on the site.

Thanks for the feedback on the video, it's really useful. Makes me think that on the developer video we should probably start from a blank site and add a custom component in the editor right away.