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

Daily Docket | Move back to hearing days up to top #4771

Closed
annienguyenUSDS opened this issue Mar 5, 2018 · 5 comments
Closed

Daily Docket | Move back to hearing days up to top #4771

annienguyenUSDS opened this issue Mar 5, 2018 · 5 comments

Comments

@annienguyenUSDS
Copy link

annienguyenUSDS commented Mar 5, 2018

To be consistent with navigation in Queue, move "< Back to Your Hearing Days" link from bottom of page to top left in gray space above hearing worksheet

@annienguyenUSDS
option 1:
back

@annienguyenUSDS
Copy link
Author

@lakohl this would be good to align navigation and make sure where they landed.

@annienguyenUSDS
Copy link
Author

Messaged Queue, Phillip is working on Queue navigation and will get back to us.

@lakohl
Copy link
Contributor

lakohl commented May 8, 2018

@Chingujo just checking if Queue has created any new navigation patterns yet?

@Chingujo
Copy link

Chingujo commented May 8, 2018

We discussed a broader navigation conversation across applications yesterday =D! We are doing some explorations on how best to navigate between apps like reader and hearings for this sprint.

We were planning to present to the broader design team once we finished (@mkhandekar @sneha-pai) for awareness.

At a more granular level we made the following in app decisions for embedded flows (i.e. for the attorney checkouts):

  • No bread crumbs as they were creating complex navigations and logic.
  • A cancel, back, and continue buttons as seen below

footer_buttons

@annienguyenUSDS
Copy link
Author

@sneha-pai is working on latest navigation between products.

@ghost ghost removed the Backlog label Nov 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants