Skip to content

Fix Name Inconsistency in tech-work-experience.md file #8574

Description

@kdaca19xx

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 update the Languages/Technologies/Tools information so that visitors to the website can find projects that use specific languages, technologies, or tools.

Action Items

  • In your IDE, open the _projects/tech-work-experience.md file.
  • Observe the existing syntax of the front matter block 1 in the file.
  • Find the tools variable and replace the following text .
    from
    Google Data Studio
    
    to
    Looker Studio
    
  • Verify the changes by viewing the following in your local environment with Docker, and include 'after' screenshots with your pull request (see the before images below to understand what we are looking for in the after images):
    • Projects page with filter 2
    • Tech Work Experience page 3

Resources/Instructions

Before Screenshot from Projects page with filter: Google Data Studio

Filter URL: https://www.hackforla.org/?tools=Google+Data+Studio

Image
Before Screenshot from Tech Work Experience page Image

Footnotes

  1. Info about the front matter block ↩

  2. post completion search results should show Tech Work Experience when you use this filter https://localhost:4000/projects/?tools=Looker+Studio ↩

  3. Project detailed info page URL: https://localhost:4000/projects/tech-work-experience ↩

Activity

  1. added
    role: front endTasks for front end developers
    ready for dev leadIssues that tech leads or merge team members need to follow up on
    size: 0.5ptCan be done in 3 hours or less
    DraftIssue is still in the process of being created
    p-feature: Projects-checkWe use this page to check to make sure that teams are using the Technology section correctly
    on Mar 26, 2026
  2. locchung commented on Mar 26, 2026

    @locchung
  3. added 2 commits that reference this issue on Mar 26, 2026
    b9b408d
    eee6587
  4. kdaca19xx commented on Mar 26, 2026

    @kdaca19xx
    Author
  5. removed
    ready for dev leadIssues that tech leads or merge team members need to follow up on
    on Mar 31, 2026
  6. 1 remaining item

  7. moved this from New Issue Approval to Ready for Prioritization in P: HfLA Website: Project Boardon Mar 31, 2026
  8. added
    DraftIssue is still in the process of being created
    and removed on May 14, 2026
  9. moved this from Ready for Prioritization to New Issue Approval in P: HfLA Website: Project Boardon May 14, 2026
  10. added
    ready for merge teamneeds a senior review either to do some re writing or to approve it for ready for prioritization
    on May 19, 2026
  11. self-assigned this
    on May 19, 2026
  12. HackforLABot commented on May 19, 2026

    @HackforLABot
    Contributor

    Hi @emoore36, thank you for taking up this issue! Hfla appreciates you :)

    Do let fellow developers know about your:-
    i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?)
    ii. ETA: (When do you expect this issue to be completed?)

    You're awesome!

    P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

  13. moved this from New Issue Approval to In progress (actively working) in P: HfLA Website: Project Boardon May 19, 2026
  14. emoore36 commented on May 19, 2026

    @emoore36
    Member

    i. Week's Availability: Flexible
    ii. ETA: Today

  15. removed
    DraftIssue is still in the process of being created
    on May 19, 2026
  16. t-will-gillis commented on May 24, 2026

    @t-will-gillis
    Member

    Hi @emoore36

    • This issue was in the "New Issue Approval" column, which means that it still needed a final review (this is also why the issue had Draft and ready for merge team labels).
    • For future reference, only work on issues in the "Prioritized backlog" column, or if you are at the part of your Skills Issue where you need to create issues, in the "ERs and epics that are ready to be turned into issues" column.
  17. moved this from In progress (actively working) to QA in P: HfLA Website: Project Boardon May 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

good first issueGood for newcomersp-feature: Projects-checkWe use this page to check to make sure that teams are using the Technology section correctlyready for merge teamneeds a senior review either to do some re writing or to approve it for ready for prioritizationrole: back end/devOpsTasks for back-end developersrole: front endTasks for front end developerssize: 0.5ptCan be done in 3 hours or less

Type

No type

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions