Update Project Profile: Hackforla.org Website Remove Ryan Keller
@MStoutTech is already working on this.
Since Sep 17, 2026.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 90/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- jekyll
- Domain
- content
Research direction
Open _projects/website.md and inspect the leadership variable and its front matter syntax. Remove the Ryan Keller entry, then run the site locally and view the Hackforla.org Website project page. Done means the entry is absent and the pull request includes before-and-after screenshots.
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: Ryan Keller
github-handle: ryanfkeller
role: Merge Team
links:
slack: https://hackforla.slack.com/team/U08SCL4KK3N
github: https://github.com/ryanfkeller
picture: https://avatars.githubusercontent.com/ryanfkeller
- 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
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
apache/cloudstack#14222 ·
-
Browser Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
getsentry/sentry-javascript#24577 · 1 comment ·
-
curation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
amponce/archive-movie-browser#186 ·
-
light
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
aemdemos/patients-stryker#253 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
clerk/javascript#9852 ·