Scaffolding of the new Quiz Creation Vue Component #11010
Labels
APP: Coach
Re: Coach App (lessons, quizzes, groups, reports, etc.)
DEV: frontend
TAG: new feature
New user-facing feature
TAG: user strings
Application text that gets translated
Milestone
Overview
In order to support upcoming work, we need to create a Quiz Creation component that mirrors the Figma designs provided and is temporarily populated by dummy data. We can incorporate some of our existing components and patterns as-is into this new component.
Before we build out all of the code that supports quiz creation behind the scenes, we will scaffold out this new component. This task involves visually creating the component and temporarily filling it with dummy data. We want the scaffolding to include the basic layout of the component as shown in the Figma, the strings the component requires, and the buttons & icons it uses. The buttons and icons do not need to be hooked up to actual quiz creation functionality, but should be implemented to work as laid out in the Figma (e.g. the
Jump to question
button is a dropdown - in this issue, we would like to seeJump to question
opening as a dropdown, but the content within it should just be dummy data/filler - no expectation of displaying actual questions).Expected appearance
The component should visually match the Figma designs as closely as reasonable, but does not need to include the central table containing the list of questions. The table of drag-and-droppable accordion item questions will be accomplished in a separate PR. Therefore, the expected UI outcome of this issue should be similar to:
Acceptance Criteria
ImmersivePage
within aKPageContainer
)KPageContainer
holding main contentKTextbox
containing quiz titleKTab*
component to display sectionsAdd Section
KButton
in line withKTab
sEdit Section
andJump to question
KButton
sBottomAppBar
with aKButton
to save the quiz<div/>
where the accordion list of questions will goNote: No need to wire up data, but wherever you would expect to get data, you should put a FIXME or TODO comment indicating what should be expected there. The aim is to have this issue completely fairly quickly, so while the goal is to replicate the design as closely as possible, there's no need to be pixel-perfect at this stage.
Once this PR is ready, it would be ideal to conduct an a11y review to identify any open a11y-related issues found in this scaffolding, to be applied to follow-up issues.
The text was updated successfully, but these errors were encountered: