Technical people tend to use github/gitlab or codeberg to make a plain list of things base on git version control, so changes are tracked. These lists are often introduced with the prefix awesome (e.g. awesome-hosting, awesome-lemmy, ...). Even when the community participates, curating these lists takes a lot of time.

[–] Humanius@lemmy.world 2 points 2 days ago* (last edited 2 days ago) (1 children)

I'm thinking of it more from a usability perspective. Im not sure if dozens of forked repositories would make it easy for the average person to find information

Having a single link to a repo with information for everyone could be very useful

Edit: Or alternatively a meta repository that links through to the individual national repositories?

[–] SrMono@feddit.org 1 points 2 days ago* (last edited 2 days ago)

Well, for the end user, if the markdown is simple well structured, it could be parsed to deployed to a website.

Or you could use any static page or documentation generator.