Ok, to supplement the discussion thread here (http://groups.drupal.org/node/19831) let's have this wiki page as the consolidated home for items we, as a group, determine appropriate to add to the issue queue. I expect that each of these items will end up needing its own thread in time, but here's a place to start.
Please be trustworthy about keeping things in the correct vetted/new lists.
New
- Ability to define menus in .info file
- Core outputs little or no markup or CSS (or vice versa, we had some disagreement)
- Extend Coder module to check for CSS namespaces based on the Drupal Manual of Style that D4D will eventually create
- Renaming of "Navigation" menu and separation from User menu: http://drupal.org/node/273137 and http://drupal.org/node/382890
- Let's bring all classnames into the theme layer. This will give those of us who know the context of each tag give it a semantic name that matches that context. Then we'll have cleaner html that is smaller and can be read by humans. The existing class/idnames can still exist, but their implementation will be in the hands of the themer. Base themes for beginner/intermediate themers can use them by default, but advanced themers will have the power they need to make their markup kick ass.
- **Ability to set classnames from the admin interface.** This could be a form element when creating a block, content type, node, menu, etc that let's users with the correct permissions override or add to the default classnames for the bit they're creating.
- **Better default classnames** I'd like to see a hyphenated version of the block, form, node, etc title be the first suggested classname. That could really help add some automatic semantic relevance to the classes, for the masses.
- **Let's not overlook menu items!** This would really help us target specific menu items in context. it would be sooo much better to target a menu item classed as "get-involved", instead of something like "
Vetted