IA1.1: Discovery: Avatars, titles & menus

[nadonomy]

The intent of these changes is to re-arrange elements to create a clearer hierarchy of global, per space, and per room actions.

• Part of a larger project to improve our IA.
• Figma
• Merging to develop to test there, rapidly iterate for production.

Tasks

• Move user avatar to Space panel. Update to the latest designs. Use existing context menu on click.
• Remove user avatar from message composer. Update to the latest designs. Temporarily move 'Set status' to user context menu for users who have it labs flagged.
• Add room list header for 'Home' or 'Space Name' to room list
• Move 'Search' to new location in designs. With Explore in lieu of 'History' until we get to 1.3.
• Add existing Space context menus to room list header
• Add a new [+] menu next to room list header.
  Home: ???
  Space: Start new chat + room. Invite to Space.
• Update existing [+] interactions
  People: Start new chat. Invite to Space.
  Rooms: Create new room. Add existing room. Explore rooms.
• Sanity check collapsed states after making the above changes

[t3chguy]

• Need design for where the pending room join spinner will live

• Need design for where the DND labs feature will live

• Need design for where the Custom Status labs feature will live

[niquewoodhouse]

Need design for where the Custom Status labs feature will live

Would custom status set for each and every space you're in?

Need design for where the DND labs feature will live

Does this mute everything - Home and all spaces? At the moment it appears on Home, but not on other Spaces

[t3chguy]

Would custom status set for each and every space you're in?

Custom status as is currently implemented is global, we don't need to give it much care beyond exposing it SOMEWHERE

Does this mute everything - Home and all spaces? At the moment it appears on Home, but not on other Spaces

I believe so, but its a labs flag I know very little about.

[turt2live]

DND can probably just get quietly lost in the migration to greener pastures. It's very much a developer-friendly feature, which means developers can use the Settings Explorer or JS console to trigger it.

For custom status, we might be able to just lose it as a feature - it's backed by a bad implementation and doesn't fit the desired UX at all. Will check internally.