> On Feb 17, 2026, at 7:31 AM, Shane Curcuru <[email protected]> wrote:
> 
> Jarek Potiuk wrote on 1/18/26 08:06:
>>> Which means we need to figure out more intuitive nav on the site. Again.
>> :)
>> That's a given :). The moment we can't improve something in what we do, is
>> the moment we stop reinventing ourselves and fall into stagnation.
> ...snip...
> 
> It feels like the homepage needs some to lead different audiences to the 
> topics they might be interested in - using the language they'll expect for 
> those topics.  And then perhaps simple list item landing pages per audience 
> that help refine what topics they want to read.
> 
> For example: the way any regular contributor will look for topics is 
> different than a complete newcomer.  Similarly, the way a technical 
> participant is looking for information is different than someone interested 
> in community or events.  How can we write simple yet helpful mini-welcome 
> pages for the kinds of readers that come to the website?
> 

That’s very much what we tired to do when we rearranged the menus into 
audiences rather than topics, and wrote landing pages for each of those 
audiences. Patches eagerly welcomed.


> Brainstorming entry questions to frame these mini-welcomes:
> 
> - I'd like to contribute code (someone just needing technical info or lists 
> of projects)
> - I'm looking for a community to join (someone interested in how our 
> communities actually work)
> - Where can my company participate around the ASF?
> - I'm a committer: what else does the ASF do outside my project?
> 
> Each of these mini-welcomes would be a short list of links to key topics they 
> might be interested in, plus perhaps a one sentence explainer to frame the 
> topics.
> 
> I guess the metaphor is: instead of having the home page images be just a 
> list of topics, have some be a list of common *audiences* we have.
> 
> This idea would sit alongside the existing nav bar and tags system, which are 
> important for the audiences who use those first.
> 
> Also: if tags are implemented across the site, why aren't they given a more 
> featured UI spot?

Primarily because we have failed to attract a designer and/or information 
architect to help us with this work. Know anyone?


— 
Rich Bowen
[email protected]




Reply via email to