## Background
- **Description:** Hierarchical structure that provides nested levels of navigation.
- **History:** Conversations about Accordion Vs. TreeView in this task T280785
- **Considerations:** //list any known challenges or blockers, or any other important information//
- **Known use case(s):** //describe known use cases for this component, including the project, team, and timeline//
| {F35870054} | {F35870050} |
| **Vector 2022 toc sections** | **Wikifunctions** [WIP] [[ https://www.figma.com/file/uNBSv1e4ceA8tGNr29R9vp/Default-View?node-id=3296%3A39515&t=oBW46gJXfAUaHWHF-0 | Figma ]] |
### User stories
- As a designer/developer I need to use the TreeView component to create different levels of navigation.
- As a designer/developer I need to understand the difference between Accordion and TreeView components.
### Previous implementations
These artifacts are listed for historical context. The figma spec, linked below, is the source of truth for the new component.
- **Design style guide:** //There are no previous guidelines for this component//
- **OOUI:** //There is no previous implementation in OOUI for this component//
---
## Codex implementation
-
### Component task owners
- Designer: //add the main designer's name//
- Developer: //add the main developer's name//
### Design spec
// Once a component spec sheet has been created in Figma, remove the note stating that the spec is missing and link to the spec below. //
A component spec sheet has not been created yet.
| Component spec sheet |
---
## Stage 1: Minimum viable product (MVP)
MVP includes basic layout, default states, and most important functionality.
### Acceptance criteria
- [] Determine what MVP includes for this component and document this in a subtask. Assign task to designer.
- [] Design MVP. Once complete, assign task to developer.
- [] Implement MVP
---
## Stage 2: Additional states, features, and variants
This might include a disabled state, framed/frameless designs, transitions, supporting different use cases, etc., which will be captured in separate subtasks.
### Acceptance criteria
- [] Document design and implementation of additional states and features in individual subtasks
- [] Complete each additional state/feature subtask
---
## Stage 3: Refinement
This stage includes any final touches or bug fixes needed before the component can be deemed complete, which will be captured in separate subtasks.
### Acceptance criteria
- [] Finalize docs: open and complete a subtask for any additional demos that need to be added or documentation that needs work
- [] Meet accessibility standards: open and complete a subtask for any necessary accessibility improvements
- [] Meet internationalization standards: open and complete a subtask to fix any i18n bugs
- [] Complete testing: open and complete a subtask for any additional unit or functional tests that are needed