Closed abettermap closed 3 years ago
whatever the approach, it's important to remember that it (or something very similar) will be used for projects landing as well.
Ladino can be single-continent for our purposes, doing it now.
if we have any basic design revelations in the coming weeks before launch weekend, i can implement. otherwise i think it's looking decent for both lang and projects landings.
Langs landing
this is pretty much going to derail any potential progress on this today:
because there's also this:
and even more undesirably it all results in this (there is no orange Asia 10 in the cards):
it's the only one that spans two continents (isn't Izmir close enough to Europe? š ). kind of a bummer that a single language wrecked the entire approach, which was otherwise reasonably interesting:
i feel like i've spent days on this page without even settling on a layout, approach, or anything solid whatsoever. so some direction that doesn't have edge cases and take days to implement (and still be semi-unintuitive, e.g. Judeo-Spanish showing in two continents) would be appreciated.
even if we scrap the markers-per-location and just show an unlabeled marker (e.g. empty blue marker for Americas), it still doesn't seem to get around the Judeo-Spanish issue.
we could label the markers in the map with the actual location name, but that would get crowded immediately and there's no conflict detection since we're using MB markers. could switch from markers to hand-rolled geojson in lieu of tilesets, then apply the label/icon conflict detection like we do in nyc map, but none of that falls into the "doesn't take days to implement" category.
not really sure what to do. langs landing repeatedly ruins my life.