Repository navigation
Fix Name Inconsistency in tech-work-experience.md file #8574
Copy link
Copy link
Closed
Labels
good first issueGood for newcomersGood for newcomersp-feature: Projects-checkWe use this page to check to make sure that teams are using the Technology section correctlyWe 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 prioritizationneeds a senior review either to do some re writing or to approve it for ready for prioritizationrole: back end/devOpsTasks for back-end developersTasks for back-end developersrole: front endTasks for front end developersTasks for front end developerssize: 0.5ptCan be done in 3 hours or lessCan be done in 3 hours or less
Milestone
Description
Activity
- addedgood first issueGood for newcomersGood for newcomersrole: front endTasks for front end developersTasks for front end developersready for dev leadIssues that tech leads or merge team members need to follow up onIssues that tech leads or merge team members need to follow up onsize: 0.5ptCan be done in 3 hours or lessCan be done in 3 hours or lessDraftIssue is still in the process of being createdIssue is still in the process of being createdp-feature: Projects-checkWe use this page to check to make sure that teams are using the Technology section correctlyWe use this page to check to make sure that teams are using the Technology section correctly
on Mar 26, 2026 - moved this to New Issue Approval in P: HfLA Website: Project Board
on Mar 26, 2026 - added a parent issue
on Mar 26, 2026 - added 2 commits that reference this issue
on Mar 26, 2026 kdaca19xx commented
on Mar 26, 2026 on Mar 26, 2026 · Hidden as resolvedAuthorshow commentMore actions- removedready for dev leadIssues that tech leads or merge team members need to follow up onIssues that tech leads or merge team members need to follow up on
on Mar 31, 2026 1 remaining item
- moved this from New Issue Approval to Ready for Prioritization in P: HfLA Website: Project Board
on Mar 31, 2026 - addedrole: back end/devOpsTasks for back-end developersTasks for back-end developers
on Mar 31, 2026 - addedDraftIssue is still in the process of being createdIssue is still in the process of being createdand removed
on May 14, 2026 - moved this from Ready for Prioritization to New Issue Approval in P: HfLA Website: Project Board
on May 14, 2026 - addedready for merge teamneeds a senior review either to do some re writing or to approve it for ready for prioritizationneeds a senior review either to do some re writing or to approve it for ready for prioritization
on May 19, 2026 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 :)
- moved this from New Issue Approval to In progress (actively working) in P: HfLA Website: Project Board
on May 19, 2026 i. Week's Availability: Flexible
ii. ETA: Today- removedDraftIssue is still in the process of being createdIssue is still in the process of being created
on May 19, 2026 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
Draftandready for merge teamlabels). - 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.
- 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
- moved this from In progress (actively working) to QA in P: HfLA Website: Project Board
on May 24, 2026
Metadata
Metadata
Assignees
Labels
good first issueGood for newcomersGood for newcomersp-feature: Projects-checkWe use this page to check to make sure that teams are using the Technology section correctlyWe 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 prioritizationneeds a senior review either to do some re writing or to approve it for ready for prioritizationrole: back end/devOpsTasks for back-end developersTasks for back-end developersrole: front endTasks for front end developersTasks for front end developerssize: 0.5ptCan be done in 3 hours or lessCan be done in 3 hours or less
Type
Projects
- StatusShow more project fieldsQA
Prerequisites
Overview
We need to update the
Languages/Technologies/Toolsinformation so that visitors to the website can find projects that use specific languages, technologies, or tools.Action Items
_projects/tech-work-experience.mdfile.toolsvariable and replace the following text .from
Resources/Instructions
Before Screenshot from Projects page with filter: Google Data Studio
Filter URL: https://www.hackforla.org/?tools=Google+Data+Studio
Before Screenshot from Tech Work Experience page
Footnotes
Info about the front matter block ↩
post completion search results should show Tech Work Experience when you use this filter https://localhost:4000/projects/?tools=Looker+Studio ↩
Project detailed info page URL: https://localhost:4000/projects/tech-work-experience ↩