Update the Web Developer wiki page

[JessicaLucindaCheng]

Overview

As a developer, I want the Web Developer wiki page to be up to date and an informative resource for developers interested in joining our team and for current developers on the team. For this issue, we will update the Web Developer wiki page.

Action Items

• We are currently in the process of moving the old wiki to the new website-wiki repo, so we will not be making any changes or additions to the old wiki at this time. Thus, we will be adding wiki content through a different process now. Read How to Contribute to the Wiki
• For an example of a good role-based wiki page, see UI UX Researcher wiki page
• Take a look at what is in the developer pre-work checklist. Is there anything on the pre-work checklist that could be useful on the Web Developer wiki page?
• Take a look at the files in our Wiki. Is there anything there that would be good to link to on the Web Developer wiki pages?
• Update the Web Developer wiki page
  • Include information about issue progression: All developers should progress from two good first issues to small to medium and then another medium or large issue. Afterward, a developer can pick any medium or large size issue to work on.

Resources/Instructions

• Web Developer wiki page
• Developer pre-work checklist
• Wiki
• For an example of a good role-based wiki page, see UI UX Researcher wiki page

[Providence-o]

@Providence-o @ExperimentsInHonesty Can you please take a look at the Web Developer wiki page and give us feedback?

Notes:

• Under 'progress through issues' bullet point, all the size issues listed should be itemized (with bullet points)
• The 'Getting started' section should show the exact steps they need to take to join the team
• The wiki page should provide an overview of the devs lifecycle: from creating a good first issue to becoming a lead

[JessicaLucindaCheng]

• Progress: Currently, 50% progress because I realized adding a FigJam diagram could take a while to do so I had overestimated how much I had completed before. Also, I figured out what diagram style I might want to use by illustrating it like a main quest (working on issues) and required and non-required side quests (writing issues, reviewing prs, etc).
• Blockers: None
• Availability: TBD
• ETA: TBD

To Do

• Remove anything that is repeated in the Getting Started section that is already in the pre-work.
• Move resources to a different Wiki page and link back to the Web Developer page.
• See if anything in About the Website Development Team is duplicated elsewhere and can be removed, not needed, or should be placed somewhere else.
• Add the developer life cycle for the team Junior, either Merge Team, and Technical Lead OR join another team
  • Using FigJam to diagram it
  • Use this structure: Analysis: Collecting Data on Issue Completion per Prework Author and Creating Looker Dashboards to Uncover Insights #4152 (comment)
• Update any references to pre-works to be called, "Team member activity support issue" as mentioned in HfLA: Dev/PM Agenda and Notes #2607 (comment)
• See if this should be added

We require all developers on the Website Team to go through a prework checklist. You'll need to start a prework issue by going to https://github.com/hackforla/website/issues/new?assignees=&labels=Feature%3A+Onboarding%2FContributing.md%2C+prework%2C+size%3A+1pt&template=pre-work-template--dev.md&title=Pre-work+Checklist%3A+Developer%3A+%5Breplace+brackets+with+your+name%5D
In the title, remove [replace brackets with your name] and then put your name there
Then, click the Submit new issue button
Then, you can start doing the items on the checklist

• From Update about-the-website-development-team.md website-wiki#11

  • Info for Meetings section, and "Wait until your pull request is merged before working on another issue." could probably be moved to the Web Developer wiki page.
    • Though, a better option might be to link to the info in section 2.1 Hack for LA in CONTRIBUTING.md in the Web Developer wiki page because the meetings and the info about prs are already in section 2.1.

[HackforLABot]

@JessicaLucindaCheng

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Monday, November 25, 2024 at 11:04 PM PST.}