Fix Name Inconsistency in food-oasis.md file
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
Research direction
Open _projects/food-oasis.md and inspect its front matter, especially the tools and technologies lists. Start the local Docker site and verify the Projects filter at /projects/?technologies=ATLAS.ti and the Food Oasis page at /projects/food-oasis; done means the renamed technology appears consistently and the requested after screenshots are included.
Written by the indexing model from the issue text.
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 page and attend an onboarding session.
- You have already read our How to Contribute to Hack for LA Guide.
Overview
We need to update the Languages/Technologies/Tools information so that visitors to the website can find projects that use specific languages, technologies, or tools.
Action Items
- In your IDE, open the
_projects/food-oasis.mdfile. - Observe the existing syntax of the front matter block [^1] in the file.
- Find the
toolsvariable and remove the following text:- AtlasTI - Find the
technologiesvariable. Add the following text at the bottom of the current list, after 'Material-UI':- ATLAS.ti - Verify the changes by viewing the following in your local environment with Docker, and include 'after' screenshots with your pull request (see the before images below to understand what we are looking for in the after images):
- Projects page with filter [^2]
- Food Oasis page [^3]
Resources/Instructions
Before Screenshot from Projects page with filter: AtlasTI
Filter URL: https://www.hackforla.org/?tools=AtlasTI
Before Screenshot from Food Oasis page
[^1]: Info about the front matter block
[^2]: post completion search results should show Food Oasis when you use this filter https://localhost:4000/projects/?technologies=ATLAS.ti
[^3]: Project detailed info page URL: https://localhost:4000/projects/food-oasis
- Dominant language
- JavaScript
- Stars
- 364
- Forks
- 872
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 13
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from hackforla/website
-
Complexity: Small P-Feature: Projects page Ready for Prioritization role: back end/devOps role: front end size: 0.25pt
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 2 days
-
Complexity: See issue making label epic good first issue Issue Making: Level 1 non-PR contribution P-Feature: Project Info and Page role: back end/devOps role: front end size: 0.25pt time sensitive
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
hackforla/website#8806 · 1 comment ·
Maintainers usually reply within 2 days
-
Complexity: Small Feature: Infrastructure Ready for Prioritization role: back end/devOps size: 0.25pt
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 2 days
-
Complexity: Small Feature: Infrastructure Ready for Prioritization role: back end/devOps size: 0.25pt
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
Maintainers usually reply within 2 days
-
Complexity: Small ER Issue Making: Level 1 non-PR contribution P-Feature: Projects page role: back end/devOps size: 0.25pt
Difficulty 1/5 Under an hour Newbie friendliness 88/100
hackforla/website#8803 · 6 comments · 1 assignee ·
Maintainers usually reply within 2 days
All issues in hackforla/website
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
TheOdinProject/curriculum#31444 ·
Maintainers usually reply within 1 day
-
software-development-practices software-development-practices:nist-ssdf
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
githubnext/gh-aw-cao#15860 ·
Maintainers usually reply within 1 day
-
framework/gatsby help wanted kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
Maintainers usually reply within 2 days
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
PedestrianDynamics/pyFDS-Evac#476 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
aiko-chan-ai/DiscordBotClient#380 ·