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

Align Feedback Hub with VADS #9261

Closed
1 task
brea11y opened this issue Aug 5, 2024 · 3 comments
Closed
1 task

Align Feedback Hub with VADS #9261

brea11y opened this issue Aug 5, 2024 · 3 comments
Assignees
Labels
API team mobile-platform work associated with building & maintaining the VA Mobile Platform ux

Comments

@brea11y
Copy link
Contributor

brea11y commented Aug 5, 2024

Using the VA Design System, create a ticket with recommendations for components that should replace existing elements on the Feedback Hub.

Recommended updates:

  • Use the header component that is used on the VADS website to replace the header on the Feedback Hub. Note: We may have to reach out to the VADS team for the component since this is not the official header component shown in VADS.
    • The header should look like this when updated:

new header for the feedback hub based on the header used on the VADS website

- Additional header updates: - [ ] Add sub-nav / dropdown navigation links below App Store and Play Store for a direct link to each store's "Rating History" - [ ] If it is decided that the analytics link should be featured in the header, it should have the external link icon after it (as seen in the screenshot above) - [ ] Remove the "VA Mobile Feedback Hub" heading on each page (since that will be moved to the header) and replace it with descriptive page titles for each page (i.e. Reddit Reviews, Apple App Store Reviews, etc.). Align all copy including headings [with VADS](https://design.va.gov/foundation/typography#headings) guidance. - [ ] All tables in the Feedback Hub site should be replaced with the [Responsive Stacked Table component](https://design.va.gov/components/table#examples---v1) from VADS. This will ensure that each table is accessible and wraps appropriates (without side-to-side / horizontal scrolling) - [ ] Use the simplified footer (vs. the official footer component) that is used on the [VADS](https://design.va.gov/) and [Platform](https://developer.va.gov/) websites. All of the possible links to include in the list below should have an external link icon to the right of the copy (like shown in the header example above). _Note: We may have to reach out to the VADS team about this component since it is not the **official** component shown in VADS._ - **Possible links to include in the footer:** - Analytics (if it is not included in the header) - [Monthly Review Summaries](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/products/va-mobile-app/reporting/App-Stores-Reviews) - [VA Mobile Documentation](https://department-of-veterans-affairs.github.io/va-mobile-app/docs/Intro) - The footer should look similar to the following screenshot (but with external link icon indicators added to each link):

Example of the Feedback Hub footer using the footer from the VADS website

- [ ] Replace all date range selectors with the [Date Input component](https://design.va.gov/components/form/date-input) - [ ] On the App and Play store pages, replace the select box with the [Select component](https://design.va.gov/components/form/select) - [ ] Replace the query input field(s) with the [Text input component](https://design.va.gov/components/form/text-input) - [ ] Replace the green "search" button with the [Default - Primary button component](https://design.va.gov/components/button/#default---primary) - [ ] Replace the blue "Download as .csv" button with the [Default - Primary button component](https://design.va.gov/components/button/#default---primary) - [ ] The "tabs" on the rating history pages, should be replaced with [Tabs component](https://design.va.gov/components/tabs) - [ ] Chat (I believe Chat GPT is going here) is cautioned against using unless it can be built with the VADS components (input fields, buttons, etc.) and can be built in a way that is fully accessible. - [ ] There are no components within VADS that can be used to replace the data within the "charts" tab and these will also not be accessible without additional content that is used to describe what is seen / displayed within the charts. At the minimum, the colors used within the charts should be updated to align with the[ VADS color palette](https://design.va.gov/foundation/color-palette) and the fonts should also be swapped out with [Source Sans Pro](https://design.va.gov/foundation/typography#fonts) (if they are not already). _If we choose to keep them, it is recommended that we have descriptive text and Brea can then identify colors to be used within them._ - [ ] The tables used within the "data" tab, should use the [Responsive Stacked Table component](https://design.va.gov/components/table#examples---v1) from VADS. This will ensure that each table is accessible and wraps appropriates (without side-to-side / horizontal scrolling).
@brea11y brea11y self-assigned this Aug 5, 2024
@brea11y brea11y added ux mobile-platform work associated with building & maintaining the VA Mobile Platform API team labels Aug 5, 2024
@StacyB2023
Copy link
Contributor

Thanks @brea11y Added to the Q3 Epic

@brea11y
Copy link
Contributor Author

brea11y commented Aug 13, 2024

Reviewed changes with Stacy and Jason on 8/13. Creating new tickets to implement the updates.

@brea11y brea11y closed this as completed Aug 13, 2024
@StacyB2023
Copy link
Contributor

StacyB2023 commented Aug 16, 2024

@brea11y I relinked this epic. Had it tagged to closed one. 9031 is the correct epic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API team mobile-platform work associated with building & maintaining the VA Mobile Platform ux
Projects
None yet
Development

No branches or pull requests

2 participants