Skip to content

Update Project Profile: Hackforla.org Website Add Jose Santiago #8760

Closed as not planned

Description

@yielderdev

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 page and attend an onboarding session.
  2. 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.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

Footnotes

  1. Info about the front matter block ↩

  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 ↩

Activity

  1. added
    role: front endTasks for front end developers
    P-Feature: Project Info and PageA project's detail page (e.g. https://www.hackforla.org/projects/100-automations)
    time sensitiveNeeds to be worked on by a particular timeframe
    size: 0.25ptCan be done in 0.5 to 1.5 hours
    on Aug 29, 2026
  2. added
    ready for merge teamneeds a senior review either to do some re writing or to approve it for ready for prioritization
    on Aug 29, 2026
  3. added and removed
    ready for merge teamneeds a senior review either to do some re writing or to approve it for ready for prioritization
    on Aug 31, 2026
  4. moved this from New Issue Approval to Ready for Prioritization in P: HfLA Website: Project Boardon Aug 31, 2026
  5. moved this from Ready for Prioritization to Prioritized backlog in P: HfLA Website: Project Boardon Sep 7, 2026
  6. daras-cu commented on Nov 14, 2026

    @daras-cu
    Member

    Closing as no longer needed

  7. HackforLABot commented on Nov 14, 2026

    @HackforLABot
    Contributor

    This issue was reopened because it did not have any of the following:

    • A linked PR,
    • An Ignore label
    • A non-PR contribution label
  8. moved this from QA to Questions / In Review in P: HfLA Website: Project Boardon Nov 14, 2026
  9. moved this from Questions / In Review to New Issue Approval in P: HfLA Website: Project Boardon Nov 14, 2026
  10. added
    non-PR contributionFor wiki additions/revisions, audit spreadsheet contributions, issue-making ERs and Epics, etc.
    on Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P-Feature: Project Info and PageA project's detail page (e.g. https://www.hackforla.org/projects/100-automations)good first issueGood for newcomersnon-PR contributionFor wiki additions/revisions, audit spreadsheet contributions, issue-making ERs and Epics, etc.ready for productrole: back end/devOpsTasks for back-end developersrole: front endTasks for front end developerssize: 0.25ptCan be done in 0.5 to 1.5 hourstime sensitiveNeeds to be worked on by a particular timeframe

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions