Skip to content

Epic: Fix Name Inconsistencies in the Tools Filter #8497

Closed
4 of 5 issues completed
Closed
Epic: Fix Name Inconsistencies in the Tools Filter#8497
4 of 5 issues completed
Assignees
kdaca19xx
Labels
Complexity: SmallTake this type of issues after the successful merge of your second good first issueepicgood first issueGood for newcomersp-feature: Projects-checkWe use this page to check to make sure that teams are using the Technology section correctlyready for dev leadIssues that tech leads or merge team members need to follow up onrole: front endTasks for front end developerssize: 0.5ptCan be done in 3 hours or less
Milestone
03.02 Onboarding flow

Description

@nadiaspn0503
nadiaspn0503
opened on Feb 3, 2026

Overview

We need to fix the name inconsistencies of the tools in the tools filter to ensure all information is up to date and correct.

Details

While doing an annual check on technology/tools/languages we found the following inconsistencies, which will need to be fixed.

  • "AtlasTI" should be "ATLAS.ti"
  • MongoDB Atlas should be MongoDB
  • "Google Data Studio" should be "Looker Studio"
  • "ArcGIS surveys" should be "ArcGIS Survey123"
  • "Style Components" is likely supposed to be "Styled Components"

Action Items

  • Identify which projects use the above tools by using filters for tool name (resource 1.01)
  • Create issues to update each project.md file using the template (resource 1.04)

Resources/Instructions

Issue template 
### 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 update tool information so that visitors to the website can find projects that use specific tools.

### Action Items
- [ ] In your IDE, open the `_projects/[Insert filename].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   
   ```
   [REPLACE WITH CURRENT TEXT (E.G., `  - Style Components`)
   ```
   to
   ```
   [REPLACE WITH FUTURE TEXT (E.G., `  - Styled Components`)
   ```
- [ ] Verify the changes by viewing the following in your local environment with Docker, and include 'before' and 'after' screenshots with your pull request:
  - [ ] [Insert name of project] page [^2]

### Resources/Instructions
[^1]: [Info about the front matter block](https://jekyllrb.com/docs/front-matter/)
[^2]: Project detailed info page URL: [Insert project specific page URL here]

Activity

  1. nadiaspn0503
    added
    size: missing
    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
    Complexity: Missing
    role missingA specific role label needs to be applied to the issue
    on Feb 3, 2026
  2. github-project-automation
    added this to P: HfLA Website: Project Boardon Feb 3, 2026
  3. github-project-automation
    moved this to New Issue Approval in P: HfLA Website: Project Boardon Feb 3, 2026

  4. github-actions commented on Feb 3, 2026

    @github-actions
    github-actionsbot
    on Feb 3, 2026 – with GitHub Actions · Hidden as resolved
  5. nadiaspn0503
    added
    role: front endTasks for front end developers
    Complexity: SmallTake this type of issues after the successful merge of your second good first issue
    size: 0.5ptCan be done in 3 hours or less
    and removed
    size: missing
    Complexity: Missing
    role missingA specific role label needs to be applied to the issue
    on Feb 3, 2026
  6. ExperimentsInHonesty
    changed the title [-]ER: Fix Name Inconsistencies in the Tools Filter[/-] [+]Epic: Fix Name Inconsistencies in the Tools Filter[/+] on Feb 4, 2026

  7. 15 remaining items

  8. kdaca19xx
    added a sub-issue on Mar 26, 2026

  9. daras-cu commented on Mar 31, 2026

    @daras-cu
    daras-cu
    on Mar 31, 2026
    Member

    @kdaca19xx I made one note on the VRMS issue, the rest of them look good. Thanks for working on this!

  10. kdaca19xx
    moved this from ERs and epics that are ready to be turned into issues to New Issue Approval in P: HfLA Website: Project Boardon Apr 26, 2026
  11. kdaca19xx
    added
    ready for dev leadIssues that tech leads or merge team members need to follow up on
    on Apr 26, 2026
  12. kdaca19xx
    moved this from New Issue Approval to Ready for Prioritization in P: HfLA Website: Project Boardon Apr 26, 2026

  13. kdaca19xx commented on Apr 26, 2026

    @kdaca19xx
    kdaca19xx
    on Apr 26, 2026
    Member

    Hi @daras-cu ,

    I changed the status to Ready for Prioritization. Is this correct?

  14. ExperimentsInHonesty
    added
    Complexity: Missing
    Complexity: SmallTake this type of issues after the successful merge of your second good first issue
    epic
    and removed
    ready for dev leadIssues that tech leads or merge team members need to follow up on
    on Apr 28, 2026
  15. ExperimentsInHonesty
    moved this from Ready for Prioritization to Questions / In Review in P: HfLA Website: Project Boardon Apr 28, 2026
  16. ExperimentsInHonesty
    added
    ready for dev leadIssues that tech leads or merge team members need to follow up on
    on Apr 28, 2026
  17. ExperimentsInHonesty
    removed
    Complexity: Missing
    on Jun 9, 2026
  18. daras-cu
    closed this as completedon Jun 29, 2026
  19. github-project-automation
    moved this from Questions / In Review to QA in P: HfLA Website: Project Boardon Jun 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Complexity: SmallTake this type of issues after the successful merge of your second good first issueepicgood first issueGood for newcomersp-feature: Projects-checkWe use this page to check to make sure that teams are using the Technology section correctlyready for dev leadIssues that tech leads or merge team members need to follow up onrole: front endTasks for front end developerssize: 0.5ptCan be done in 3 hours or less

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions