You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a meta ticket for the Web Map development (UX elements will change so this is for the purpose of backend development mainly):
See attached file for a rough UX on the functionality.
We would like to get a clear idea of how this data will be available. Is this individual queries or are these Panels Json blobs that are filled by cron job based routines that keep them up to date and/or are they triggered on any change that effects each tree/sponsor/wallet/planter/organisation entry. Comments and discussion welcome on this. (mentioned orgs planters and individuals are randomly chosen)
The below UX drafts show the switch between the different impact panel views.
The text was updated successfully, but these errors were encountered:
For anyone looking at this, please share your questions and/or suggestions. I'll provide an end-to-end walkthrough prototype soon so that we can all see what the end goal is. Thanks! :)
FYI: The term Forest is not going to be used here. Maybe "digital Forest"
Davidezrajay
changed the title
Web Map 2.0: Build out different impact panel views see attached UX draft
Web Map 2.0: Design impact panel views
Mar 2, 2020
This is a meta ticket for the Web Map development (UX elements will change so this is for the purpose of backend development mainly):
See attached file for a rough UX on the functionality.
We would like to get a clear idea of how this data will be available. Is this individual queries or are these Panels Json blobs that are filled by cron job based routines that keep them up to date and/or are they triggered on any change that effects each tree/sponsor/wallet/planter/organisation entry. Comments and discussion welcome on this. (mentioned orgs planters and individuals are randomly chosen)
The below UX drafts show the switch between the different impact panel views.
The text was updated successfully, but these errors were encountered: