Joining the Team

Introduction

Welcome to the Expunge Assist team! This guide will help get you up to speed on what you need to know to get started as a project team member.

Let's go!

If you have not read the Guide for New Volunteers, please do so.

Read Introduction to the Project if you haven't already read it.
Join the #expunge-assist(https://app.slack.com/client/T04502KQX/CN8NXTPK5) Slack channel and introduce yourself.
Slack our PMs (Thomas Demoner, Valeriya Metla and Jamie Siu) with your desired volunteer role and email address.
PMs will onboard you using the GitHub onboarding issue for your team:
1. Accept your Google Drive invite to access the shared folder.
2. Add yourself to the Team Roster and inform PM after you have done so.
Attend our biweekly Team Meetings (alternating Tuesdays at 5pm PST) as well as meeting for your team (all links in the Slack channel):
1. Development Meeting (Thursday at 6pm PST)
2. Dev/Design/Product Collab. Meeting (Monday at 5pm PST)
3. UX Design Team meeting (Wednesday at 5pm PST)
4. Content Meeting (Thursday 11 am PST)
5. Content and Design Meeting (Friday 9:30 am PST)
6. Research Meeting (Friday at 11 am PST)
7. If you are a new PM - also attend:
  1. PM Meeting (Monday at 3 PST) and 2) Org Meeting (Thursday at 4 PST)
Review Communication & Style Guidelines for the project
Review Gudes about using GitHub

Accessibility standards

Title III of the Americans with Disabilities Act (ADA) requires that all websites be accessible to people with disabilities. The World Wide Web (W3C) Consortium's Web Content Accessibility Guidelines (WCAG) 2.0 Level AA function as the current legal standard for website accessibility.

Get acquainted with accessibility: https://www.ada.gov/pcatoolkit/chap5toolkit.htm

DRAFT NOT YET FILLED OUT

Who are you?

Click the link that applies to you to find a sequence of immediate action steps:

Web Developer

UI/UX Designer

UX Researcher

Content Designer/UX Writer

Product Manager/Owner

Other Volunteer

The Wiki is a working document and we would love to improve it. Please compile any questions and suggestions you may have and submit it via GitHub. Here's information on how to create a GiHub issue.