Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Design messages for empty Submit Snapshot tables #2009

Open
9 tasks
thetanmancan opened this issue Jan 1, 2025 · 0 comments
Open
9 tasks

Design messages for empty Submit Snapshot tables #2009

thetanmancan opened this issue Jan 1, 2025 · 0 comments
Labels
Dependency Issues that cannot be worked on until another issue is closed level: easy p-feature: Submit Snapshot priority: MUST HAVE role: ui/ux design size: 0.5pt Can be done in 2-3 hours or less
Milestone

Comments

@thetanmancan
Copy link
Member

thetanmancan commented Jan 1, 2025

Dependency

Overview

Please design messages that replace the tables on the Submit Snapshot page when no snapshots are listed.

Details

Currently on the Submit Snapshot page, when there are no snapshots on the page, the page shows the name and column headers for each table even though there is no content in the table cells, making the page look awkward.

A Submit Snapshot page devoid of snapshots on the current Dev site

Image

This issue calls for the design of error messages in two scenarios.

  1. If there is no data in any of the tables, one message should replace all table titles and tables. The message should inform the user of what a snapshot is and how to create and submit one.
  2. If there is data in at least one of the tables, then those tables should present as normal, but any unpopulated tables should have a message appear below the table title in place of the table itself.

Action Items

  • Wait for the text content for these messages to be approved by stakeholders via Draft language for Submit Snapshot page popovers and non content #2010 .
  • Design UI mockups of designs for the two scenarios listed above.
  • Review with the design team. Update designs if needed based on feedback.
  • Review with the product, development, and research teams. Update designs if needed based on feedback.
  • Add a slide to the the staging deck.
  • After the slide has been approved by production, move it to the stakeholder presentation deck for the next stakeholder meeting.
  • Review the design at the stakeholder meeting. Update designs if needed based on feedback.
  • After getting stakeholder approval, create a design handoff for the development team.

Resources/Instructions

@thetanmancan thetanmancan moved this to New Issue Approval in P: TDM: project board Jan 1, 2025
@ExperimentsInHonesty ExperimentsInHonesty added this to the 10 - Launch milestone Jan 2, 2025
@ExperimentsInHonesty ExperimentsInHonesty added Dependency Issues that cannot be worked on until another issue is closed and removed ready for prioritization Issues that are ready to be prioritized by product labels Jan 2, 2025
@ExperimentsInHonesty ExperimentsInHonesty moved this from New Issue Approval to Ice Box in P: TDM: project board Jan 2, 2025
@thetanmancan thetanmancan changed the title Design a message for an empty Submit Snapshot page Design messages for empty Submit Snapshot tables Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Dependency Issues that cannot be worked on until another issue is closed level: easy p-feature: Submit Snapshot priority: MUST HAVE role: ui/ux design size: 0.5pt Can be done in 2-3 hours or less
Projects
Status: Ice Box
Development

No branches or pull requests

2 participants