Incorporate Tilman's suggestions into Webtool

[Tilmon]

Dear @maurolepore,

responding to this comment , I reviewed the Webtool Document and the actual tool.

Based on the review, please do the following: Webtool Document

1. In the webtool document, I made suggestions in track changes. Can you please incorporate the changes?

Webtool - general feedback sorted by tab

2. Welcoming Page: Space between paragraphs seems larger for “Welcome to tilt’s Online Portal” card than for “What you’ll Find on This Website”. Is that true? If yes, can you please align the spacing?
3. Dataset: When I logged in 20min ago, the data didn't load, I didn't even see the buffer "big data...". Now it worked again. Any idea what's the reason behind that?
4. Dictionary: 2nd card was also empty when I logged in 20min ago, now it shows the actual dictionary. I guess this issue is somewhat related to the dataset not showing up (point 4). Just flagging here in case you have an idea what the reason might be.
5. Method: This is just a heads up: We also need to upload a 2nd video once it's ready. Not sure yet when it will be ready, but ideally at some point next week. Just FYI.

[maurolepore]

WIP

• [x] 1. See

• 221

• 222

• 223

• 224

• 225

• 226

• [x] 2. Not sure the content under those two headers are comparable. The text under "Welcome to tilt's Online Portal" indeed has multiple paragraphs so the idea of "separation between paragraphs" does apply. But the text under "What You'll Find in This Website" is a single bullet-list (think just one paragraph) so the concept of "separation between paragraphs" doesn't seem to apply here. For consistent spacing between text-elements we could consider the following: a. Turn each paragraph under into a bullet. b. Turn each bullet into a paragraph.

• [x] 3. and 4. It seems like the app wasn't alive. One scenario when I can imagine this happening is this: 1) You login to the app, 2) land in the Welcome page and spend a lot of time reading all its details (e.g. reviewing it to provide feedback). 3) The cloud platform detects inactivity and kills the cloud computer that serves the app. 4) By the time you move to the tab "Data" or "Dictionary" the underlying computer is dead to it can't run the processes required to serve those datasets to you. We can run some interactive tests to explore this issue. If we detect this is a likely problem we can do a few things: a) Investigate if we can increase the time before the app is killed for inactivity, b) show some kind of message to the user warning of inactivity and eventual kill. In our interactive test we should explore if refreshing the browser brings the app back to life (or logs out the user).

• [x] 5. See https://github.com/2DegreesInvesting/tiltWebTool/issues/227

RE 2.

[maurolepore]

RE 2. I tested the app and confirm that after timeout the app looks gray, indicating the user that needs refresh. Refreshing results in logout. Loging back in brings the app back to life.

The timeout now is 300s (5'). We can change the settings easily.

• https://github.com/2DegreesInvesting/tiltWebTool/issues/229

[maurolepore]

Having explained 3-4, I take that as understood. I'll close but feel free to open a dedicated issue if we need some change.

[Tilmon]

Hi @maurolepore , sorry for late response!

RE 1, 2 and 5: Great!

RE 3 & 4: thanks for explaining and already extending the time out period. I just tested it again and for some reason, the data don't load when logging in. I also re-freshed, logged in again but still no data are automatically previewed (see screenshot). When I click on the "Go!" button, the data load. But they don't show up without hitting the "Go!" button. Is that how it's supposed to be? Dicitionairy works fine now, so extending the time out period seems to have worked there!

[maurolepore]

@Tilmon

When I click on the "Go!" button, the data load. But they don't show up without hitting the "Go!" button. Is that how it's supposed to be?

Yes, that's how it's supposed to be. That avoids expensive computations before the user is done making all the selections they want. It gives the user more control and saves computation and costs.

But I do see your point. It would be nice to start with the app showing some data rather than an empty page.

This behavior has been like this for a while. If you still need to test the app it would be best to do it ASAP so we can prioritize those changes during sprint planning tomorrow.

[Tilmon]

Hi @maurolepore OK I think then it's good :) I think I got confused because I was used to seeing data immediately from the past. But if a user looks at this the first time, I'm sure they'll figure out to click "Go!" ;)