I think this is a very smart addition to the site; however, I don't think all the ALCs have enough going on to justify a full page at this point. Since there are only a baker's dozen, a short listing for each would fit on a single page; then, for ones like Taipei, there could be a link for more information. And as other ALCs become more active, their entry could follow the Taipei pattern.
Andrew Wetmore Assistant VP, Marketing and Publicity, The ASF <https://apache.org> Editor-Writer, Infra team, The ASF Editor, moosehousepress.com On Mon, Oct 12, 2026 at 11:58 AM Rich Bowen <[email protected]> wrote: > FYI, I demoed my proposed website addition to Gav and some others at > Community Over Code, and I’ve also requested Privacy approve loading > OpenStreetMap (OSM) maps, here — > https://lists.apache.org/thread.html/gvkwmqg84pzyrbqdyfjznr0ocr6yj4d2 > > The draft implementation is here: > https://github.com/apache/comdev-site/tree/rbowen-alc in the /source/alc > directory. > > See also attached screenshot. > > > > > > > > On Oct 12, 2026, at 12:01 PM, Rich Bowen <[email protected]> wrote: > > > > Hi, folks (and especially Gav who has stepped up to get some of the ALC > > process updated): > > > > As part of the ongoing effort to tidy up the ComDev website's structure > > and navigation, I'd like to propose adding a new top-level /alc/ section > > for the Apache Local Community program. This augments the existing > > Wiki content - which I still need to review, because I suspect that some > > of it is outdated or inaccurate. > > > > Right now the only ALC presence on community.apache.org is a single > > navbar link under "Join the Conversation" that points off to the cwiki > > page. There's no home for ALC on the site itself, no list of chapters, > > and no map. Given that ALC is a ComDev program, I think it deserves a > > proper section. > > > > == What I'm proposing == > > > > A new /alc/ section with roughly this shape: > > > > /alc/ Landing page: what ALC is, how to find a chapter > > near you, how to start one. Includes an > > interactive map of chapters. > > /alc/chapters/ One short page per chapter (city, organizers, > > meetup/contact link, recent activity), and then a > link > > to the wiki content. > > /alc/start-a-chapter The process for establishing a new chapter, and > > the ground rules. > > /alc/organizers Practical help for running a chapter: finding > > speakers (linked to our existing speaker and > > slide resources), event ideas, ALC resources. > > > > == The map == > > > > I’d like to do a fancy javascripty thing that has a map that updates as > we > > add chapters. > > > > Each chapter page would carry a little front-matter block in its Markdown > > (city, country, lat/long, status, organizers). The site build generates > > the map data from those files automatically, so the map stays in sync and > > adding a chapter is just a single Markdown file plus a pull request — no > > separate data source to maintain. > > > > == How it connects to the rest of the site == > > > > - The Events dropdown gets a "Local groups" entry pointing at /alc/. > > - The homepage gets a "Find a local community near you" card. > > - Chapters can reuse our speaker list and sample-presentation pages. > > - Event write-ups from chapters can be ordinary blog posts tagged "alc". > > > > == Relationship to the cwiki == > > > > The ALC program documentation currently lives on the cwiki. The intent > > isn't to fork or replace it — the authoritative program rules (the apply > > and dissolve processes, ALC Resources, Slack invite) can keep living > > there and be linked from /alc/. What the website adds is the public, > > newcomer-facing front door: the "what is this / is there one near me / > > how do I start one" layer, plus the map, which the wiki can't really do. > > > > I wanted to float the structure here first in case there are chapters, > policies, > > or links I'm missing, and to make sure the split between "website front > door” > > and "cwiki source of truth” sits right with everyone. > > > > Thoughts welcome. > > > > Rich > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected]
