[openstreetmap/openstreetmap-website] Communities page (#3256)

[Adam Hoyle]

Hi @tomhughes,

Thanks for the speedy reply!

> You might want to start by reviewing previous discussion about adding new top level links there - given how limited that space is you're going to need to make a very good case.

We're aware of Andy's recommendations here - https://github.com/openstreetmap/openstreetmap-website/issues/3041#issuecomment-780445950 - are there any other specific conversations we should be aware of?

> Examples of how it works in English aren't very useful - try it with something like German where the translations are much longer ;-)

Haha yeah good point - we'll take a look 🚀 

> How would a data driven solution work? I understand you have a geocoded index, but what would you use as the key? The current map position? For a map that's not longer displayed once you switch to the community tab? The user's home location?

The key reason for a data driven solution is to support the ideal of a single source of truth and therefore reduce ongoing maintenance effort.

There are currently 17 Local Chapters, so there isn't a need to have a particularly fancy or clever listing of them - showing an alphabetical list would be sufficient (certainly for an initial release). Saying that tho - are there other areas on the site where data is displayed differently depending on location and does that then set a precedent for expected behaviour for a communities page?

Are there other examples of external data such as osm-community-index being loaded into the site (so that we can follow a similar pattern)? This data does not change very often, so there would be no need to refresh it more often than every 24 hours.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/3256#issuecomment-879740803
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20210714/b339c879/attachment.htm>