Feedback needed! More extensive workload information in the docs 🚀

Hey everyone,

We’re revamping how we present workload in articles, along with other technical details. Our goal? To make workload information in specific contexts accessible, without bogging down the article with technical jargon.

:page_facing_up: Here’s a sneak peek from the User Manual article on Workflows (these changes are not yet public). It outlines where WU consumption occurs within workflows, supported by annotated tooltips for deeper insights (hover over underlined words for more info).

Your thoughts? :speech_balloon:

4 Likes

Solid idea. Would be great if those also provide links to articles that might dive deeper than the tooltip could. For example, the ‘kind of event’ it is, I’d imagine the tooltip might not have enough space to break down all the different kinds of events and the associated WU cost, so if a link could navigate a user to a detailed list of such things as well as some practical examples, that would help alleviate confusion.

Thanks for the great feedback @boston85719!

Yes, that’s the idea. The tooltip provides short, to-the-point information, and links to other relevant content. You can see an example of that here:

Was it something like this you had in mind?

1 Like

Yes, that looks great.

Are those linked articles going to have the detailed breakdowns of WU costs for the different client/server side processing and some practical examples? I’d imagine the practical examples that could be helpful may be screen shots of editor with series of actions that point out each action and if it is charged or not and if so how much, which may then provided an estimated total cost of WUs for the series of actions.

That particular article is live here already. I’d say it contains a fairly expansive overview of what happens client-side/server-side in Bubble, but whether it highlights all aspects of it is hard to say tbh, and requries feedback and ongoing polishing.

I guess the best answer to your question is that the “blurbs” we’re working on now will link to content that’s already live. In other words, it won’t be directly linked to what we mention in the blurb, but will hopefully still answer questions in more generalized way.

1 Like