[Design] Design mock-ups that preview PDF-imported text

[emilylordahl]

As a form author, I need to see and modify imported text (such as orphaned words or section numbers) that were ingested so that I can have control over the output of the PDF ingestion and reduce confusion.

After the PDF(s) have been uploaded, explore designing features that:

• cleans up poorly imported text (orphaned texted, phrases that got split into 2 questions but should read as one, etc.)
• provide a way for questions to be referenced by section number on the PDF itself so that authors and applicants can make connections across pages of the form.

@jimmoffet This issue was added as a result of the UX Concept testing in https://github.com/GSA-TTS/atj-platform/issues/116 . It needs further refinement and prioritization. Closely related to #250

UX considers this a major feature/issue due to it coming up with a majority of participants. Review details from the research in the research report.

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

[JennyRichards-Flexion]

9/6/24: In conversation with Jim, this item is MEDIUM priority.

[JennyRichards-Flexion]

Note: Research is needed to validate that this is in fact, needed.