Is there a chance your documentation will see an uplift too. While the overall quality is very high, for new users like myself I would like to see greater breadth to what’s available.
Could you also increase the academy content too please?
1 Like
Could you kindly work on the SEO for dynamic page? The cloudflare method doesn’t work anymore. Online stores and blogs posts are all in need of that feature!
Also, having voice input would be great especially for the interaction with the AI chatbot.
1 Like
The CloudFlare method doesn’t work anymore? When was that breaking change announced? And there is no workaround? If there is no way to do dynamic SEO, we’re going to have to abandon what we’ve built over the last year because our use case (event platform SaaS where users can create conference, webinar, etc event pages and a lot more) is impossible to generate any revenue without strong SEO capabilities.
1 Like
Could you please provide more info as to why you think the Cloudflare method is not working? We will take a look, thanks!
Please check out this thread:
https://community.weweb.io/t/dynamic-metadata-through-cloudflare-dont-appear/13099/15
cloudflare worker only work on www. but www. need to be point to weweb server. Any idea how to fix it? The problem has been around for some time in the forum.
the Supabase issue has been taken care of, it’s in QA, if the QA goes well it will be in prod on Thursday
1 Like
I love this so much.
1 Like
the fix has been deployed, let us know if it works
3 Likes
@Raphael Super exciting!
When can we expect gantt, timeline and tree view?
I will need them and was thinking about trying tk code them myself. I just discovered weweb 10 days ago, though. Learning curve was not steep at all, but creating custom components is still to be learned haha
Hey! Glad to read that 
Gantt and Timeline are already developed and currently in QA, if all goes well they will be in prod next week. Tree view will be dev next week, so it will hopefully be in production the week after.
4 Likes
Hello everyone! As promised, here is the bi-weekly update:
-
Improving the quality of the AI-generated logic: we’ve revamped our internal agentic structure to make it more efficient and are now focused on getting Sonnet 3.7 to work well within the WeWeb context. We’ve made a lot of progress over the past 2 weeks, and the results are promising. We’re continuing to double down on this and hope to roll out a completely new and improved AI experience in about 3 weeks.
-
Improving the quality of the AI-generated UI: the update is live. It’s a small improvement, but a pretty meaningful one. Sonnet 3.7 will bring a much bigger leap forward.
-
Datagrid improvements: all previously mentioned improvements are now live. We have a few more in the works:
- Fix when you filter the column and use the select all option, it ignores your filter and selects the entire collection - should be in prod this week or the next
- Custom colors for the tick box - should be in prod in 2 to 3 weeks
- Trigger on row deselected - should be in prod in 2 to 3 weeks
- Back-end filter - should be in prod in 2 to 3 weeks
- We progressed on our long list of advanced components:
- Skeleton Loader - in production
- Currency input - in QA, should be live this week
- A new, improved calendar - in QA, should be live this week
- A new, improved file upload - in QA, should be live this week
- A new, improved Kanban - in QA, should be live this week
- Carousel / Image Slider - in QA, should be live this week
- Breadcrumbs - in QA, should be live this week or the next
- Gantt - in QA, should be live this week or the next
- Timeline - in QA, should be live this week or the next
- Chat - in QA, should be live this week or the next
- AI chat - in QA, should be live this week or the next
- Stepper - under development, should be live in 2/3 weeks
- Tree View - under development, should be live in 2/3 weeks
- OTP Input - under development, should be live in 2/3 weeks
- Comments & Threads - we decided to postpone this one for now as the use case was not as obvious as we thought.
-
Detaching modals from pages and making them accessible at project level: it still under development and should be in QA this week and in production in 2/3 weeks.
-
New organization of global workflows and edge functions + revamp of the plugins panel: same as the improved modals, this is under development and should be in QA this week, so in production in 2/3 weeks.
-
Vite setup to reduce the build time: this was longer than expected and more complex, but we did not give up! This will be in QA in 2 weeks and should be in production in 3 to 4 weeks.
-
Icons improvements: we hadn’t originally planned on making so many updates, but managed to sneak them into the roadmap, as you’ve seen. And we have got a few more coming:
- On upload, force the
fillandstrokeproperties to"currentColor"(to inherit the color in the SVG) so that when choosing a color in the editor for an SVG you uploaded it will always work - should be in prod in 2 to 3 weeks - Ability to copy/paste a full configuration of an element to another element to facilitate the migration to new icons for existing projects. This will also be useful as a “quality of life improvement” feature - should be in prod in 2 to 3 weeks.
- Improve the handling of full icon ZIP uploads (folders, ability to delete entire folders, etc.) - should be in prod in 3 to 4 weeks.
The product team is still mostly focused on what we shared two weeks ago, these are major features that take time to properly scope and qualify:
- Environment management with Supabase.
- Branching feature.
- Figma integration.
As always, feel free to comment and add your feedback in this thread in case you feel we missed something important!
23 Likes
Feedback on your bi-weekly updates: love it!!!
1 Like
Thank you 
glad it’s useful!
2 Likes
Those are amazing changes! We’ve already made our own modal component for exactly the reasons given, where we can also pass data in the modal. So I’m exited to see what you guys cooked up!
1 Like
Hi Rapheal,
Any plans for SEO handling of dynamic pages? Currently unsupported by WeWeb:
- canonical URL’s (
my biggest issue/required to index pages) - dynamic titles
- dynamic social metadata / opengraph
- dynamic structured data
- dynamic sitemaps
I tried hard to setup cloudflare workers to leverage the html rewriter as a solution to handling the above, but it’s not possible as we can’t enable “Proxied” at the DNS level to allow Cloudflare to do this, as it must be set to “DNS Only” to point to your server for the hosting.
(I’m using Supabase)
1 Like
What about the Supabase Environment Management? I’m currently building out an HR App in a seperate project that will hold all the employee data and manage users and handle auth for the whole app. But my main app is on different project. I know I could just connect to one with the plugin and one with rest API but it would be much nicer to have two instances of the plugin to comfortably manage both from weweb
1 Like
I second this
Hey @what.gift, yes and no: as we finalize the implementation of Vite, we’ll take a closer look to assess whether supporting SSR is feasible. That said, there’s a high likelihood it would require significant time and technical refactoring, in which case we’d postpone it. Please note that this is the most probable outcome, but we’ll keep the community informed as soon as we know more - likely towards the end of April.
If SSR support eventually makes it onto the roadmap, we’ll definitely re-prioritize everything related to SEO. For now, unfortunately, it’s not a focus, as we’re currently concentrating on SPA use cases.
hey @andreas.schaefer this is currently being qualified by the product team, the devs will work on it this month, ETA to be confirmed once we are done with the qualification - I’ll keep everyone posted on this.