OpenATO / demo-ui

Front-end for demo
GNU General Public License v3.0
0 stars 0 forks source link

Identify controls, components, and tasks to show in demo #10

Open suzanne-gray opened 1 year ago

suzanne-gray commented 1 year ago

Overview

The demo will work with a limited number of controls and components in order to show how they interact. We need to figure out which ones we want to showcase and where the variables will show up in the product.

Background

The demo needs to show:

Controls We know we want to use the control for password length, 1A-5.1. Do we need to use all the sub-controls or just some of them?

Components We know we will use the Drupal component as an example. Do we need to include anything else?

User Tasks What questions does the user need to answer in order to implement the controls? Where in the demo do these questions get answered? (agency profile vs. project profile vs. component detail)

Steps

References

Working doc with control info

Acceptance Criteria

Team

🌀 Unknown/TBD/Other