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.

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

Code new Issue template for UI/UX Designer onboarding #1188

Closed
3 tasks done
Tracked by #1205
anitadesigns opened this issue Mar 7, 2024 · 3 comments · Fixed by #1300
Closed
3 tasks done
Tracked by #1205

Code new Issue template for UI/UX Designer onboarding #1188

anitadesigns opened this issue Mar 7, 2024 · 3 comments · Fixed by #1300
Assignees
Labels
feature: GitHub/Project Board maintenance feature: onboard / offboard onboarding & offboarding issue level I: request Smallest type of issue; Typically can be completed by one person priority: high role: development anything related to code size: 1pt can be done in 6 hours or less

Comments

@anitadesigns
Copy link
Member

anitadesigns commented Mar 7, 2024

Dependency

Overview

Currently, the PMs use #543 to onboard new designers, but the Design team noticed some gaps in which we would like to expand. Instead of using one general issue to document and track a Designer's onboarding journey, the Design team would like an issue template developed so that new UI/UX Designers and Leads can track onboarding progress. Once all action items are completed, the ui/ux designer will close the issue and begin working on an issue for the current milestone.

Action Items

Resources/Notes

See desired template in comments
linked to #1205

@anitadesigns anitadesigns added role: development anything related to code priority: high draft Not yet ready to be worked on size: 1pt can be done in 6 hours or less feature: GitHub/Project Board maintenance feature: onboard / offboard onboarding & offboarding ready for dev lead task ready for dev lead to evaluate issue level I: request Smallest type of issue; Typically can be completed by one person labels Mar 7, 2024
@anitadesigns anitadesigns added this to the Team Workflow milestone Mar 7, 2024
@sydneywalcoff sydneywalcoff removed their assignment Mar 7, 2024
@sydneywalcoff sydneywalcoff added dependency The issue or reason why this issue is in the icebox and removed draft Not yet ready to be worked on ready for dev lead task ready for dev lead to evaluate labels Mar 7, 2024
@sydneywalcoff sydneywalcoff changed the title Develop Issue template for UI/UX Designer onboarding Code new Issue template for UI/UX Designer onboarding Mar 8, 2024
@anitadesigns
Copy link
Member Author

anitadesigns commented Mar 12, 2024

Overview

To help you jump into the team and make Expunge Assist even better, this onboarding issue shares tips for using team resources. As a new UX/UI Designer at Expunge Assist, fill in the fields below as you tackle each onboarding task. Below is the table of content and areas of focus:

Focus Area Description
Set-up Take actionable steps to make sure you have everything set-up to begin contributing to the project.
Project Familiarization Review background documentation to learn about EA and where the project is going.
GitHub 101 Using GitHub tends to be a learning curve for UX Designers. Learn about GitHub and how our team uses it.
Your first issue Learn how to take your first Github issue and team best practices.
Team Resources A list of team resources that would be helpful to bookmark

Tip: Take your time ✨

Navigating through a lot of information can be overwhelming at first, but it's perfectly natural. Don't hesitate to ask questions whenever you need clarification. Embrace the journey of learning as you progress. Take your time with your onboarding tasks; there's no rush to be at full speed right away!

Questions?

If you have questions, don't hesitate to mention @jyehllow or @anitadesigns (Design Co-leads), @vanessaavviles (Product Design Manager) You can also reach out to team members in the #expunge-asssit-design-and-content Slack channel.

Set-up

Action Items

  • Set up this GitHub Issue

    • At the top of this Issue, under ' Add a title', replace "[NAME]" with your name
    • Assign yourself to this issue using the gear in the right sidebar
    • Under Labels, replace role: missing label with role: design
    • Under Projects, add issue to Expunge Assist Project Tracking using the gear in the sidebar
    • move to In Progress (active) column
    • Under Milestones move to Team Workflow using the gear in the sidebar
  • Add yourself to the Slack channels

    • #expunge-assist
    • #expunge-assist-design-content
    • #expunge-assist-research-team
    • #expunge-assist-dev
  • Introduce yourself on #expunge-assist Slack channel

    • Include name, role in the team, where you're from, and what brings you to EA.
  • Ensure you have edit access to tools

    • Add yourself to the Google Drive Team Roster
    • Reach out to the Design team leadership (lead or PM) to get Github, Drive, and Figma access
      • Check the Wiki Roster to find leadership
      • Slack is often the easiest way to contact them
    • Ensure you have edit access to Figma
      • Sign-up for a Figma account if you don't have one
    • Ensure you have edit access to Google Drive
    • Ensure you have edit access to GitHub
    • Ensure you have Google calendar invites to the following meetings:
      • Design meetings
      • Design/Content/ Research meetings
      • All-Team meetings

Project Familiarization

Action Items

GitHub 101

GitHub is a web-based and open-source platform used for version control and collaboration on software development projects. It provides tools for developers to host and review code, manage projects, and build software together. Although Developers are mostly known to use GitHub, Hack for LA and our team use GitHub for project management and documentation.

Action Items

Your first issue

Now that you are familiar with our project and learned a bit about using our tools, it's time to work on your first Issue. I

t's important to note to practice the following:

  • Most of our issues are 1pt, but do occasionally get higher than that. Start small and work your way up
  • Frequently add updates to all issues you are assigned to or providing input to
    • updates are required once a week and should use the following format:
1. Progress
2. Blockers
3. Availability
4. ETA
  • Make sure to check off 'Action Items' as they are completed
  • Make sure to close issues as you finish them

Action Items

  • Go to our Project Board
  • Look under "Prioritized Backlog" on Project Board
  • Filter board using 'good first issue' label
    • Talk to Design lead or PM if there are no design issues with that label
  • Assign yourself to issue
  • Move issue to "In Progress" column on Project Board

Team Resources

Stuff You Should Bookmark

@anitadesigns
Copy link
Member Author

Attached the desired template content for "Designer Pre-work" template to the comment above. Since we are onboarding a designer today, I created an issue #1256 which the designer will be assigned to, and did not want to rush Dev to create the template. Aiming to use the template once it's developed/added

@anitadesigns anitadesigns added ready for dev lead task ready for dev lead to evaluate and removed dependency The issue or reason why this issue is in the icebox labels Mar 12, 2024
@sydneywalcoff sydneywalcoff removed the ready for dev lead task ready for dev lead to evaluate label Mar 17, 2024
@sydneywalcoff
Copy link
Member

@anitadesigns adding this to the backlog, but wanted to let you know I added the instruction to add the issue to the team workflow milestone. That's something I missed in my first iteration and now have to fix lol

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature: GitHub/Project Board maintenance feature: onboard / offboard onboarding & offboarding issue level I: request Smallest type of issue; Typically can be completed by one person priority: high role: development anything related to code size: 1pt can be done in 6 hours or less
Projects
Development

Successfully merging a pull request may close this issue.

3 participants