WeWeb - update on what we are working on at the moment

[Broberto]

@Raphael

That said, there’s a high likelihood it would require significant time and technical refactoring, in which case we’d postpone it.

You don’t probably need refactoring or SSR to solve most of the points related to dynamic titles, structured metadata etc. Do you?

[jayjay13]

what would it mean to postpone it? earliest next year or even later? i think ssr would be worth the effort as it would enable many more use cases and therefore a bigger user base..

[Raphael]

hey @jayjay13 unfortunately we don’t know yet, as we’re still in the process of qualifying it and understanding the scope of work it would involve. We expect to have more clarity by the end of this month, and I’ll make sure to update the community here as soon as we do.

[dsturnerville]

Did not see an update on any of these. Did any of these make to production?

@Raphael

4. 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

[jose]

Hi Raphael,

For the icon colors, please make sure we can still customize them through code. I’m concerned that forcing all fill and stroke values to "currentColor" removes the ability to style individual parts of the SVG.

For example, I have an SVG with two fill paths—one uses "currentColor", and the other uses fill="var(--color2)" so I can apply a secondary color via CSS. If everything is forced to use the same color, that flexibility is lost.

Unless there’s a way to keep each path’s original color definition as the priority, applying "currentColor" globally does more harm than good.

Thanks!

[Raphael]

hey @dsturnerville not yet unfortunately, we are holding them back because we want to finalize the documentation before deploying them to production. Breadcrumb, file upload and calendar should go live tomorrow. Timeline on Monday or Tuesday next week.
Chat and AI Chat next week, Gantt and Currency not sure yet exactly, we had to re-prioritize other tickets, but I’ll have a better visibility next week. Sorry for the delay, we are almost there!

[Raphael]

@jose

For the icon colors, please make sure we can still customize them through code. I’m concerned that forcing all fill and stroke values to "currentColor" removes the ability to style individual parts of the SVG.

Thanks Jose, it shouldn’t be a problem!

[Raphael]

Following up on this, Breadcrumb is live, see the documentation here: Breadcrumb | WeWeb Documentation

File upload, Timeline and Calendar are ready and will be deployed to production on Monday afternoon CET.

[CedricFR73]

Hi @Raphael

Congratulations for this.
In " Datagrid improvements", is there a plan to implement a trigger that allows selecting a row by clicking anywhere on it, instead of using the checkboxes? For example, clicking anywhere on the row would trigger an event.

Using a simple onClick doesn’t work as it doesn’t capture event.row.

Thanks

[julian]

+1 for this one. My workaround is setting all cells to custom and then add the onClick even to the custom cell div-container.

[dsturnerville]

This is what we are doing as well.

[nick]

+1 for a more user friendly dynamic metadata experience. I’m not sure I’ll be able to continue my project without it.

[andreas.schaefer]

is there an ETA on the GANTT Component? I’m actively looking for a GANTT component currently and before I buy another Component I’d like to see if the built-in might be able to handle my use case

[Fishfrom96]

I’m trying to implement this but one major thing that seems to be missing is multilingual support. Is this planned?

[Yaj]

Hey Raphael

Do you know if the issue with Modals becoming components and having overlay issues is going to be fixed in this next update? It’s been going on for months since the new modals came in and seems to be a common issue many people are facing. I think you can rig some stuff up so it doesn’t happen but I shouldn’t have to rig up weird workarounds.

I understand the team has a lot going on but this is a new thing implemented and broken on release and hasn’t been fixed in months now and I’m just struggling to comprehend how an obvious glaring issue can go on for so long.

New Dialog as component problem

This is still an issue and its a huge pain. Why do i have to delete these elements from the DOM to be able to edit properly? So you can edit the overlay to be pretty much invisible but you can’t even remove their overlay you just have to make it redundant. You could easily set up something so it only does it in the editor but its incredibly fucking stupid I have to do anything like that at all.

[Fishfrom96]

@Raphael I think it’s time for a bi-weekly update again right?

[ralphlasry]

Ya I keep coming to visit the forum to check if there’s an update

[Raphael]

Hi everyone! Apologies for the delay, after being off last week, I wanted to ensure I had better clarity on a few items before sending out the bi-weekly update:

1. Improving the quality of the AI-generated logic: The new agentic AI structure, now powered by Sonnet 3.7, is live on our staging. We’re currently running extensive tests to improve output quality and the results so far are impressive. I’ll be sharing a video update next week to give you a closer look at the progress. As for the release, it’s difficult to pin down an exact date, but we’re aiming for the week of the 19th of May.

2. Datagrid improvements:

• Trigger on row deselected - is in production.
• Fix Datagrid causing infinite loops in some cases - in production.
• Custom colors for the tick box - is QA approved, will be live next week.
• Add Range selection border color property and checkbox selected background color property - is QA approved, will be live next week.
• Expose filters & sort and add init filter and sort properties - is QA approved, will be live next week.
• Add a property lang in the settings tab to allow translations - is in QA, will be live next week or the one after.
• Back-end filter - While this feature would be useful, we decided to move it to the backlog for now since it’s not highly requested and would require a lot of development time.
• Fix when you filter the column and use the select all option, it ignores your filter and selects the entire collection - following further analysis, we determined that this cannot be done because of a limitation in AG Grid.

4. Here is the progress on our long list of advanced components:

• Timeline - is in production, link to the documentation
• Breadcrumb - is in production, link to the documentation
• Improved file upload - is in production, link to the documentation
• Improved calendar - is in production, link to the documentation
• Having the Kanban working well with AI - is in production
• Having the Carousel / Image Slider working well with AI - is in production
• Gantt - currently in QA, it’s expected to be in production toward the end of May.
• Chat - currently in QA, it’s expected to be in production toward mid-May.
• AI chat - currently in QA, it’s expected to be in production toward mid-May.
• Currency input - currently in QA, it’s expected to be in production toward the end of May.
• OTP Input - under development, it’s expected to be in production toward the end of May.
• Stepper - under development, it’s expected to be in production toward the end of May.
• Tree View - moved to backlog for now since the demand is not very high.

5. Detaching modals from pages and making them accessible at project level: the new system for modals / popups has been in QA for the past week. We’re currently focused on stabilizing it, improving it and making it compatible with the new AI. It will be released to production together with the updated AI, so hopefully the week of May 19th.

6. New organization of global workflows and edge functions + revamp of the plugins panel: we’ve been pushing this a bit further. In addition to revamping the UX/UI around global workflows and plugin management, we also added the ability to create backend workflows with Supabase, similar to how frontend workflows are built. The feature is really exciting, it will allow the creation of Supabase edge functions in no-code, which is a major improvement. The whole feature went back into development so we could integrate this new functionality. It should be in staging by the end of next week, and we’re aiming to push it to production toward the end of May.

7. Vite setup to reduce the build time: the feature is now in staging, being tested. It will be released to production together with the updated AI, so hopefully the week of May 19th.

8. Icons improvements: we had to postpone these improvements to focus on the Datagrid improvements and the performance issues reported over the past two weeks (most of which we have now fixed).

9. We have the following fixes planned for the roadmap next week:

• Fix the input’s On enter event bug.
• Fix the issue where changing the language on a dynamic page causes the parameter to become undefined.
• Fix the fact that the name is not saved when saving a template into the library.
• Fix the calendar issue binding events
• Fix tooltips in the add menu (they are not displaying right now)
• Add a Help button to the top bar of the editor so users can easily access chat support

10. Other topics:

• SSR: We are still exploring the technical feasibility of implementing SSR with WeWeb. We should be able to share whether we’ll be able to prioritize it this year in the next bi-weekly report.
• Support & ticketing system: we’re in the process of overhauling our ticketing system and chat support through Intercom, making it much easier for users to track their ticket status. On top of that, we’ve made strong progress in hiring a new Customer Care Engineer, someone will be joining our team in early May! We’ll share more with the community in the next bi-weekly update.
• Branching: the product team has completed the first version of the qualification, and it is now with the developers for review. We’ll share an initial estimate of the time required to build this feature in the next bi-weekly update.

---

As always, feel free to comment and add your feedback in this thread in case you feel we missed something important!

[Raphael]

hey @Yaj, yes it should be fixed with the new modals system

[Raphael]

Thanks for reporting it, I’ll check with the team to see what we can do.