Messaging System: Categories, nuances, accompanying styles

[ninavizz]

How should user-facing content be structured across categories of Client messages to users, and what will each of those types of messages look like?

Needs to fulfill this Issue:

• Workshop w/ team a complete inventory of messaging to date, and anticipated messaging needs
• Categorize/taxonimize
• Spec how each category of message should display; timing, content, styling
• What messages are outliers in need of one-off treatment, if any?
  • Run updater asap for Template installs
  • ???

[ninavizz]

This is now a sub-task within #31 and #18

[ninavizz]

Additional requirements:

• How do contextual messages look? What will the text of those messages be—any icons? Cross-referencing Workstation Client Content Inventory + Design #17 with that.
• What should rudimentary tasks be required to meet Sprint 23 requirements?

[ninavizz]

Closing, as much of what this was created to address has been done (sync messaging, error bar stuff), and other bits will just get done later as extended features get developed.

TBD task from discussion with Erik however, is the need to document existing patterns and standards throughout the client in a behavioral/visual styleguide.