Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

create outline of expectation for May 17 meeting #18

Open
3 of 5 tasks
ProsperousHeart opened this issue May 11, 2023 · 4 comments
Open
3 of 5 tasks

create outline of expectation for May 17 meeting #18

ProsperousHeart opened this issue May 11, 2023 · 4 comments
Assignees
@ProsperousHeart
Labels
documentation Update to documentation requirements

Comments

@ProsperousHeart
Copy link
Member

ProsperousHeart commented May 11, 2023 •
edited
Loading

  • 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
  • explanation of hierarchy of elements (for UX/UI people to know what component names are) --- INCOMPLETE, see here
  • 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 ProsperousHeart added the documentation Update to documentation label May 11, 2023
@ProsperousHeart ProsperousHeart self-assigned this May 11, 2023
@ProsperousHeart
Copy link
Member Author

ProsperousHeart commented May 11, 2023 •
edited
Loading

Created the following issues for people to begin working on:

Nice to haves:

@ProsperousHeart
Copy link
Member Author

ProsperousHeart commented May 11, 2023 •
edited
Loading

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

@ProsperousHeart ProsperousHeart changed the title create outline of expectation for May meeting create outline of expectation for May 17 meeting May 11, 2023
@ShermanMarshall
Copy link
Contributor

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

@ProsperousHeart
Copy link
Member Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ProsperousHeart ProsperousHeart

Labels
documentation Update to documentation requirements
Projects
Site Sprint Board
Status: In Progress
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ShermanMarshall @ProsperousHeart