> It would be lovely to make those (sub)sections dynamically > expandable. I believe it would make the eggs list easier to > understand and search on for newbies like me.
The only thing I have to add to this suggestion is /not/ to use a strictly hierarchical classification, allowing for a single egg to reside under multiple categories. (Like: Role/Program, Development/Library and Protocol/HTTP, if the egg in question happens to provide both an HTTP client library, and one or more example applications built on top of it.) See also [1].
For a viable software classification, check, e. g., debtags [2] (though it certainly isn't the only one available.)