From 784fcbc26a8a146efa7aa7a0802d4ac1eb178b5e Mon Sep 17 00:00:00 2001 From: Rebecca Hsieh Date: Thu, 4 Apr 2024 15:35:15 -0700 Subject: [PATCH 01/15] Update expiration date code and unit test --- src/registrar/admin.py | 8 ++------ src/registrar/tests/test_admin.py | 12 +++--------- 2 files changed, 5 insertions(+), 15 deletions(-) diff --git a/src/registrar/admin.py b/src/registrar/admin.py index e0c98b7c2..37535f1a2 100644 --- a/src/registrar/admin.py +++ b/src/registrar/admin.py @@ -1600,12 +1600,8 @@ class DomainAdmin(ListHeaderAdmin): # No expiration date was found. Return none. extra_context["extended_expiration_date"] = None return super().changeform_view(request, object_id, form_url, extra_context) - - if curr_exp_date < date.today(): - extra_context["extended_expiration_date"] = date.today() + relativedelta(years=years_to_extend_by) - else: - new_date = domain.registry_expiration_date + relativedelta(years=years_to_extend_by) - extra_context["extended_expiration_date"] = new_date + new_date = curr_exp_date + relativedelta(years=years_to_extend_by) + extra_context["extended_expiration_date"] = new_date else: extra_context["extended_expiration_date"] = None diff --git a/src/registrar/tests/test_admin.py b/src/registrar/tests/test_admin.py index 368f30721..4cb66c534 100644 --- a/src/registrar/tests/test_admin.py +++ b/src/registrar/tests/test_admin.py @@ -74,11 +74,10 @@ class TestDomainAdmin(MockEppLib, WebTest): ) super().setUp() - @skip("TODO for another ticket. This test case is grabbing old db data.") @patch("registrar.admin.DomainAdmin._get_current_date", return_value=date(2024, 1, 1)) def test_extend_expiration_date_button(self, mock_date_today): """ - Tests if extend_expiration_date button extends correctly + Tests if extend_expiration_date modal gives an accurate date """ # Create a ready domain with a preset expiration date @@ -105,17 +104,11 @@ class TestDomainAdmin(MockEppLib, WebTest): # Follow the response response = response.follow() - # refresh_from_db() does not work for objects with protected=True. - # https://github.com/viewflow/django-fsm/issues/89 - new_domain = Domain.objects.get(id=domain.id) - - # Check that the current expiration date is what we expect - self.assertEqual(new_domain.expiration_date, date(2025, 5, 25)) - # Assert that everything on the page looks correct self.assertEqual(response.status_code, 200) self.assertContains(response, domain.name) self.assertContains(response, "Extend expiration date") + self.assertContains(response, "New expiration date: May 25, 2025") # Ensure the message we recieve is in line with what we expect expected_message = "Successfully extended the expiration date." @@ -127,6 +120,7 @@ class TestDomainAdmin(MockEppLib, WebTest): extra_tags="", fail_silently=False, ) + mock_add_message.assert_has_calls([expected_call], 1) @less_console_noise_decorator From 739e24ea3258fba7a985d6b509a7a4eda54d9dc8 Mon Sep 17 00:00:00 2001 From: Kristina Yin <140533113+kristinacyin@users.noreply.github.com> Date: Fri, 5 Apr 2024 12:36:27 -0700 Subject: [PATCH 02/15] Create design-onboarding --- .github/ISSUE_TEMPLATE/design-onboarding | 56 ++++++++++++++++++++++++ 1 file changed, 56 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/design-onboarding diff --git a/.github/ISSUE_TEMPLATE/design-onboarding b/.github/ISSUE_TEMPLATE/design-onboarding new file mode 100644 index 000000000..bf7047706 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/design-onboarding @@ -0,0 +1,56 @@ +--- +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 + +### Steps for the onboardee +- [ ] Setup [commit signing in Github](#setting-up-commit-signing) and with git locally. +- [ ] [Create a cloud.gov account](https://cloud.gov/docs/getting-started/accounts/) +- [ ] Email github@cisa.dhs.gov (cc: Cameron) to add you to the [CISA Github organization](https://github.com/getgov) and [.gov Team](https://github.com/orgs/cisagov/teams/gov). +- [ ] Ensure you can login to your cloud.gov account via the CLI +```bash +cf login -a api.fr.cloud.gov --sso +``` +- [ ] Have an admin add you to cloud.gov org and set up your [sandbox developer space](#setting-up-developer-sandbox). Ensure you can deploy to your sandbox space. +- [ ] Have an admin add you to our login.gov sandbox team (`.gov Registrar`) via the [dashboard](https://dashboard.int.identitysandbox.gov/). + + **Note:** As mentioned in the [Login documentation](https://developers.login.gov/testing/), the sandbox Login account is different account from your regular, production Login account. If you have not created a Login account for the sandbox before, you will need to create a new account first. + +- [ ] Optional- add yourself as a codeowner if desired. See the [Developer readme](https://github.com/cisagov/getgov/blob/main/docs/developer/README.md) for how to do this and what it does. + +### Steps for the onboarder +- [ ] Add the onboardee to cloud.gov org (cisa-dotgov) +- [ ] Setup a [developer specific space for the new developer](#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) From 52bfcfa64defc0456d097214dee7ad1829800777 Mon Sep 17 00:00:00 2001 From: Kristina Yin <140533113+kristinacyin@users.noreply.github.com> Date: Fri, 5 Apr 2024 12:50:51 -0700 Subject: [PATCH 03/15] Update design-onboarding organizing steps --- .github/ISSUE_TEMPLATE/design-onboarding | 23 ++++++++--------------- 1 file changed, 8 insertions(+), 15 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/design-onboarding b/.github/ISSUE_TEMPLATE/design-onboarding index bf7047706..01f1f8e83 100644 --- a/.github/ISSUE_TEMPLATE/design-onboarding +++ b/.github/ISSUE_TEMPLATE/design-onboarding @@ -29,25 +29,18 @@ Schedule a meet-n-greet with Vicky, our Scrum master to get overview of our Scru 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 -- [ ] Setup [commit signing in Github](#setting-up-commit-signing) and with git locally. -- [ ] [Create a cloud.gov account](https://cloud.gov/docs/getting-started/accounts/) -- [ ] Email github@cisa.dhs.gov (cc: Cameron) to add you to the [CISA Github organization](https://github.com/getgov) and [.gov Team](https://github.com/orgs/cisagov/teams/gov). -- [ ] Ensure you can login to your cloud.gov account via the CLI -```bash -cf login -a api.fr.cloud.gov --sso -``` -- [ ] Have an admin add you to cloud.gov org and set up your [sandbox developer space](#setting-up-developer-sandbox). Ensure you can deploy to your sandbox space. -- [ ] Have an admin add you to our login.gov sandbox team (`.gov Registrar`) via the [dashboard](https://dashboard.int.identitysandbox.gov/). - - **Note:** As mentioned in the [Login documentation](https://developers.login.gov/testing/), the sandbox Login account is different account from your regular, production Login account. If you have not created a Login account for the sandbox before, you will need to create a new account first. - -- [ ] Optional- add yourself as a codeowner if desired. See the [Developer readme](https://github.com/cisagov/getgov/blob/main/docs/developer/README.md) for how to do this and what it does. +- [ ] ### Steps for the onboarder -- [ ] Add the onboardee to cloud.gov org (cisa-dotgov) -- [ ] Setup a [developer specific space for the new developer](#setting-up-developer-sandbox) +- [ ] 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/) From 6548d3870f432d0e588937e0d098363984b79b9b Mon Sep 17 00:00:00 2001 From: Kristina Yin <140533113+kristinacyin@users.noreply.github.com> Date: Fri, 5 Apr 2024 12:52:09 -0700 Subject: [PATCH 04/15] Rename design-onboarding to design-onboarding.md Forgot to make it an md file --- .../ISSUE_TEMPLATE/{design-onboarding => design-onboarding.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename .github/ISSUE_TEMPLATE/{design-onboarding => design-onboarding.md} (100%) diff --git a/.github/ISSUE_TEMPLATE/design-onboarding b/.github/ISSUE_TEMPLATE/design-onboarding.md similarity index 100% rename from .github/ISSUE_TEMPLATE/design-onboarding rename to .github/ISSUE_TEMPLATE/design-onboarding.md From db65cdba9b794359d6e0073d2463d31612d14b4a Mon Sep 17 00:00:00 2001 From: Kristina Yin <140533113+kristinacyin@users.noreply.github.com> Date: Fri, 5 Apr 2024 12:53:12 -0700 Subject: [PATCH 05/15] Update design-onboarding.md --- .github/ISSUE_TEMPLATE/design-onboarding.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/design-onboarding.md b/.github/ISSUE_TEMPLATE/design-onboarding.md index 01f1f8e83..3cca6e96c 100644 --- a/.github/ISSUE_TEMPLATE/design-onboarding.md +++ b/.github/ISSUE_TEMPLATE/design-onboarding.md @@ -30,11 +30,11 @@ 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 +- [ ] 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 - [ ] From 80ce98bf9cacb93561f4e8c93b35f5a1dc8e22de Mon Sep 17 00:00:00 2001 From: Kristina Yin <140533113+kristinacyin@users.noreply.github.com> Date: Mon, 8 Apr 2024 10:50:31 -0700 Subject: [PATCH 06/15] Update and rename design-onboarding.md to designer-onboarding.md --- .github/ISSUE_TEMPLATE/design-onboarding.md | 49 ----------- .github/ISSUE_TEMPLATE/designer-onboarding.md | 88 +++++++++++++++++++ 2 files changed, 88 insertions(+), 49 deletions(-) delete mode 100644 .github/ISSUE_TEMPLATE/design-onboarding.md create mode 100644 .github/ISSUE_TEMPLATE/designer-onboarding.md diff --git a/.github/ISSUE_TEMPLATE/design-onboarding.md b/.github/ISSUE_TEMPLATE/design-onboarding.md deleted file mode 100644 index 3cca6e96c..000000000 --- a/.github/ISSUE_TEMPLATE/design-onboarding.md +++ /dev/null @@ -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) diff --git a/.github/ISSUE_TEMPLATE/designer-onboarding.md b/.github/ISSUE_TEMPLATE/designer-onboarding.md new file mode 100644 index 000000000..b04ea4314 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/designer-onboarding.md @@ -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-.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/) From ca4490e3da8e972c7a9b272c2d500c2942bcba02 Mon Sep 17 00:00:00 2001 From: Kristina Yin <140533113+kristinacyin@users.noreply.github.com> Date: Mon, 8 Apr 2024 20:28:19 -0700 Subject: [PATCH 07/15] Update designer-onboarding.md --- .github/ISSUE_TEMPLATE/designer-onboarding.md | 19 +++++++++---------- 1 file changed, 9 insertions(+), 10 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/designer-onboarding.md b/.github/ISSUE_TEMPLATE/designer-onboarding.md index b04ea4314..6f2374311 100644 --- a/.github/ISSUE_TEMPLATE/designer-onboarding.md +++ b/.github/ISSUE_TEMPLATE/designer-onboarding.md @@ -61,16 +61,15 @@ Check up with your manager on your EOD clearance process. - 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-.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 + - [ ] 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-.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](https://github.com/cisagov/getgov/blob/main/docs/developer/README.md#adding-user-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](https://github.com/cisagov/getgov/blob/main/docs/developer/README.md#adding-an-analyst-to-admin) + - 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 From f6d95723cea38dea2605ceef6dd883930449ee26 Mon Sep 17 00:00:00 2001 From: Kristina Yin <140533113+kristinacyin@users.noreply.github.com> Date: Mon, 8 Apr 2024 21:48:28 -0700 Subject: [PATCH 08/15] Update designer-onboarding.md --- .github/ISSUE_TEMPLATE/designer-onboarding.md | 40 +++++++++---------- 1 file changed, 19 insertions(+), 21 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/designer-onboarding.md b/.github/ISSUE_TEMPLATE/designer-onboarding.md index 6f2374311..8f36462dc 100644 --- a/.github/ISSUE_TEMPLATE/designer-onboarding.md +++ b/.github/ISSUE_TEMPLATE/designer-onboarding.md @@ -14,35 +14,28 @@ assignees: katherineosos 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. +- [ ] Accept an invitation to our Slack workspace 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. +- [ ] Create a [Google workspace enterprise account](https://docs.google.com/document/d/1ukbpW4LSqkb_CCt8LWfpehP03qqfyYfvK3Fl21NaEq8/edit?pli=1#heading=h.xowzg9w0qlis) for CISA. - [ ] 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. +- [ ] Review our [design tools](https://docs.google.com/document/d/1ukbpW4LSqkb_CCt8LWfpehP03qqfyYfvK3Fl21NaEq8/edit?pli=1#heading=h.aprurp3z4gmv). +- [ ] Accept invitation to our [Figma workspace](https://www.figma.com/files/1287135731043703282/team/1299882813146449644). +- [ ] Follow the steps in [Preparing for your sandbox](#preparing-for-your-sandbox) section below. +- [ ] Schedule coffee chats with Design Lead, other designers, scrum master, and product manager ([team directory](https://docs.google.com/document/d/1ukbpW4LSqkb_CCt8LWfpehP03qqfyYfvK3Fl21NaEq8/edit?pli=1#heading=h.1vq6r8e52e9f)). +- [ ] Look over [recommended reading](https://docs.google.com/document/d/1ukbpW4LSqkb_CCt8LWfpehP03qqfyYfvK3Fl21NaEq8/edit?pli=1#heading=h.7ox9ee7v5q5n) and [relevant links](https://docs.google.com/document/d/1ukbpW4LSqkb_CCt8LWfpehP03qqfyYfvK3Fl21NaEq8/edit?pli=1#heading=h.d9pac1gc751t). +- [ ] Fill out your own Personal Operating Manual (POM) on the [team norming board](https://miro.com/app/board/uXjVMxMu1SA=/). Present it on the next team coffee meeting. +- [ ] FOR FEDERAL EMPLOYEES: Check in with your manager on the CISA onboarding process and getting your PIV card. +- [ ] FOR CONTRACTORS: Check with your manager on your EOD clearance process. +- [ ] OPTIONAL: Request access to our [analytics tools](https://docs.google.com/document/d/1ukbpW4LSqkb_CCt8LWfpehP03qqfyYfvK3Fl21NaEq8/edit?pli=1#heading=h.9q334hs4lbks). + #### Preparing for your sandbox - [ ] Create two identity sandbox accounts, this is login.gov’s test environment @@ -80,8 +73,13 @@ By following the steps, you should have access / been added to the following: - [ ] [.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/) +- [ ] Make sure onboardee is given an invitation to our Slack workspace +- [ ] Add onboardee to dotgov Slack channels +- [ ] Once onboardee has a Google workspace enterprise account, add onboardee to Project Folder as an editor +- [ ] Once onboardee has been granted a Figma license, add them as an editor to the Figma team workspace +- [ ] Add onboardee to our team meetings +- [ ] If applicable, invite onboardee to Google Analytics, Google Search Console, and Search.gov console From ccf49040fd4d61ec33d1a945f727c513d476a463 Mon Sep 17 00:00:00 2001 From: Kristina Yin <140533113+kristinacyin@users.noreply.github.com> Date: Tue, 9 Apr 2024 16:56:27 -0700 Subject: [PATCH 09/15] Update designer-onboarding.md --- .github/ISSUE_TEMPLATE/designer-onboarding.md | 42 ++++--------------- 1 file changed, 8 insertions(+), 34 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/designer-onboarding.md b/.github/ISSUE_TEMPLATE/designer-onboarding.md index 8f36462dc..0b810fd5c 100644 --- a/.github/ISSUE_TEMPLATE/designer-onboarding.md +++ b/.github/ISSUE_TEMPLATE/designer-onboarding.md @@ -14,6 +14,7 @@ assignees: katherineosos 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. + ## Onboardee ### Steps for the onboardee @@ -22,53 +23,25 @@ Welcome to the .gov team! We're excited to have you here. Please follow the step - [ ] 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. -- [ ] Create a [Google workspace enterprise account](https://docs.google.com/document/d/1ukbpW4LSqkb_CCt8LWfpehP03qqfyYfvK3Fl21NaEq8/edit?pli=1#heading=h.xowzg9w0qlis) for CISA. +- [ ] FOR FEDERAL EMPLOYEES: Create a [Google workspace enterprise account](https://docs.google.com/document/d/1ukbpW4LSqkb_CCt8LWfpehP03qqfyYfvK3Fl21NaEq8/edit?pli=1#heading=h.xowzg9w0qlis) for CISA. - [ ] 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. - [ ] Review our [design tools](https://docs.google.com/document/d/1ukbpW4LSqkb_CCt8LWfpehP03qqfyYfvK3Fl21NaEq8/edit?pli=1#heading=h.aprurp3z4gmv). - [ ] Accept invitation to our [Figma workspace](https://www.figma.com/files/1287135731043703282/team/1299882813146449644). -- [ ] Follow the steps in [Preparing for your sandbox](#preparing-for-your-sandbox) section below. +- [ ] Follow the steps in [preparing for your sandbox](https://docs.google.com/document/d/1ukbpW4LSqkb_CCt8LWfpehP03qqfyYfvK3Fl21NaEq8/edit?pli=1#heading=h.au66hq5e0l8s) section on the onboarding doc. - [ ] Schedule coffee chats with Design Lead, other designers, scrum master, and product manager ([team directory](https://docs.google.com/document/d/1ukbpW4LSqkb_CCt8LWfpehP03qqfyYfvK3Fl21NaEq8/edit?pli=1#heading=h.1vq6r8e52e9f)). - [ ] Look over [recommended reading](https://docs.google.com/document/d/1ukbpW4LSqkb_CCt8LWfpehP03qqfyYfvK3Fl21NaEq8/edit?pli=1#heading=h.7ox9ee7v5q5n) and [relevant links](https://docs.google.com/document/d/1ukbpW4LSqkb_CCt8LWfpehP03qqfyYfvK3Fl21NaEq8/edit?pli=1#heading=h.d9pac1gc751t). -- [ ] Fill out your own Personal Operating Manual (POM) on the [team norming board](https://miro.com/app/board/uXjVMxMu1SA=/). Present it on the next team coffee meeting. +- [ ] Fill out your own Personal Operating Manual (POM) on the [team norming board](https://miro.com/app/board/uXjVMxMu1SA=/). OPTIONAL: Present it on the next team coffee meeting. - [ ] FOR FEDERAL EMPLOYEES: Check in with your manager on the CISA onboarding process and getting your PIV card. - [ ] FOR CONTRACTORS: Check with your manager on your EOD clearance process. - [ ] OPTIONAL: Request access to our [analytics tools](https://docs.google.com/document/d/1ukbpW4LSqkb_CCt8LWfpehP03qqfyYfvK3Fl21NaEq8/edit?pli=1#heading=h.9q334hs4lbks). -#### 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-.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](https://github.com/cisagov/getgov/blob/main/docs/developer/README.md#adding-user-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](https://github.com/cisagov/getgov/blob/main/docs/developer/README.md#adding-an-analyst-to-admin) - - 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 +- [ ] [Slack](https://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) @@ -79,7 +52,8 @@ By following the steps, you should have access / been added to the following: ### Steps for the onboarder - [ ] Make sure onboardee is given an invitation to our Slack workspace - [ ] Add onboardee to dotgov Slack channels -- [ ] Once onboardee has a Google workspace enterprise account, add onboardee to Project Folder as an editor -- [ ] Once onboardee has been granted a Figma license, add them as an editor to the Figma team workspace +- [ ] Add onboardee is added to Project Folder as a "Contributor" (or if you do not have permissions, confirm with Cameron) + - If onboardee if a federal employee, add them as a "Content Manager" instead +- [ ] Once onboardee has been granted a Figma license, add them as an editor to the Figma team workspace, Otherwise, you can add them as a viewer in the meantime. - [ ] Add onboardee to our team meetings - [ ] If applicable, invite onboardee to Google Analytics, Google Search Console, and Search.gov console From 536a3f6684b468cc181563a530e263723cf1917d Mon Sep 17 00:00:00 2001 From: Kristina Yin <140533113+kristinacyin@users.noreply.github.com> Date: Wed, 10 Apr 2024 23:55:28 -0700 Subject: [PATCH 10/15] Update designer-onboarding.md --- .github/ISSUE_TEMPLATE/designer-onboarding.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/designer-onboarding.md b/.github/ISSUE_TEMPLATE/designer-onboarding.md index 0b810fd5c..0921728ae 100644 --- a/.github/ISSUE_TEMPLATE/designer-onboarding.md +++ b/.github/ISSUE_TEMPLATE/designer-onboarding.md @@ -35,7 +35,9 @@ Welcome to the .gov team! We're excited to have you here. Please follow the step - [ ] Fill out your own Personal Operating Manual (POM) on the [team norming board](https://miro.com/app/board/uXjVMxMu1SA=/). OPTIONAL: Present it on the next team coffee meeting. - [ ] FOR FEDERAL EMPLOYEES: Check in with your manager on the CISA onboarding process and getting your PIV card. - [ ] FOR CONTRACTORS: Check with your manager on your EOD clearance process. -- [ ] OPTIONAL: Request access to our [analytics tools](https://docs.google.com/document/d/1ukbpW4LSqkb_CCt8LWfpehP03qqfyYfvK3Fl21NaEq8/edit?pli=1#heading=h.9q334hs4lbks). +- [ ] OPTIONAL: Request access to our [analytics tools](https://docs.google.com/document/d/1ukbpW4LSqkb_CCt8LWfpehP03qqfyYfvK3Fl21NaEq8/edit?pli=1#heading=h.9q334hs4lbks). +- [ ] OPTIONAL: If you would like to manage content updates by running code locally rather than through GitHub, follow the steps in the [dev onboarding ticket](https://github.com/cisagov/getgov/issues/new?assignees=loganmeetsworld&labels=dev%2C+onboarding&template=developer-onboarding.md&title=Developer+Onboarding%3A+GH_HANDLE). + - [ ] If you would like to run code locally on a CISA laptop, reference the "Setting up a developer environment on CISA laptops" section of the onboarding doc. ### Access From 8302fe1ae1e7704729fd0247ed03e9e37fa4d462 Mon Sep 17 00:00:00 2001 From: Kristina Yin <140533113+kristinacyin@users.noreply.github.com> Date: Wed, 10 Apr 2024 23:58:14 -0700 Subject: [PATCH 11/15] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f457e7e69..12efb2a31 100644 --- a/README.md +++ b/README.md @@ -4,7 +4,7 @@ The .gov domain helps U.S.-based government organizations gain public trust by b ## Onboarding -For new members of the @cisagov/dotgov team looking to contribute to the registrar, please open an [onboarding ticket](https://github.com/cisagov/getgov/issues/new?assignees=loganmeetsworld&labels=dev%2C+onboarding&template=developer-onboarding.md&title=Developer+Onboarding%3A+GH_HANDLE). +For new members of the @cisagov/dotgov team looking to contribute to the registrar, please open an [dev onboarding ticket](https://github.com/cisagov/getgov/issues/new?assignees=loganmeetsworld&labels=dev%2C+onboarding&template=developer-onboarding.md&title=Developer+Onboarding%3A+GH_HANDLE) or [designer onboarding ticket](https://github.com/cisagov/getgov/issues/new?assignees=loganmeetsworld&labels=design%2C+onboarding&template=designer-onboarding.md&title=Designer+Onboarding%3A+GH_HANDLE). ## Code From f954f3fcf30587e270ad7c3030fba62f4881738c Mon Sep 17 00:00:00 2001 From: Kristina Yin <140533113+kristinacyin@users.noreply.github.com> Date: Wed, 10 Apr 2024 23:59:00 -0700 Subject: [PATCH 12/15] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 12efb2a31..545b64f99 100644 --- a/README.md +++ b/README.md @@ -4,7 +4,7 @@ The .gov domain helps U.S.-based government organizations gain public trust by b ## Onboarding -For new members of the @cisagov/dotgov team looking to contribute to the registrar, please open an [dev onboarding ticket](https://github.com/cisagov/getgov/issues/new?assignees=loganmeetsworld&labels=dev%2C+onboarding&template=developer-onboarding.md&title=Developer+Onboarding%3A+GH_HANDLE) or [designer onboarding ticket](https://github.com/cisagov/getgov/issues/new?assignees=loganmeetsworld&labels=design%2C+onboarding&template=designer-onboarding.md&title=Designer+Onboarding%3A+GH_HANDLE). +For new members of the @cisagov/dotgov team looking to contribute to the registrar, please open a [dev onboarding ticket](https://github.com/cisagov/getgov/issues/new?assignees=loganmeetsworld&labels=dev%2C+onboarding&template=developer-onboarding.md&title=Developer+Onboarding%3A+GH_HANDLE) or a [designer onboarding ticket](https://github.com/cisagov/getgov/issues/new?assignees=loganmeetsworld&labels=design%2C+onboarding&template=designer-onboarding.md&title=Designer+Onboarding%3A+GH_HANDLE). ## Code From c0f83f7696a1057a71fa284b34b081a1c751e47d Mon Sep 17 00:00:00 2001 From: Kristina Yin <140533113+kristinacyin@users.noreply.github.com> Date: Thu, 11 Apr 2024 08:18:55 -0700 Subject: [PATCH 13/15] Update README.md Co-authored-by: Alysia Broddrick <109625347+abroddrick@users.noreply.github.com> --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 545b64f99..4fa110464 100644 --- a/README.md +++ b/README.md @@ -4,7 +4,7 @@ The .gov domain helps U.S.-based government organizations gain public trust by b ## Onboarding -For new members of the @cisagov/dotgov team looking to contribute to the registrar, please open a [dev onboarding ticket](https://github.com/cisagov/getgov/issues/new?assignees=loganmeetsworld&labels=dev%2C+onboarding&template=developer-onboarding.md&title=Developer+Onboarding%3A+GH_HANDLE) or a [designer onboarding ticket](https://github.com/cisagov/getgov/issues/new?assignees=loganmeetsworld&labels=design%2C+onboarding&template=designer-onboarding.md&title=Designer+Onboarding%3A+GH_HANDLE). +For new members of the @cisagov/dotgov team looking to contribute to the registrar, please open a [developer onboarding ticket](https://github.com/cisagov/getgov/issues/new?assignees=loganmeetsworld&labels=dev%2C+onboarding&template=developer-onboarding.md&title=Developer+Onboarding%3A+GH_HANDLE) or a [designer onboarding ticket](https://github.com/cisagov/getgov/issues/new?assignees=loganmeetsworld&labels=design%2C+onboarding&template=designer-onboarding.md&title=Designer+Onboarding%3A+GH_HANDLE). ## Code From 217604d753931b737e8ecfc863bf63b6138fcf4c Mon Sep 17 00:00:00 2001 From: Kristina Yin <140533113+kristinacyin@users.noreply.github.com> Date: Thu, 11 Apr 2024 09:10:53 -0700 Subject: [PATCH 14/15] Update designer-onboarding.md --- .github/ISSUE_TEMPLATE/designer-onboarding.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/designer-onboarding.md b/.github/ISSUE_TEMPLATE/designer-onboarding.md index 0921728ae..2a620a1f0 100644 --- a/.github/ISSUE_TEMPLATE/designer-onboarding.md +++ b/.github/ISSUE_TEMPLATE/designer-onboarding.md @@ -37,7 +37,7 @@ Welcome to the .gov team! We're excited to have you here. Please follow the step - [ ] FOR CONTRACTORS: Check with your manager on your EOD clearance process. - [ ] OPTIONAL: Request access to our [analytics tools](https://docs.google.com/document/d/1ukbpW4LSqkb_CCt8LWfpehP03qqfyYfvK3Fl21NaEq8/edit?pli=1#heading=h.9q334hs4lbks). - [ ] OPTIONAL: If you would like to manage content updates by running code locally rather than through GitHub, follow the steps in the [dev onboarding ticket](https://github.com/cisagov/getgov/issues/new?assignees=loganmeetsworld&labels=dev%2C+onboarding&template=developer-onboarding.md&title=Developer+Onboarding%3A+GH_HANDLE). - - [ ] If you would like to run code locally on a CISA laptop, reference the "Setting up a developer environment on CISA laptops" section of the onboarding doc. + - [ ] If you would like to run code locally on a CISA laptop, reference the "[Setting up a developer environment on CISA laptops](https://docs.google.com/document/d/1ukbpW4LSqkb_CCt8LWfpehP03qqfyYfvK3Fl21NaEq8/edit#heading=h.2ctyba51d1zp)" section of the onboarding doc. ### Access From 0792d68608dffcb1f230f14f130fd29abd08a24c Mon Sep 17 00:00:00 2001 From: Kristina Yin <140533113+kristinacyin@users.noreply.github.com> Date: Thu, 11 Apr 2024 09:20:06 -0700 Subject: [PATCH 15/15] Update designer-onboarding.md --- .github/ISSUE_TEMPLATE/designer-onboarding.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/designer-onboarding.md b/.github/ISSUE_TEMPLATE/designer-onboarding.md index 2a620a1f0..0296b653d 100644 --- a/.github/ISSUE_TEMPLATE/designer-onboarding.md +++ b/.github/ISSUE_TEMPLATE/designer-onboarding.md @@ -26,7 +26,7 @@ Welcome to the .gov team! We're excited to have you here. Please follow the step - [ ] FOR FEDERAL EMPLOYEES: Create a [Google workspace enterprise account](https://docs.google.com/document/d/1ukbpW4LSqkb_CCt8LWfpehP03qqfyYfvK3Fl21NaEq8/edit?pli=1#heading=h.xowzg9w0qlis) for CISA. - [ ] 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. +- [ ] Make sure you have been invited to our [team meetings](https://docs.google.com/document/d/1ukbpW4LSqkb_CCt8LWfpehP03qqfyYfvK3Fl21NaEq8/edit#heading=h.emgtp2hgvabr) on Google Meet. - [ ] Review our [design tools](https://docs.google.com/document/d/1ukbpW4LSqkb_CCt8LWfpehP03qqfyYfvK3Fl21NaEq8/edit?pli=1#heading=h.aprurp3z4gmv). - [ ] Accept invitation to our [Figma workspace](https://www.figma.com/files/1287135731043703282/team/1299882813146449644). - [ ] Follow the steps in [preparing for your sandbox](https://docs.google.com/document/d/1ukbpW4LSqkb_CCt8LWfpehP03qqfyYfvK3Fl21NaEq8/edit?pli=1#heading=h.au66hq5e0l8s) section on the onboarding doc. @@ -54,7 +54,7 @@ By following the steps, you should have access / been added to the following: ### Steps for the onboarder - [ ] Make sure onboardee is given an invitation to our Slack workspace - [ ] Add onboardee to dotgov Slack channels -- [ ] Add onboardee is added to Project Folder as a "Contributor" (or if you do not have permissions, confirm with Cameron) +- [ ] Add onboardee to Project Folder as a "Contributor" (or if you do not have permissions, confirm with Cameron) - If onboardee if a federal employee, add them as a "Content Manager" instead - [ ] Once onboardee has been granted a Figma license, add them as an editor to the Figma team workspace, Otherwise, you can add them as a viewer in the meantime. - [ ] Add onboardee to our team meetings