Correctly Classify Tools and Technologies Used In Projects

[kirandhamotharan]

Overview

We need to correctly classify tools and technologies used in projects so users/volunteers have clarity on what systems are being used.

Details

• Move Figma from Technologies to Tools on the following projects where it's listed as Technology
• Google Analytics → Web analytics platform, should be Technology
• Hotjar → Analytics/heatmap platform, should be Technology
• SPSS → Statistical software, should be Technology
• Mplus → Statistical modeling software, should be Technology
• AtlasTI → Qualitative analysis software, should be Technology
• Storybook → UI component development tool, should be Technology
• Style Components → React CSS-in-JS library, should be Technology (and fix spelling)
• pnpm → Package manager, should be Technology
• Observable → Data visualization platform, should be Technology
• Google Data Studio → BI tool, should be Technology
• Google Colab → Jupyter notebook platform, should be Technology

Action Items

• Create a template for changing item from Technology to Tools on a single project.md file
• Create issue for each project file that needs to be changed (a project file might have multiple changes)

Resources/Instructions

• 1.01 Issue that produced these changes Review project data to determine reclassifying requirements for their Technologies and Tools. #4262 (comment)
• 1.02 where you can check the project and filters https://www.hackforla.org/projects-check/

[github-actions]

Hi @kirandhamotharan.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:

• Size

NOTE: Please ignore this comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards.
To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels