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

Revise Guidance on Write Plan page #495

Closed
stephaniesimms opened this issue Jul 5, 2017 · 10 comments
Closed

Revise Guidance on Write Plan page #495

stephaniesimms opened this issue Jul 5, 2017 · 10 comments

Comments

@stephaniesimms
Copy link

stephaniesimms commented Jul 5, 2017

UX wireframes @JEK-III : http://h90c3m.axshare.com/#g=1&p=write_plan

screen shot 2017-12-12 at 7 36 36 pm

@stephaniesimms stephaniesimms added this to the Write plan pages milestone Jul 5, 2017
@stephaniesimms stephaniesimms changed the title Write Plan 2: Revise Guidance on Write Plan page Revise Guidance on Write Plan page Jul 5, 2017
@briri
Copy link
Contributor

briri commented Jul 7, 2017

This one needs to be worked on with close coordination with #494

Instead of having separate guidance/comments sections next to each answer we want a single tabbed box that is contextualized based on where the user is currently working.

  • The tabbed box should stay visible as the user scrolls up and down.
  • All guidance sections should be collapsed on page load or a new section is expanded
  • When a user expands a section, the following should happen:
    • The Guidance reloads. All of the themed guidance for all of the questions within that section should appear (separated by org as shown in the wireframe)
    • All accordion guidance should be collapsed
    • The comments tab should be cleared and any old question specific annotations should be removed from the guidance tab
    • A message should appear on the comments tab letting the user know that they should click on an answer to show comments - @JEK-III, @stephaniesimms, @sjDCC if this one is true what should the message say? (this is when a user has expanded a section on the page but has not yet clicked on a specific question)
  • When the user clicks on a specific question/answer the following should happen:
    • The comments tab should reload
    • Any old question specific annotations should be removed from the guidance tab
    • Question specific annotations should be loaded and appended to the bottom of the appropriate guidance (e.g. DMPOnline suggested answer would be added at the bottom of the DMPOnline guidance)
    • If a guidance area was expanded and is still available to the user, it should remain expanded
    • The current tab guidance/comments should remain active (e.g. if the user had the comments tab open and clicked on a different answer then the comments tab should remain open)

@vyruss
Copy link
Contributor

vyruss commented Jul 11, 2017

I'm a bit concerned with changing the layout so drastically as it's not clear how we can display "annotations" (i.e. guidance and/or example answers for specific questions) aligned alongside the question

@xsrust
Copy link
Contributor

xsrust commented Jul 11, 2017

I'm confused as to why themed guidance would be displayed on a per-section basis instead of a per-question one. Templates rarely have multiple questions with the same theme in a section. Furthermore, unless we display the theme next to the question, it will be difficult for the user to pair guidance to questions.

The comments tab only re-loading once the user has selected an answer box may also confuse users and require extra clicks. I also find it difficult to understand how this layout would work for a keyboard-only user.

@briri
Copy link
Contributor

briri commented Jul 11, 2017

@JEK-III did we decide on how to display things like question specific guidance and example answers? If I remember correctly, we were going to add them as sections to each of the org tabs if I remember correctly.
Not sure of all the use cases for displaying themed guidance per section. @sjDCC and @stephaniesimms should be able to clarify.

@stephaniesimms
Copy link
Author

we discussed all points above during UX mtg on 12 Jul and @JEK-III is revising the wireframes accordingly. we can review them together on Tues and/or Wed calls next week.

@vyruss
Copy link
Contributor

vyruss commented Jul 14, 2017

I'm not too sure about the <h3> size for guidance titles - it might be a bit too big and it also produces an indentation effect on my browser

image

@briri
Copy link
Contributor

briri commented Oct 19, 2017

Convert the guidance portion of the write plan page to look like the one in the wireframe. Use a slider to switch between guidance and comments and create guidance tabs by organisation.

@xsrust
Copy link
Contributor

xsrust commented Dec 12, 2017

Just to clarify, The desired work here is to continue having one guidance/notes portion per question, but refactoring the UI to be similar to the wireframe linked in the first comment?

@stephaniesimms
Copy link
Author

yes @xsrust - we can confirm this on call today

@stephaniesimms
Copy link
Author

discussed on call and changes confirmed. closing this issue and replacing it w/a clean one #944

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