hackforla / hackforla/website

Epic: Update project profile - Move from tools to technologies in projects

Open
#8,750 1 comment 0 reactions 0 assignees View on GitHub
Complexity: Small Dependency epic Feature: Accessibility Issue Making: Level 1 non-PR contribution P-Feature: Projects page p-feature: Projects-check role: back end/devOps size: 1pt
Dominant language
JavaScript
Stars
363
Forks
872
Avg merge
2d 21h
Merged PRs (30d)
18

Description

### Prerequisites
- 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.
- 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 correctly classify tools and technologies used in projects so users/volunteers have clarity on what systems are being used.

### Action Items
- [ ] Create issues to move the following items from tools to technologies for these projects using [this template](https://github.com/hackforla/website/issues/new?template=project-tool-to-technology.md):
- [ ] Food Oasis:
- Google Analytics
- SPSS
- Mplus
- [ ] Engage:
- Hotjar
- Google Analytics
- [ ] Lucky parking:
- Storybook
- pnpm
- Google Colab
- [ ] 311 Data:
- Observable
- [ ] Railstats LA:
- Observable
- [ ] Tech work experience:
- Looker Studio
- [ ] Hack for LA Site
- Google Analytics
- [ ] For each issue, make sure to fill in the project-specific information in the placeholders:
- [Insert filename] - e.g. 'website.md'
- [Insert current line(s) of code in tools] - this will be the tools for the project listed above
- [Insert desired line(s) of code in technologies] - this will be the same list of tools from above since we are just moving them
- [Insert name of project] - e.g. 'HackforLA Website'
- [Insert project-specific page URL here] - e.g. 'https://www.hackforla.org/projects/website'
- [ ] For each issue, add this issue as the parent under 'Relationships'
- [ ] When all the issues have been created, move this issue to 'Questions/In Review' on the project board and add the 'ready for merge team' label

### Resources/Instructions

1.01. Issue that produced these changes https://github.com/hackforla/website/issues/4262#issuecomment-3850007965
1.02. Where you can check the project and filters https://www.hackforla.org/projects-check/
1.03. Template to move from tool to tech: [Template](https://github.com/hackforla/website/issues/new?template=project-tool-to-technology.md)

Contributor guide

Open the contributing guide

Research direction

Start with the project-specific pages and tools entries, then use the project-tool-to-technology issue template and review the project filters page. Create one child issue for each listed project item, filling in the filename, current and desired lines, project name, and page URL. Done means all child issues link back to this issue and the parent is moved to Questions/In Review with the ready for merge team label.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, jekyll
Domain
content
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.