Improve page text functionality

[nichole-aquino]

Overview

As a form builder, I would like be able to apply advanced rich text formatting, so that I can create clear form content.

Context

Currently, a builder can format text with the 'page text' component, which includes the following options: H2, H3, bold, italic, bulleted and numbered lists. Additionally, copying/pasting into this component strips all styling from the original source of content (e.g. headers, paragraph breaks). For example:

In stakeholder feedback sessions, participants wanted to be able to:

• apply links in the page text component
• retain text formatting when copying/pasting into the page text component (e.g. links, headings, paragraph breaks)

Other feedback

• One participant wanted to be able style the H1 (especially if the form title is very long)
• One participant wanted to be able to include links in the hint fields

Acceptance Criteria

Required outcomes of the story

• Links included in rich text editor
• Ability to retain text formatting when copying/pasting from another content source

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