Update Project Profile: Hackforla.org Website Add Jose Santiago
- 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 add the following profile after other member(s) with the same role.[^2]
```
- name: Jose Santiago
github-handle: santi-jose
role: Merge Team
links:
slack: https://hackforla.slack.com/team/U091RQ37UBC
github: https://github.com/santi-jose
picture: https://avatars.githubusercontent.com/santi-jose
```
- [ ] Verify the changes by viewing the following in your local environment with Docker, and include 'before' and 'after' screenshots with your pull request:
- [ ] Hackforla.org Website page [^3]
### Resources/Instructions
[^1]: [Info about the front matter block](https://jekyllrb.com/docs/front-matter/)
[^2]: Note: The typical order of roles should be: 'role: Owner' --> 'role: Manager' --> 'role: Lead' --> 'role: Merge Team' --> 'role: Researcher/Designer/Developer/Engineer'. If the intended order is not clear, ask the person who submitted the original request.
[^3]: Project detailed info page URL: [https://www.hackforla.org/projects/website](https://www.hackforla.org/projects/website)
Contributor guide
Research direction
Open _projects/website.md and inspect the existing front matter and leadership entries, especially nearby Merge Team members. Add Jose Santiago's provided profile in the appropriate role order, then use the local Docker environment to view the website project page. Done means the profile appears correctly and the pull request includes before-and-after screenshots.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, jekyll
- Domain
- content, web-dev
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 90/100