I’m sorry, but whoever came up with the placement of this button clearly didn’t think it through. When you’re working on updates and frequently switching to staging mode to check things in the browser, it’s way too easy to accidentally miss the staging button — and boom, the entire project gets published. This design is poorly thought out and borderline negligent.
1 Like
I think it asks you it you want to promote, doesn’t it?
Unfortunately not. After clicking the promote button, the site is immediately published to the project domain without any confirmation prompt or field to double-check the action.
Good feedback for @luka
I hope the team will address this. The editor has gone through a lot of design changes recently – most of them were great, but some felt unnecessary. For example, the placement and design of the preview button changed several times without clear benefit.
1 Like
Yeah, I actually agree with the preview button lmao. My brain was so mashed up after the first change that I was getting so confused each time I wanted to go to preview that I just simply started using the shortcuts.. The cognitive load was crazy
2 Likes
Yes, I really like Weweb, but there are some things done that dont seem well thought through and that makes you somewhat nervous as I am getting closer to a production release…
1 Like
Yes, I completely agree with you! But quite often the shortcut doesn’t work for me (Mac / Chrome browser)…
1 Like
I simply think WeWeb 3.0, i.e. the integration of AI, takes too much capacity away from more important topics that we need as developers. Personally, I hardly use the AI feature because most of the time it doesn’t work anyway and gives me back errors or the results are simply disillusioning. I also no longer want to create a bug report ticket every time.
Things like Datagrid are then released lovelessly and completely unfinished… I think the WeWeb community would like to see a clearer direction here again.
I did use the formula Copilot back when it was working and was giving good results, now ..
It sometimes feels useless to open tickets since they go unanswered for months anyway 
2 Likes
Yes, the formula co-pilot was just nice in helping with what was essential. I understand the buzz words for many businesses to roll out AI but its disappointing because it can make many more unauthorised changes in many places. I veer away from AI at the moment.
Weweb team does need to focus on making the core great and not getting distracted with too many changes and half baked releases.
1 Like
so sad!
The Forumlar Copilot was so great! Now when I want to edit forms with AI I get no results or always have the feeling that the AI tries to interpret way too much what I don’t need… I only use chat gpt and try my luck here
1 Like
I agree. I can’t trust the Ai results and when I have used it, it’s rewritten (broke) entire action workflows and missed key details. It’s half baked. I’ll stick to using Ai in a seperate window for when I use it.
I wish they would focus on some core missing features like… SEO for dynamic pages. I don’t understand how there isn’t more need for something so crucial. I can’t be the only one despereatly needing this for a ecommerce/marketplace type website?
Ai is all the buzz, but having tried Replit to actually build a proper App, it just can’t. Context windows/token limits are the hard ceiling at the moment which isn’t going away anytime soon. WeWeb shouldn’t try to compete with building entry level websites/Apps which is where Ai is currently at in “vibe coding”, and stick to it’s core of building powerful, granular and controlled fully fledged dynamic web applications - which is what it’s really designed for!
But, if it can’t offer proper SEO for dynamic page support…
Omg I agree wish they brought back the old formula copilot. It was just easier to use hahahaha
We can have both they serve difference functions
1 Like