[Tree Details - UX] Information Architecture

[ri0nardo]

Need to add a user flow for devs to understand how the tree details work.

Miro Board:
https://miro.com/app/board/uXjVPj0Fujg=/

Existing Flow:

[ri0nardo]

Adding the revised tree details information architecture with new features / additions. This new flow includes the "tree preview" for mobile which will be a great ux addition for mobile users who are browsing around the map. Will also include potential fun additions including confetti for adopting / liking a tree, confirmation screens for maintenance and removing a tree, and uploading photos from the tree details sidebar.

@zoobot any thoughts on this mapping? I think this is good enough to get by with all the features we are considering implementing.

[ri0nardo]

Added modifying maintenance performed and delete maintenance session.

[zoobot]

Maintenance buttons should be loaded for the day so they are "clicked" if previous maintenance was done that day. A user should be able to unclick them and it will remove from history. Looks like this is currently broken though.
Not sure which PR broke it but I started to fix it here: #435

[ri0nardo]

additions / revisions to the information architecture. Now the maintenance will lead to options of what kind of maintenance needs to occur. (called tree care on the map).

We now have

• Maintenance (tree care)
• City Request
• Tree Removal
• Modification of Information
• Something Else (Report)

All central in one place. @zoobot what do you think?