I’m rebuilding my live site in WeWeb. I use Claude to design the frontend first, then convert its HTML to a WeWeb-compatible JSON layout tree (element types, names, CSS properties, children) via a custom HTML-to-WeWeb mapping. It’s not perfect 1:1, but it speeds up development a lot.
This structured approach seems to use fewer tokens too—Claude gives a clear format for Wewebs AI to follow with no guesswork.
WeWeb team: Are there docs listing all prebuilt elements with their styling/settings options? It would help Claude map CSS more accurately to WeWeb’s system.
Hey Chase! The UI looks pretty cool
Did you use Claude for Chrome to build this?
Also, thanks for calling this out. I’ve shared the suggestion internally about having a more detailed reference for available styling and settings options.
No, i use Claude directly. I set up a project to store the necessary example docs and pages it designs then just reference those as I have it build each page. The only real issue is the cost of AI tokens on Weweb. Many builders offer free AI assistance, like Xano and I think Bubble as well. I’m happy to pay for it, but compare the usage I get from Claude for $17/month to the usage I get in Weweb for $60/month - it’s not even close to comparable.
They do which is why I had to upgrade t0 $17/month. But I have yet to hit the limit on this tier and even if I did, it resets in a few hours - not a month.
