Minor changes in Task & sign up menu ...

[MarcosMoreu]

• Everytime the user clicks on “Search” (or a default search), the previously loaded map layers remain visible. Is this on purpose or a bug? I think that when a new layer/polygon is added, all previously loaded layers should be removed from the map?

• In the “Create new task” menu:

1. “Add Logo” not working, but not needed actually >> remove button (for now).
2. Just 1 checkbox “I want the WhatsApp Maps of this task to be open data. For more information click here” (unchecked by default)
3. The code generated is always the same unless log out/in.
4. We don’t really need the box with the long codes etc. Let’s keep it simple:
   The task has been created. Use this code to upload and search WhatsApp Maps
   ABC123

• Home screen before log in/sign up:

1. Burger should be visible and interactive
2. Globe, search bar and buttons should be visible but not interactive and with some transparency
3. Sign up restrictions in Kapta Web >> Add the code restriction as discussed. As a heading for the input code box, add “Don’t have a code? Please click here to join the waitlist” >> We can create a form or use tools like cognito forms for that. What do you think? https://www.cognitoforms.com/
4. If Kapta Web is opened in a mobile device >> I believe the (disabled) globe, buttons etc will not look good, so perhaps we can remove them and add: 1) A message “Kapta mobile version is under development” (or whatever). 2) A button “WhatsApp Maps Assistant” that open a conversation with our Kapa WhatsApp

• Buttons’ text

1. “Search WhatsApp Maps” (remove ground data & capital M)
2. “Task WhatsApp Mappers” (instead of TASKS only)

• Reduce width of the Search bar - something like ChatGPT/Gemini width?
• Add License in the repository, also in the infrastructure one, so it's ready for when we open source it next week. I've updated the README, but please update the developers' section in it.
• In the map attributes OpenStreetMap Contributors (add Contributors)

[acholyn]

Sign up restrictions in Kapta Web >> Add the code restriction as discussed. As a heading for the input code box, add “Don’t have a code? Please click here to join the waitlist” >> We can create a form or use tools like cognito forms for that. What do you think? https://www.cognitoforms.com/

We also discovered that the invite system via cognito is actually quite easy and straightforward - it will send a temporary password to the email provided and then when the user logs in with the temporary password, they're supposed to set a new password.
With the code one, the easiest thing to do, I think, would be to use waitlist (I couldn't find one of these on cognito forms). Then you'd either import to cognito and send them invites that way, or email them a generic code which we've set. I think the personalised one through cognito is safer but the generic code has less AWS reliance.
From a technical standpoint, I think the flow with a temp pw is more reusable since we want to also add the forgot password button

[acholyn]

“Task WhatsApp Mappers” (instead of TASKS only)

This button will be much longer than the current one - do you want it to be one line or wrapped? and should it still be inline with the search bar or should it be slightly above so they don't overlap?

[MarcosMoreu]

“Task WhatsApp Mappers” (instead of TASKS only)

This button will be much longer than the current one - do you want it to be one line or wrapped? and should it still be inline with the search bar or should it be slightly above so they don't overlap?

Yeah. I think we have to options: 1) keep the search bar centered but make it narrower so the button is inline and in one line; 2) I was thinking that perhaps we could put the button below the search bar, following the same concept of Google's "I'm feeling lucky". What do think?

[acholyn]

I've noticed a bug when viewing items from search results so will address that with these

[acholyn]

I think that when a new layer/polygon is added, all previously loaded layers should be removed from the map?

I've cleaned it up and reworked the map so this should be the case except when we do search results, just because when there are search results, all relevant polygons are plotted on the map for better exploration (some tasks in the results might not have data yet so they can't be plotted). If you want me to get rid of that functionality, I can, and people will just have to click through like with tasks. Let me know what you think