Form Summary component minimum viable implementation

[jimmoffet]

Overview

Should this component end up anywhere other than the top of the first screen of the form? Can there ever be more than one? Should it show up in the Questions dropdown? Should the form builder have the option to move it, or delete it? We can pre-fill this info on upload, should we? Should changes that the user makes in this component always overwrite what appears on the My Forms page?

Acceptance Criteria

Required outcomes of the story

• Form builders have an affordance that is easy to discover, understand and use for modifying the title and description of the form that they are building

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