rperlin-ela
commented
3 years ago Thin map above, content below
i think this is the way to go for mobile and tablet portrait at least:
Makes sense.
I could see just leaving the header (e.g. Languages) and I'm not sure that text below is a crucial, though I could certainly fill something in there. We can see how intuitive the whole thing feels as it comes together, but I'm easy
Side by side, 35% map 65% content
this won't work out on mobile, but desktop maybe.
Looks good
i could type all this out but i have like 150 questions, so let me know when you're free. i'm open (except tomorrow if Moderna statistics are accurate).
Sunday eve/good chunk of Monday is free
grid/list + map, or just map
do we show a grid/list at all for these super-custom landings, or just map? (i like the list)
I think list but keeping it more minimal on the main Langugages and Projects, more detail on instance pages. Your breakdown sounds like it would work.
abettermap
i can see a few scenarios for map-ness. i'm open to 1 layout (2 tops) depending on page (e.g Projects vs. Project) as it makes sense, but i think we agreed on (or at least what i had in mind) for maps was just one consistent layout. regardless of page/post type. that said, i think the question may be more of how to present the rest of the content next to or below it.
Options for map
i'm sure there are MANY and we'll evolve this as we go through the usual iterations, but let's get the pretend-visualization-imagination goggles on since i can't code all these for full-on demos in the short time frame! just going for map vs. not map general layoutness here so try to see past style details a bit.
Thin map above, content below
i think this is the way to go for mobile and tablet portrait at least:
Side by side, 35% map 65% content
this won't work out on mobile, but desktop maybe.
Zoom
i could type all this out but i have like 150 questions, so let me know when you're free. i'm open (except tomorrow if Moderna statistics are accurate).
basically questions will come down to priorities and decisions again:
grid/list + map, or just map
do we show a grid/list at all for these super-custom landings, or just map? (i like the list)
if list, what to include?
taking Languages page for example, as a user i'd like to see in list:
orrr, if your priorities are only to show that level of detail on an instance page, e.g. /projects/jewish or /languages/neo-aramaic, then as a grid perhaps :
obvi want to see more than 1-2 langs or projects on first view, so really gotta crank down what we show in custom landings like this.
Interaction
SOW only covers some basic interaction at best (click point, get popup w/link to next level down). but all the info/content available (way beyond SOWness) we/I have added capabilities for, will trigger new questions, ideas, suggestions, etc. This ain't my first language map UI-rodeo, i know how this works. 😉 BUT given the confines of reality and time, gotta narrow it down to the basics. it's a website, not web app, so keep that in the back of your head when making some of these decisions.
i could think of another dozen things to say/ask, so let's save for Zoom. whatever we come up with for /languages landing should be reusable enough (at least for the overall map-vs-content layout) for the other 3 map scenarios: projects list, project instance, and lang instance.