‹ Home
Exported

GEMS

https://gems.umn.edu/ https://gems.dev.umn.edu/
Robyn, Project Manager at Matogen DigitalIan Parsons, Head Chef at Matogen DigitalLaura Hurley, Designer, UX and Engagement Specialist at Matogen DigitalDavid Mundell, Developer at Matogen DigitalXoliswa Shandu, Matogen DigitalJohnny Sheridan, Sales Boss at Matogen DigitalPatience Kudyatasa, QA Specialist
From the list: Website updates

✔ Put Phil's feedback on the XD file

Robyn added this on
Completed by Laura H.
Assigned to
Laura Hurley, Designer, UX and Engagement Specialist at Matogen Digital Laura H.
Due on
Notes
Dear Laura,
 
Kevin and I used the Landcover API as a basis for redesigning the web entry for our website. See here for our suggestion to remake the page. Note in particular:
  1. We picked up on your suggestion to include a table at the end of each accordion entry summarizing the key at-a-glance features of each API product.
  2. We suggest removing the current GEMS APIs at a glance table and instead using a ‘more details’ button to take users to an indexed listing of all the API product specifications, formatted just like you had before:
 
API Product: lcmap-1.2
 
  1. We also made some edits to the LandCover API product details description.
  2. Using all of this we’ve laid out as an example, we’d suggest you remake each of the other API specifications, noting that Biotic Risk Geography, Climate, Elevation, and Hydro also have multiple API products each.

Comments & Events

Laura Hurley, Designer, UX and Engagement Specialist at Matogen Digital Laura Hurley, Designer, UX and Engagement Specialist
Robyn, Project Manager at Matogen Digital Robyn Ian Parsons, Head Chef at Matogen Digital Ian I've created a mockup for the changes Phil and Kevin have suggested on the API's pages, please have a look and let me know if there's anything I've missed and if all is good, I'll share it with the team. Thanks!
https://xd.adobe.com/view/5397c206-dce6-44ba-b8e3-1385258fbccb-06c4/grid
Notified 2 people
Robyn, Project Manager at Matogen Digital Robyn, Project Manager
Laura Hurley, Designer, UX and Engagement Specialist at Matogen Digital Laura  I think this is in line with what Phil and Kevin asked for - seems right to me!
Laura Hurley, Designer, UX and Engagement Specialist at Matogen Digital 🔥Lekker!
Notified 2 people
Laura Hurley, Designer, UX and Engagement Specialist at Matogen Digital Laura Hurley, Designer, UX and Engagement Specialist
Thanks Robyn, Project Manager at Matogen Digital Robyn ! 
Robyn, Project Manager at Matogen Digital ❤️
Notified 2 people
Ian Parsons, Head Chef at Matogen Digital Ian Parsons, Head Chef
Laura Hurley, Designer, UX and Engagement Specialist at Matogen Digital Laura do you think it's a good idea to take people to another page to view more detail about each API product? I'm not sure how we can solve it otherwise. Options: 
  • suggest that this level of info is not suited to the marketing website, and people can read more on the documentation
  • keep it like it is, on a separate page
Alternatively, we should put each API on its own page, where we can have detailed information. We're trying to stuff a lot of info into a small space, and the fact that we're pushing some content onto a separate page makes me realise we actually just need a separate page for each API :) 
Notified 2 people
Robyn, Project Manager at Matogen Digital Robyn, Project Manager
Ian Parsons, Head Chef at Matogen Digital Ian  good suggestion but perhaps we need a second option to show this - I believe Lau's design is in line with what the team asked for so I think we should do another option - what do you think? 
Notified 2 people
Laura Hurley, Designer, UX and Engagement Specialist at Matogen Digital Laura Hurley, Designer, UX and Engagement Specialist
Hey Ian Parsons, Head Chef at Matogen Digital Ian , the Data specification at a glance table gives some of the details for each product and those who want to get into the details can click through to this additional page, which could easily be swapped out for a link to the documentation rather (is that on GitHub?) :)

I hear what you are saying though. The page will be very long if every accordion is expanded and there are lots of tables nested in accordions.. I think they said 4 or 5 more API will need tables, but this will likely grow in the future.

I think a dedicated page for each API is not a bad idea. But as Robyn, Project Manager at Matogen Digital Robyn  said, let's show them what I've done according to their request, plus an option to show separate pages.
Notified 2 people
Ian Parsons, Head Chef at Matogen Digital Ian Parsons, Head Chef
Sounds good to me!
Laura Hurley, Designer, UX and Engagement Specialist at Matogen Digital 🔥 On it!
Notified 2 people
Laura Hurley, Designer, UX and Engagement Specialist at Matogen Digital Laura Hurley, Designer, UX and Engagement Specialist
Please just refresh option 2, forgot to remove the one button
Notified 2 people
Robyn, Project Manager at Matogen Digital Robyn, Project Manager
Laura Hurley, Designer, UX and Engagement Specialist at Matogen Digital Laura I like both options - I think you can share it - don't remember your exact feedback this morning in our chat Ian Parsons, Head Chef at Matogen Digital Ian  so please confirm you are happy :) 
Notified 2 people
Ian Parsons, Head Chef at Matogen Digital Ian Parsons, Head Chef
Yup, let's get their feedback. 
Notified 2 people
Laura Hurley, Designer, UX and Engagement Specialist at Matogen Digital Laura Hurley, Designer, UX and Engagement Specialist
Sorry I am still busy applying the feedback Ian suggested this morning. Will share with them as soon as that's complete
Notified 2 people
Robyn rescheduled this to-do
Was
Now
Notified 1 person
Laura Hurley, Designer, UX and Engagement Specialist at Matogen Digital
Laura Hurley completed this to-do.