[Eng] Update UI for Other components

[nichole-aquino]

Overview

Form builders can easily add/edit form Other components (attachment, rich text, form summary, package download)

Context

• Design ticket: [Design] Update UI for Other components #431
• Figma mockups
• USWDS components: text input and text-area, unstyled button, delete icon, list icon

Rename components:

• Rich text: Change to Page text
• Form summary: Change to Form title
• Attachment: No change
• Package download: Remove

On the build screen, for the attachment component:

• Relabel the question input field to ‘Question text’
• Widen the question input field
• Hide the configuration options for allowable file types and max number of files
• Add optional help text component; the field grows as needed (GH ticket #373)
• Add optional information box component 'Add supplementary information or instructions' (GH ticket #415)

On the build screen, for the page text (aka rich text) component:

• Remove the pre-filled text “Rich text…”

On the build screen, for the form title (aka form summary) component:

• Remove this component from the menu since the title/H1 is required for accessibility
• Remove the option to delete this component since this is not optional
• Remove the description input (the rich text component can be used instead)
• Relabel the input field to ‘Form title’
• Widen the input field

On the build screen, for the package download component:

• Remove this component from the menu since this is not optional and should be baked into the publishing experience

Acceptance Criteria

The changes should be made to the following question types:

• Attachment
  

• Page text (aka rich text)
  

• Title (aka form summary)
  

• Package download -- remove this as a component

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