Zarino Zappia

Further thoughts from @dracos, spurred by us looking at this mockup of the page with lots of the buttons removed:  * Should metadata go _below_ the problem description? *...

Here’s where the mockups got to on this:  * Removed map controls – dragging and scrolling still work to pan and zoom * `#sub_map_links` replaced with a new element...

If we do change the styling of updates, I’ll need to think how to handle the "Still open, via questionnaire, [date]" style of updates, that don’t have any body text.

> Perhaps if it's been sent to the council the same day, it could be "Reported to FOO [in the blah] [today | on date]". If not yet sent, could...

> Could expand map be just the icon in the corner of the map? That would match e.g. youtube or google maps streetview map. Yeah, could be! That would just...

Note – it looks like FMS now allows "non public" reports (in only some areas, or for only staff users, maybe? can’t tell) so the button text will _also_ need...

> Thinking about what it would do on mobile too, not sure balloon would work there - probably a button right under the map I guess seems most obvious, even...

> Just on the mobile view (design by screenshot :) ), perhaps could have back to all reports be left half, new report here button be right half of same...

Quick update on this. Now that #2195 and #2198 have been merged, the "Report a problem" button in the nav bar is a bit more useful for actually reporting problems...

iOS strips EXIF data from images before allowing them to be uploaded to a website – so there’s no way we’ll be able to extract geo-location from photos uploaded _to...