Update Project Profile: HackforLA Website
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- jekyll, markdown
- Domain
- content
Research direction
Start with the Project Update Data in this issue and the linked add-new-leader template; the target project profile is website.md. Follow the template's checklist to create and relate the add-leader sub-issue, then record its URL here and verify all add/remove issue work is complete.
Written by the indexing model from the issue text.
Description
Prerequisite
- Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our Getting Started page and attend an onboarding session.
- Before you claim or start working on an issue, please make sure you have read our How to Contribute to Hack for LA Guide.
Overview
The Website project team needs its project leadership variable information updated, so that the current team members can be properly displayed on the Hack for LA website.
Action Items
- Review the Project Update Data below and then follow the instructions for either adding or deleting team members from the project's .md
Adding new volunteers to team page
- Create a new issue using the add new leader to project template
- Customize the title with name of project and person to add
- Customize the body
- In the ER, go to the value under the line "Project Card URL"
- Copy the file name
- On the line that starts "- [ ] In your IDE…" replace brackets with the copy (the text we are expecting is a file name with the extension .md)
- In the copy block below the line that starts, "Find the
leadershipvariable and add the following profile." add all the information from the ER for the person you are adding. - On the checkbox line below, "- [ ] Verify the changes by viewing..." replace with name of project
- to Resource 3, find the project on the https://www.hackforla.org/projects/ page
- click on its link
- copy link
- replace brackets on resource 3 with the URL
- In the ER, go to the value under the line "Project Card URL"
- Choose
Createbutton - Under Relationships, add this epic or ER as a parent to the issue you just created
- Add milestone
03.02 Onboarding flow - Review, and if ready, apply label
ready for merge team - At the bottom of this issue description, next to "Create sub-issue", click the drop-down menu arrow. Then, click "Add existing issue", search for the issue you just created, and select that issue to add as a sub-issue.
- Add the URL to a comment on this ER
- if this is the first add leader issue to be created, paste this into a comment and add the URL of the issue you just created.
### Adding Leader issues
-
### Complete
- [ ] Check this when all the Add leader issues have been made
- if the above comment already exists, just add your new issue URL to the list.
- Check off the box, if it's the last one that needed to be created.
Removing volunteers from team page
- Create a new issue using the remove leader from project template
- Customize the title with name of project and person to remove
- Customize the body
- In the epic, go to the value under the line "Project Card URL"
- Copy the file name
- On the line that starts "- [ ] In your IDE…" replace brackets with the copy (the text we are expecting is a file name with the extension .md)
- Go to https://github.com/hackforla/website/tree/gh-pages/_projects and find and click on the file
- click on code view
- copy the code block
- highlight the text on your new issue where it says
[Insert the lines of code to remove the specified leadership member]and delete it and replace with the copy block
- On the checkbox line below, "- [ ] Verify the changes by viewing..." replace with name of project
- to Resource 2, find the project on the https://www.hackforla.org/projects/ page
- click on its link
- copy link
- replace brackets on resource 2 with the URL
- In the epic, go to the value under the line "Project Card URL"
- Choose
Createbutton - Under Relationships, add this epic or ER as a parent to the issue you just created
- Add milestone
Onboarding flow - Review, and if ready, apply label
ready for merge team - At the bottom of this issue description, next to "Create sub-issue", click the drop-down menu arrow. Then, click "Add existing issue", search for the issue you just created, and select that issue to add as a sub-issue.
- Add the URL to a comment on this ER
- if this is the first remove leader issue to be created, paste this into a comment on this issue and add the URL of the issue you just created.
### Removing Leader issues
-
### Complete
- [ ] Check this when all the removal issues have been made
- if the above comment already exists, just add your new issue URL to the list.
- Check off the box, if it's the last one that needed to be created.
- When you have completed making all the add and remove issues
- move this issue into the Questions/Review column
- add the
ready for merge teamlabel
For Merge Team Members
- Check each sub-issue created for this ER/epic
- For each sub-issue that is ready, apply a
ready for prioritizationlabel
- For each sub-issue that is ready, apply a
- If all sub-issues have been created so that the request in this ER/epic has been fulfilled, apply a
ready for productlabel to this ER/epic
Project Update Data
Project Name
Hackforla.org Website
Project Card URL
website.md
Add person(s) and info to Leadership?
YES
If YES on add person(s), edit the below to provide the information required. If NO, delete the template in the field below:
Name: Michael Hughes
GitHub Handle: yielderdev
Role: Merge Team
Slack Member ID: U0BMZF5MQE9
Project Status
Active
- Dominant language
- JavaScript
- Stars
- 364
- Forks
- 873
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 8
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from hackforla/website
-
Complexity: Small P-Feature: Projects page ready for merge team role: back end/devOps role: front end size: 0.25pt
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Complexity: Small Feature: Board/GitHub Maintenance ready for merge team role: back end/devOps size: 0.25pt
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Complexity: Small Feature: Board/GitHub Maintenance ready for merge team role: back end/devOps size: 0.25pt
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Complexity: Small ER Issue Making: Level 2 P-Feature: Home page ready for merge team role: back end/devOps size: 0.25pt
Difficulty 1/5 Under an hour Newbie friendliness 88/100
hackforla/website#8803 · 1 comment ·
Maintainers usually reply within 1 day
-
good first issue new-win-submission P-Feature: Wins Page role: product size: missing
Difficulty 1/5 Under an hour Newbie friendliness 85/100
hackforla/website#8798 · 1 comment ·
Maintainers usually reply within 1 day
All issues in hackforla/website
Similar issues
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
amponce/archive-movie-browser#354 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
saayam-for-all/webapp#1870 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Imageomics/OpenCite#66 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
chr15m/twiiit.com#20 ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
antropos17/Aegis#629 ·
Maintainers usually reply within 4 days