Layout of records
All records should be layed out in the same order
- Start with enough information to identify the record we are looking at
- If there is a high level way of splitting the record, this should come next (e.g. tabs for the contact screen, or concertina for event screen)
- Actions specific to each tab should flow directly beneath that tab using the 80/20 rule. Try and keep this to one line maximum
- default first selected tab might inlcude repition of actions also available in other tabs (e.g. record event attendance)
- Collapsed context specific help should also be available here
- Information relevant to the record, or the section of the record that we are looking at. (e.g fields, related records)
- Actions repeated at the bottom
- Help expanded at the bottom
Chunking complex records
For records that are more complex, chunking into managable sections is a good idea.
Headings / chunking should be visible and clearly seperated from fields.
Relation between edit and view screens for records
These should match each other in terms of layout and design as much as possisble, but shuld also clearly indicate whether a user is in view or edit mode.