zydronium/manage.get.gov
1
0
Fork 0
mirror of https://github.com/cisagov/manage.get.gov.git synced 2025-07-20 01:36:00 +02:00
Code Issues Projects Releases Packages Wiki Activity

Update and rename design-onboarding.md to designer-onboarding.md

Browse source
This commit is contained in:
Kristina Yin 2024-04-08 10:50:31 -07:00 • committed by GitHub
parent db65cdba9b
commit 80ce98bf9c
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 88 additions and 49 deletions
Download patch file Download diff file Expand all files Collapse all files

49
.github/ISSUE_TEMPLATE/design-onboarding.md vendored
View file

@ -1,49 +0,0 @@
---
name: Design Onboarding
about: Onboarding steps for designers.
title: 'Designer Onboarding: GH_HANDLE'
labels: design, onboarding
assignees: katherineosos
---
# Designer Onboarding
- Onboardee: _GH handle of person being onboarded_
- Onboarder: _GH handle of onboard buddy_
Read the .gov onboarding document
Get access to Slack. Familiar yourself with the channels. Post a hi message in the disc channel.
Get access to Google doc. Navigate through our documents. Find the design folders.
Get access to our project on Github. Look at our project directories. Find our product repos. Find our Product backlog.
Know who to ask for what -- know your team mates.
Make sure you are invited to all our team meetings.
Get an introduction on our application and the design process from Katherine, our Design lead.
Understand the designer tools (Miro, Fisma, etc).
Familiarize with our design guides (e.g., USWDS, 21st Century Integrated Digital Experience Act)
Make a request to the dev lead to get your sandbox created and get access to /admin (added to fixatures).
Look at get.gov. Test out manage.get.gov.
Create your POM and present in the Team coffee.
Schedule a meet-n-greet with Paul, our Product Manager to learn about our application.
Schedule a meet-n-greet with Vicky, our Scrum master to get overview of our Scrum process, our backlog, how our sprint works and how to use your Scrum master to your advantage.
Check up with your manager on your EOD clearance process.
## Access
Make sure you have access / been added to the following:
- [ ] The [.gov team](https://github.com/orgs/cisagov/teams/gov) under cisagov on GitHub
- [ ] [Slack](dhscisa.enterprise.slack.com), and added to the necessary channels
- [ ] Google Drive Project folder
- [ ] Figma
- [ ] Team meetings
### Steps for the onboardee
- [ ]
### Steps for the onboarder
- [ ] Setup a [sandbox] for the onboardee (#setting-up-developer-sandbox)
- [ ] Add the onboardee to our login.gov sandbox team (`.gov Registrar`) via the [dashboard](https://dashboard.int.identitysandbox.gov/)
## Documents to Review
- [ ] [Team Onboarding](https://docs.google.com/document/d/1ukbpW4LSqkb_CCt8LWfpehP03qqfyYfvK3Fl21NaEq8/edit?usp=sharing)

88
.github/ISSUE_TEMPLATE/designer-onboarding.md vendored Normal file
View file

@ -0,0 +1,88 @@
---
name: Designer Onboarding
about: Onboarding steps for designers.
title: 'Designer Onboarding: GH_HANDLE'
labels: design, onboarding
assignees: katherineosos
---
# Designer Onboarding
- Onboardee: _GH handle of person being onboarded_
- Onboarder: _GH handle of onboard buddy_
Welcome to the .gov team! We're excited to have you here. Please follow the steps below to get everything set up. An onboarding buddy will help grant you access to all the tools and platforms we use. If you haven't been assigned an onboarding buddy, let us know in the #dotgov-disco channel.
Read the .gov onboarding document
Get access to Slack. Familiar yourself with the channels. Post a hi message in the disc channel.
Get access to Google doc. Navigate through our documents. Find the design folders.
Get access to our project on Github. Look at our project directories. Find our product repos. Find our Product backlog.
Know who to ask for what -- know your team mates.
Make sure you are invited to all our team meetings.
Get an introduction on our application and the design process from Katherine, our Design lead.
Understand the designer tools (Miro, Fisma, etc).
Familiarize with our design guides (e.g., USWDS, 21st Century Integrated Digital Experience Act)
Make a request to the dev lead to get your sandbox created and get access to /admin (added to fixatures).
Look at get.gov. Test out manage.get.gov.
Create your POM and present in the Team coffee.
Schedule a meet-n-greet with Paul, our Product Manager to learn about our application.
Schedule a meet-n-greet with Vicky, our Scrum master to get overview of our Scrum process, our backlog, how our sprint works and how to use your Scrum master to your advantage.
Check up with your manager on your EOD clearance process.
## Onboardee
### Steps for the onboardee
- [ ] Read the [.gov onboarding doc](https://docs.google.com/document/d/1ukbpW4LSqkb_CCt8LWfpehP03qqfyYfvK3Fl21NaEq8/edit?usp=sharing) thoroughly.
- [ ] Accept Slack invitation and fill out your profile.
- [ ] For our Slack profile names, we usually follow the naming convention of `Firstname Lastname (Org, State, pronouns)`.
Example: Katherine Osos (Truss, MN, she/her)
- [ ] Make sure you have been added to the necessary [channels](https://docs.google.com/document/d/1ukbpW4LSqkb_CCt8LWfpehP03qqfyYfvK3Fl21NaEq8/edit#heading=h.li3lqcygw8ax) and familiarize yourself with them.
- [ ] Get access to our [Project Folder](https://drive.google.com/drive/folders/1qkoFQBlzXA7axi9CZ_OBhlJqRcqlNfpW?usp=drive_link) on Google Drive.
- [ ] Explore the folders and docs. Designers interface with the Product Design, Content, and Research folders most often.
- [ ] Make sure you have been invited to our [team meetings](https://docs.google.com/document/d/1ukbpW4LSqkb_CCt8LWfpehP03qqfyYfvK3Fl21NaEq8/edit#heading=h.h62kzew057p1) on Google Meet.
- [ ] Get access to our design tools: [Figma](https://www.figma.com/files/1287135731043703282/team/1299882813146449644), Miro
- [ ] Follow the steps in [Preparing for your sandbox](####preparing-for-your-sandbox) section below.
#### Preparing for your sandbox
- [ ] Create two identity sandbox accounts, this is login.gov’s test environment
- How to make it:
- [ ] Navigate to [identity sandbox](https://idp.int.identitysandbox.gov/)
- [ ] Click create an account
- [ ] Fill in the information with fake data, though you may choose to use your real name. For the social security field, input a SSN that starts with 666 or 900. Instead of uploading a picture of your ID, you may upload any picture (include a cat meme).
- [ ] See login.gov’s [developer section](https://developers.login.gov/testing/#testing-identity-proofing) for testing with identity sandbox if you encounter issues.
- One account should be your preferred work email for the username, the second should be the SAME email address followed by a plus one
- Ex: bob@dhs.gov for the first login account and bob+1@dhs.gov
- One account will represent a normal user while the other will be your way of simulating a “analyst”
- [ ] Sandbox: Have an engineer create a sandbox for you (message in #dotgov-dev Slack channel). This will be used to make content updates in the UI.
- [ ] You will receive a link for Cloud.gov to be added to an organization. Be sure to verify via that link or you may not be able to access any sandbox.
- [ ] Also ask that they add mock data to that sandbox. This will be helpful for testing various scenarios in the UI.
- Note: at any point you can add mock data to your sandbox and reset all test data in you sandbox by running the [reset action on github](https://github.com/cisagov/getgov/actions/workflows/reset-db.yaml)
- Go to the provided link. Click the Run Workflow dropdown
- Select your sandbox environment (your initials).
- Then click the green “Run workflow” button
- [ ] Your sandbox makes the app available online, and everyone should be able to access your sandbox once it is made. See the [sandbox section of the onboarding doc](https://docs.google.com/document/d/1ukbpW4LSqkb_CCt8LWfpehP03qqfyYfvK3Fl21NaEq8/edit#heading=h.cdlfxamcvus5), your sandbox url will be in this format: https://getgov-<ENV>.app.cloud.gov/ where ENV refers to your initials.
- [ ] Make sure to check that you can log into your sandbox with the identity sandbox login credentials you made.
Request access to /admin (also known as “add to fixtures”)
Follow the steps in the developer readme for adding yourself to admin
When you get to the last step about editing the code you can instead share the ID you found in the previous step with someone on the development team
OPTIONAL: Request an “analyst” account by using your second identity sandbox credential
This account will allow you to see what an analyst sees when they log in to the application
Use whichever identity sandbox account you did not use when requesting /admin access and follow the developer readme for creating an analyst account
Tip: You can add a ‘+1’ to the end of your gmail account to create a “new” email address that can be used for making a new Login.gov account (example: “orginalemailaddress+1@gmail.com”). Everything will still go to the same email without needing to make a new one.
Just like with /admin, in the last step about editing the code you can instead share the ID you found in the previous step with someone on the development team
### Access
By following the steps, you should have access / been added to the following:
- [ ] The [.gov team](https://github.com/orgs/cisagov/teams/gov) under cisagov on GitHub
- [ ] [Slack](dhscisa.enterprise.slack.com), and have been added to the necessary channels
- [ ] [Google Drive Project folder](https://drive.google.com/drive/folders/1qkoFQBlzXA7axi9CZ_OBhlJqRcqlNfpW?usp=drive_link)
- [ ] [.gov team on Figma](https://www.figma.com/files/1287135731043703282/team/1299882813146449644) (as an editor if you have a license)
- [ ] [Team meetings](https://docs.google.com/document/d/1ukbpW4LSqkb_CCt8LWfpehP03qqfyYfvK3Fl21NaEq8/edit#heading=h.h62kzew057p1)
## Onboarder
### Steps for the onboarder
- [ ] Setup a [sandbox] for the onboardee (#setting-up-developer-sandbox)
- [ ] Add the onboardee to our login.gov sandbox team (`.gov Registrar`) via the [dashboard](https://dashboard.int.identitysandbox.gov/)