- Too long and unwieldy.
- Important information and controls are hidden behind fieldsets.
- Drafts are lost when clicking links, even help links.
- It is not obvious that permissions control what the content creator sees.
We discussed improve the admin's ability to design the form and improve Drupal's use of progressive disclosure. Ideas included:
- Provide option to hide fields next to required checkbox on fields admin screen.
- Decide which fields to hide using usage statistics.
- Make a 1 to n priority system so content creators can choose their level of fields to show.
- Allow content creators to access hidden fields when needed.
We also discussed improving Drupal's split summary at cursor feature.
- Find the best words and be consistent- summary, teaser, excerpt, read more, etc.
- Integrate with wysiwyg editors.
- Look at how Joomla, Wordpress and others handle this common interface.
Finally, we discussed vertical tabs. We saw in Baltimore that these are a potential improvement, but not there yet.
- Summaries have recently been added under tab titles, they should be user tested.
- What is a good semantic term to use in code?
- UI standards are needed.
- bertboerland and ximo will write standards for and continue to improve vertical tabs.
- ximo, Jan K, and I will think about and mock up new split summary at cursor.
- Jan K will mock up layouts for multiple taxonomies, which quickly use a lot of vertical space.
- al.ex will suggest wording changes.
Roundup meeting slides
Notes after our roundup meeting
- The "prioritysystem" for the fields and fieldsets adds another big layer of complexity
- So only the predefined contenttypes will benefit from our suggestions
we're shifting the problem from one side to another
- We need to make suggestions for the contenttype creation form also since that is were we are shifting the burden to