hackforla / hackforla/website

Update Project Profile: Hackforla.org Website Remove Santiago Vidal

Open Beginner friendly
#8,771 0 comments 0 reactions 0 assignees View on GitHub
good first issue P-Feature: Project Info and Page role: back end/devOps role: front end size: 0.25pt time sensitive
Dominant language
JavaScript
Stars
363
Forks
872
Avg merge
2d 21h
Merged PRs (30d)
18

Description

### Prerequisites
1. 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](https://www.hackforla.org/getting-started) page and attend an onboarding session.
2. You have already read our [How to Contribute to Hack for LA Guide](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md).

### 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.md` file.
- [ ] Observe the existing syntax of the front matter block [^1] in the file.
- [ ] Find the `leadership` variable and remove the following:
```
- name: Santiago Vidal
github-handle: santiseccovidal
role: Merge Team
links:
slack: https://hackforla.slack.com/team/U06MQ37T90E
github: https://github.com/santiseccovidal
picture: https://avatars.githubusercontent.com/santiseccovidal
```
- [ ] 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](https://jekyllrb.com/docs/front-matter/)
[^2]: Project detailed info page URL: https://www.hackforla.org/projects/website

Contributor guide

Open the contributing guide

Research direction

Open _projects/website.md and inspect its front matter, then find the leadership variable and remove Santiago Vidal's entry. Run the site locally and check the Hackforla.org Website project page. Done means the entry is absent and the pull request includes before-and-after screenshots of that page.

Written by the indexing model from the issue text.

Assessment

Tech stack
jekyll
Domain
content
Issue type
Documentation
Difficulty
1/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
92/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.