A test attempt at moving some of the Product team feature definition and prioritisation into GitHub. The aim is to create more detailed feature definitions, provide more transparent prioritisation and more effective "linking" of product design to development tickets (currently in the xPub project board).
"As an author submitting my research I would like a "preview" of my submission before I submit so I can review it before sending to feel confident I have sufficiently filled it in."
We're still getting feedback about wanting to "review" files even though we have added the "preview" button. Many users go back to the start to double-check their submission for submitting.
Could show submission in tabbed "details" view - access via the wizard somehow
Or typical "check over everything" view at the end... seems to be the expected pattern based on other journals setting user expectation... but is this more work than is necessary?
Decision needed
[ ] Is this necessary? Or is it a request based on lack of confidence resulting from some other failures in the wizard? If the form is clear and easy to navigate is a preview necessary?
[ ] Tabbed interface or "single page"? Preview "as Editors see it" or "single page for quick browsing?"
[ ] How is it accessed? Clear final step in the stepper? Or optional link on final step?
Early mockup
Preview link at end of wizard
Preview based on tab interface?
This is perhaps more useful once HTML manuscript view is available
User need
"As an author submitting my research I would like a "preview" of my submission before I submit so I can review it before sending to feel confident I have sufficiently filled it in."
We're still getting feedback about wanting to "review" files even though we have added the "preview" button. Many users go back to the start to double-check their submission for submitting.
Could show submission in tabbed "details" view - access via the wizard somehow
Or typical "check over everything" view at the end... seems to be the expected pattern based on other journals setting user expectation... but is this more work than is necessary?
Decision needed
[ ] Is this necessary? Or is it a request based on lack of confidence resulting from some other failures in the wizard? If the form is clear and easy to navigate is a preview necessary?
[ ] Tabbed interface or "single page"? Preview "as Editors see it" or "single page for quick browsing?"
[ ] How is it accessed? Clear final step in the stepper? Or optional link on final step?
Early mockup
Preview link at end of wizard
Preview based on tab interface?
This is perhaps more useful once HTML manuscript view is available