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

Self-Onboarding Content: [GISELLE DIZON] #1658

Closed
31 tasks done
giselledizon opened this issue Dec 13, 2024 · 2 comments
Closed
31 tasks done

Self-Onboarding Content: [GISELLE DIZON] #1658

giselledizon opened this issue Dec 13, 2024 · 2 comments
Assignees
Labels
feature: onboard / offboard onboarding & offboarding issue level I: request Smallest type of issue; Typically can be completed by one person priority: medium role: UX content writing size: 1pt can be done in 6 hours or less Status: Update Requested

Comments

@giselledizon
Copy link
Member

giselledizon commented Dec 13, 2024

Overview

Hello and welcome to the UX Writing/Content Design team at Expunge Assist!

This is to help introduce new team members to all important documents, work processes, and other information that will help them orient and get started at EA.
This onboarding process is here to help familiarize you with the project and begin to work with GitHub. Take your time as you work through each step and don't hesitate to comment with questions and tag/slack @SamHyler and/or @emmathrash (content co-leads). You can also find and message members in the EA slack channel

Set Up This New Issue

  • At the top of the issue, under "add a title" replace [NAME] with your name
  • Assign yourself to this issue using the gear in the sidebar on the right
  • Under Labels, replace role: missing label with role: content
  • Under Projects, add issue to Expunge Assist Project Tracking using the gear in the sidebar
  • Under Milestones add issue to Team Workflow using the gear in the sidebar
  • Submit this issue and then find it on the Project Board and move into the In Progress (active) column

Slack

Add yourself to the following slack channels

Project Resources

Read through and bookmark the following:

Your workspaces:

  • Github project board
  • Figjam board for collaboration between Content and Design. There is also a Figjam board for UXR, and one for PMs/planning.
    EA has access to 3 collaborative Figjam boards, the main Figma, Slack, and Google Drive. We don't use Miro, Notion, or other tools. Please use these boards only (and not your personal boards, for example), so that all work is saved for future EA volunteers! If we need additional resources, raise it at a meeting and with the leads/PMs so that it can be discussed and created through EA resources if deemed a necessary new tool.
  • Figma

Specific Figma pages

  • Read "Start Here" page on Figma. Read the Team Workflow "Practical steps to getting the work done" on the Start Here page. This is a general guide to how we collaborate between crossfunctional teams and take an issue through to completion.
  • Familiarize with Figma - master pages "desktop" and "mobile" we are working in responsive web, no app. These are the source of truth sections
  • Familiarize with Work in Progress pages. This is where we work and collaborate between Design and Content.
  • Familiarize with the Design hand off space to Dev, this happens at the end of an issue
  • There is a Figma Archive with work prior to 2024. This is because the free version ran out of storage space. This is a resource to see previous design decisions.

General resources:

Content specific resources:

Meetings

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. It's important to note to practice the following:

  • Most of our issues are 1pt (1pt should = 1 week of work), but do occasionally get higher than that. Start small and work your way up. We discuss upcoming issues during Content meetings, you can express interest for any issue during the meetings
  • 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

Resources/Notes

#819 - Content PM onboarding issue

@giselledizon giselledizon added priority: medium role: missing size: 1pt can be done in 6 hours or less feature: onboard / offboard onboarding & offboarding issue level I: request Smallest type of issue; Typically can be completed by one person labels Dec 13, 2024
@giselledizon giselledizon self-assigned this Dec 13, 2024
Copy link

Hey @giselledizon! Thanks for taking this issue.

To help keep everyone in the loop, please comment your Estimated Time to Completion (ETC) below!

Thanks again!

@github-project-automation github-project-automation bot moved this to New Issues for approval in P: EA: Project Board Dec 13, 2024
@giselledizon giselledizon added this to the 06. Team Workflow milestone Dec 13, 2024
@giselledizon giselledizon moved this from New Issues for approval to In Progress (active) in P: EA: Project Board Dec 13, 2024
Copy link

Hey @giselledizon! Thanks again for taking this issue.

Time for an update! Please comment the following update:
**Progress:** What's the status of the project? What have you done and what still needs to be done?
**Estimated Time to Completion (ETC):** When do you estimate to be finished?
**Blockers:** Anything preventing you from finishing?

Thanks again!

@github-project-automation github-project-automation bot moved this from In Progress (active) to Done in P: EA: Project Board Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature: onboard / offboard onboarding & offboarding issue level I: request Smallest type of issue; Typically can be completed by one person priority: medium role: UX content writing size: 1pt can be done in 6 hours or less Status: Update Requested
Projects
Development

No branches or pull requests

1 participant