You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 22, 2024. It is now read-only.
You'll need to complete Hack for LA onboarding before beginning this checklist. If you're deciding between HFLA teams, you can request in our Slack channel to observe one of our all-hands meetings first.
Slack
Introduce yourself in the #design-systems Slack channel. Request a recurring 1-on-1 meeting with your team lead, and that the PM grant you access to our Google Drive, Google Calendar meetings, Figma project, and Github repo. (Until you have access, some of the following links will not work.) @ the PM and your team lead in this message.
Check your calendar and accept the invites to our recurring meetings. You might occasionally be asked to attend a meeting outside of your function.
Update your Slack profile in the HFLA workspace. Under Title, type in your role and the name of the team (i.e. "UX Writer, Design Systems").
Under Pronunciation, type in any pronunciation guidelines and your preferred pronouns.
GitHub
Doing the following tasks on desktop is recommended.
Profile settings
At the top right of this very webpage, you'll see a row of dropdown menus. Click "⭐ Star" so the button turns into ⭐ Starred. Now, people will be able to find your profile from our repository's homepage.
Issue settings
Below the Pins and Star settings, you'll see a list of more settings, starting with "Assignee" at the top. Add your Github username as an assignee.
Select the labelrole: _ (your role).
Select the projectLearning about design systems.
Click 🚧 BACKLOG to open a dropdown, and select ✈️ IN PROGRESS.
About project documentation
At the top of this page, find "Wiki." Under "Pages," read the "Documentation 101" article about how project documentation works.
At the very top of this page, find "Issues." Here you'll be able to find all issues that you've created or been assigned to, regardless of which repository it's a part of.
Optional Step to learn about Design Systems: Under "Tutorials", find the PDF of Alla Kholmatova's Design Systems book and read chapter 1 (pages 18-45).
Optional Step to learn about the stakeholder needs and the purpose of the project: Under "User Insights" > "Stakeholder", listen to the stakeholder interview. You can follow along with the transcript.
Learning about our Product and the history of the project
First, read the Release Note for "HfLA Figma Kit". You can access the PDF from the above link or here.
Then you can open the v1.0 in Figma to see the product we released for our external audience who are designers across HfLA. You can access the link to Figma from the release section mentioned above.
Optional Step: Go to our Wiki > Background so you can learn about the history of the project. You can access the background page either from the sidebar pages on right or here.
Other Steps
If you are a UXer
Click the green button Submit new issue on this page. This issue will generate under HfLA's UX/UI community of practice and is meant to track the skills you learn during your time at HfLA.
You'll need to complete Hack for LA onboarding before beginning this checklist. If you're deciding between HFLA teams, you can request in our Slack channel to observe one of our all-hands meetings first.
Slack
GitHub
Doing the following tasks on desktop is recommended.
Profile settings
⭐ Starred
. Now, people will be able to find your profile from our repository's homepage.Issue settings
role: _
(your role).Learning about design systems
.🚧 BACKLOG
to open a dropdown, and select✈️ IN PROGRESS
.About project documentation
Drive
Learning about our Product and the history of the project
Other Steps
If you are a UXer
Submit new issue
on this page. This issue will generate under HfLA's UX/UI community of practice and is meant to track the skills you learn during your time at HfLA.If you are a developer
If you are a product manager
Yay!
The text was updated successfully, but these errors were encountered: