[Design] Redesign the ‘Add element’ menu dropdown

[nichole-aquino]

Overview

Form builders can easily scan and understand their options when adding components.

Context

Reference:

• Figma
• Spreadsheet of component names and descriptions

Issues/assumptions:

• The current menu is long, not categorized, and not scrollable - Question/add element dropdown not scrollable #417
• Descriptions will help builders understand how to use components (before adding them)

Solution (WIP):

• Help builders scan and understand their options with a submenu or megamenu, categorized by:

• Choice
• Freeform answers
• Personal information
• Form structure
• Other

• Megamenu option (for the main 'Add element' and for 'Add question to set' in the the repeater component)

• Submenu option (only for the main 'Add element')

Acceptance Criteria

The changes should be made to:

• The main ‘Add element’ button
• In the (repeating) question set components, the menu for 'Add question to set'

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