Experience & Layout (Information Architecture + Flow)

[mikegianno]

I believe we need a section providing solutions or principles with proper reasoning on page layouts and flows.

Examples include:

• A dashboard page or hub page
• Flow when interacting with a things settings
• Validation/Confirmation flow structure (feedback mechanisms)

[codegaze]

Some notes on the validation/confirmation interactions (for reference)

• Modals
  • Main save/set action [Success/Error]
  • Set something in a subarea of the modal [Success/Error]
• Full page settings
  • Save a group of settings [Success/Error]
  • Set something in a subarea of these settings [Success/Error/Additional Info]
• Common
  • Info/warning action on a user interaction
  • Confirmation on an action. Modals might have a different approach
  • Waiting a response of an action (aka loading)
  • Single button actions [Loading/Success/Error]

We should keep in mind that our feedback apart from visual clues should have informative messages (aka what happens if the layout/space cannot support our messages)

[mikegianno]

Note regarding modals

We have cases of modals used for complex interactions that are NOT on the core purpose of the page (examples: Edit Languages, resource settings, video settings for a resource, requested languages, Edit translation memory group,...). Those cases are special because we cannot redirect to a different settings page as the information architecture does not compute.

For those cases I propose we examine a modal takeover to secure some more real estate for complex interactions.