Repository navigation
Epic: Fix Name Inconsistencies in the Tools Filter #8497
Description
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)
- Add this dependency (Identify What Style Components Is #8495) on the home-unite-us.md project file issue
Resources/Instructions
- 1.01 https://www.hackforla.org/projects-check
- 1.02 https://www.hackforla.org/projects
- 1.03 Instructions for using the projects check page: Create documentation for projects-check page #3487 (comment)
- 1.04
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]
Metadata
Metadata
Assignees
Labels
Take this type of issues after the successful merge of your second good first issueGood for newcomersWe use this page to check to make sure that teams are using the Technology section correctlyIssues that tech leads or merge team members need to follow up onTasks for front end developersCan be done in 3 hours or less
Activity
github-actions commentedon Feb 3, 2026
[-]ER: Fix Name Inconsistencies in the Tools Filter[/-][+]Epic: Fix Name Inconsistencies in the Tools Filter[/+]15 remaining items
daras-cu commentedon Mar 31, 2026
@kdaca19xx I made one note on the VRMS issue, the rest of them look good. Thanks for working on this!
kdaca19xx commentedon Apr 26, 2026
Hi @daras-cu ,
I changed the status to
Ready for Prioritization. Is this correct?