create outline of expectation for May 17 meeting

[ProsperousHeart]

• [x] have write up explaining we need HTML / React devs (see here)
• [ ] training for PR request
• [ ] content doc for attendees to pull from for their components
• [x] explanation of hierarchy of elements (for UX/UI people to know what component names are) --- INCOMPLETE, see here
• [x] create issues for each section needed

Will consolidate code at end of meeting.

Different components should have their own repo issues. This will allow for people to go between break rooms:

• "bare bones creation"
• CSS / Visual

[ProsperousHeart]

Created the following issues for people to begin working on:

• 19

• 20

• 21

• 23

• 24

• 25

• 26

• 27

Nice to haves:

• 22

[ProsperousHeart]

Instead of dictating CSS stuff, inquired to the UI/UX people how they normally prefer to complete this as per this Discord message

[ShermanMarshall]

How do we want to split up components? Rock, paper, scissors; vote; draw straws?

[ProsperousHeart]

How do we want to split up components? Rock, paper, scissors; vote; draw straws?

The same way you would normally - from the backlog.

1. Assign it to themself then work it.
2. If help needed, speak up.
3. When ready for review, follow the process.
4. Start another one.