Overview pages

No indication of custom content types on node/add

criticality: 
Moderate
Drupal7: 
Open
Task: 
This happened to: 

When on node/add there's no indication that you can create additional content types - some users get here first.

Solution: 
Add a link for users with 'administer content types' permissions.

Enable box is hard to find

criticality: 
Moderate
Drupal7: 
Open
Task: 
This happened to: 

When you are looking at selecting a new theme or finding out which one is enabled, it is hard to find out which one is selected.

All themes are blue

criticality: 
Critical
Drupal7: 
Fixed
Task: 
This happened to: 

All themes being blue makes it difficult to know what theme is enabled.

Save button is far from required fields

criticality: 
Moderate
Drupal7: 
Open
This happened to: 

It is easy to miss the save button because it is far from the active or required fields. An example is on the block admin page where the active/changed item cold be at the top and with many blocks the the save button is far away at the bottom.

User Does Not Save Blocks After Reordering

criticality: 
Moderate
Drupal7: 
Open
This happened to: 

User clicked "configure" after moving a block into a new region.

List of menu not formatted correctly

criticality: 
Critical
Drupal7: 
Fixed

The admin/build/menu page is formatted as a definition list which makes things look like help. These types of lists are almost always formatted to tables.

Region Indicators Deceptive

criticality: 
Critical
Drupal7: 
Open
This happened to: 

On admin/build/block, the user was confused as to what the *new* regions were. He thought that it would be nice if he could drag blocks to the region directly and add content from the region itself. This is not stating a solution, but merely stating what the user found.

Implications: 

Another point of confusion is the dotted lines. This is becoming a universal symbol for a droppable region.

No "empty text" Table Row For Empty Menus

criticality: 
Minor
Drupal7: 
Fixed

After creating a new menu, the "empty text" of "No menu items" is not in a table, it's simply plain text. Users do not ever read this far down the page since they think that it is part of the help text. No call to action to add a new menu item.

Implications: 

After creating a new menu, it's not clear how or why they need to add an item to the menu.

Users Expect Disable Blocks Be Displayed Separately or Differently

criticality: 
Moderate
Drupal7: 
Open
This happened to: 

When looking at admin/build/block, Users expected to see some kind of difference between the active region area and the list of disabled blocks.

Implications: 

User didn't see the disabled blocks section because it was so far down the page.

"Add New" Item Expected at the bottom of tables (menus/vocabularies/terms)

criticality: 
Minor
Drupal7: 
Open
This happened to: 

Users expect a "Add an item" row at the bottom of lists.

Syndicate content