Update Project Profile: Hackforla.org Website Remove Xavier Neal-Carson
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 92/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- jekyll
- Domain
- content
Research direction
Open _projects/website.md and inspect its front matter, especially the leadership variable. Remove the Xavier Neal-Carson entry, then view the Hackforla.org Website project page in the local environment and include before-and-after screenshots in the pull request; done means the profile no longer lists Xavier Neal-Carson.
Written by the indexing model from the issue text.
Description
Prerequisites
- 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.
- You have already read our How to Contribute to Hack for LA Guide.
Overview
We need to keep project information up to date so that visitors to the website can find accurate information.
Action Items
- In your IDE, open the
_projects/website.mdfile. - Observe the existing syntax of the front matter block [^1] in the file.
- Find the
leadershipvariable and remove the following:
- name: Xavier Neal-Carson
github-handle: xnealcarson
role: Merge Team
links:
slack: https://hackforla.slack.com/team/U08GNFS09SL
github: https://github.com/xnealcarson
picture: https://avatars.githubusercontent.com/xnealcarson
- Verify the changes by viewing the following in your local environment and include before and after screenshots with your pull request:
- Hackforla.org Website page [^2]
Resources/Instructions
[^1]: Info about the front matter block
[^2]: Project detailed info page URL: https://www.hackforla.org/projects/website
- Dominant language
- JavaScript
- Stars
- 364
- Forks
- 873
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 12
Contributor guide
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 Feature: Infrastructure Ready for Prioritization role: back end/devOps role: front end size: 0.25pt
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Complexity: Small P-Feature: Project Info and Page ready for merge team role: front end size: 0.25pt
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
-
good first issue P-Feature: Project Info and Page Ready for Prioritization role: back end/devOps role: front end size: 0.25pt time sensitive
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Complexity: Medium Feature: Administrative ready for merge team role: back end/devOps role: front end size: 0.5pt
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Complexity: See issue making label ER Feature: Infrastructure Issue Making: Level 2 non-PR contribution ready for merge team role: back end/devOps role: front end size: 0.25pt
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
All issues in hackforla/website
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·