We're currently hard-coding the menu path of a module's configuration page to a specific, often subjective, parent category page.
The problem is best described by webchick in #34:
Currently, your only option is to hook_menu_alter() the path from admin/config/development/XXX to admin/config/butterfly/XXX. But when you do that, suddenly all of your help text/drupal_set_message() links are broken, the tests (which are all pointing to the default path) no longer pass, etc.
I'm sorry. I predicted this fact already, but no one wanted to listen.
I'm trying to port http://drupal.org/project/compact_forms to D7 as part of my personal D7 porting effort.
There is no suitable category.
A suitable category would may be "User interface".
But that does not exist.
My little module has, as of now, 609 users.
It doesn't make sense for a module like that to define a new "category".
The "expected" result is to have 4,000+ Drupal modules to define their own "categories".
Core is not able to pre-define the categories.
We already know that. And we really should have learned from admin/build/modules.
I mentioned exactly that before.
The thinking is 2D.
The reality is 3D.