You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the PDF(s) have been uploaded, design a view that puts the PDF and edit experience side by side where the PDF view is the primary place where actions take place. The visual of the PDF is familiar and makes the experience approachable. Consider the users are likely to move their attention to the PDF view right away. See exploration.
Other PDF viewer ideations were completed by the team in a design jam session and are available to explore on Mural.
Overview
As a _, I would like _, so that I can _.
Context
Optional: Any reference material or thoughts we may need for later reference, or assumptions of prior or future work that's out of scope for this story.
[ ]
Acceptance Criteria
Required outcomes of the story
[ ]
Research Questions
Optional: Any initial questions for research
Tasks
Research, design, and engineering work needed to complete the story.
[ ]
Definition of done
The "definition of done" ensures our quality standards are met with each bit of user-facing behavior we add. Everything that can be done incrementally should be done incrementally, while the context and details are fresh. If it’s inefficient or “hard” to do so, the team should figure out why and add OPEX/DEVEX backlog items to make it easier and more efficient.
Behavior
Acceptance criteria met
Implementation matches design decisions
Documentation
ADRs (/documents/adr folder)
Relevant README.md(s)
Code quality
Code refactored for clarity and no design/technical debt
Adhere to separation of concerns; code is not tightly coupled, especially to 3rd party dependencies; dependency rule followed
Code is reviewed by team member
Code quality checks passed
Security and privacy
Automated security and privacy gates passed
Testing tasks completed
Automated tests pass
Unit test coverage of our code >= 90%
Build and deploy
Build process updated
API(s) are versioned
Feature toggles created and/or deleted. Document the feature toggle
Source code is merged to the main branch
Decisions
Optional: Any decisions we've made while working on this story
The text was updated successfully, but these errors were encountered:
JennyRichards-Flexion
changed the title
As a form author, I need to work off a PDF that is visible and actionable so that I can start from a place of familiarity.
[design] Research to validate side-by-side PDF edit experience design concept
Oct 15, 2024
JennyRichards-Flexion
changed the title
[design] Research to validate side-by-side PDF edit experience design concept
[Design] Research to validate side-by-side PDF edit experience design concept
Oct 15, 2024
After the PDF(s) have been uploaded, design a view that puts the PDF and edit experience side by side where the PDF view is the primary place where actions take place. The visual of the PDF is familiar and makes the experience approachable. Consider the users are likely to move their attention to the PDF view right away. See exploration.
Other PDF viewer ideations were completed by the team in a design jam session and are available to explore on Mural.
Overview
As a _, I would like _, so that I can _.
Context
Optional: Any reference material or thoughts we may need for later reference, or assumptions of prior or future work that's out of scope for this story.
Acceptance Criteria
Required outcomes of the story
Research Questions
Tasks
Research, design, and engineering work needed to complete the story.
Definition of done
The "definition of done" ensures our quality standards are met with each bit of user-facing behavior we add. Everything that can be done incrementally should be done incrementally, while the context and details are fresh. If it’s inefficient or “hard” to do so, the team should figure out why and add OPEX/DEVEX backlog items to make it easier and more efficient.
/documents/adr
folder)README.md
(s)Decisions
The text was updated successfully, but these errors were encountered: