Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move items from Tools to Technologies in hellogov.md #5340

Closed
4 tasks done
t-will-gillis opened this issue Aug 29, 2023 · 4 comments · Fixed by #5569
Closed
4 tasks done

Move items from Tools to Technologies in hellogov.md #5340

t-will-gillis opened this issue Aug 29, 2023 · 4 comments · Fixed by #5569
Assignees
Labels
good first issue Good for newcomers P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) P-Feature: Projects page https://www.hackforla.org/projects/ p-feature: Projects-check We use this page to check to make sure that teams are using the Technology section correctly role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.25pt Can be done in 0.5 to 1.5 hours

Comments

@t-will-gillis
Copy link
Member

t-will-gillis commented Aug 29, 2023

Prerequisite

  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 page.
  2. Please make sure you have read our Hack for LA Contributing Guide before you claim/start working on an issue.

Overview

For each Hack for LA project listed on our webpages, we need to ensure that the data entries for Tools, Technologies, etc. are appropriate for each category. On the HelloGOV project, there are some entries under Tools that should move to Technologies.

Action Items

  • Locate the HelloGOV markdown file in the website/_projects/ folder.
  • Locate the section tools: ... For this particular project, we want all of the "Tools" listed to be categorized as "Technologies" instead. Also, some of the entries need minor revisions as shown.
  • Therefore, replace:
tools:
  - Mongo
  - Angular
  - Node

with:

technologies:
  - MongoDB
  - Angular
  - Node.js
  • Provide before and after screenshots of the relevant web pages showing that the change was made successfully with no unintended effects. Also, confirm that the side filter displays the correct information.

Resources/Instructions

hellogov.md
Hello GOV project page
Hack for LA homepage
Projects page
This issue is initiated by ER #5268

@t-will-gillis t-will-gillis added good first issue Good for newcomers role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) Ready for Prioritization P-Feature: Projects page https://www.hackforla.org/projects/ size: 0.25pt Can be done in 0.5 to 1.5 hours p-feature: Projects-check We use this page to check to make sure that teams are using the Technology section correctly labels Aug 29, 2023
@t-will-gillis t-will-gillis added this to the 03.02 Onboarding flow milestone Aug 29, 2023
@t-will-gillis

This comment was marked as resolved.

@segbuniwe segbuniwe self-assigned this Sep 15, 2023
@github-actions
Copy link

Hi @segbuniwe, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:-
i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?)
ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

@segbuniwe
Copy link
Member

Availability for this week: I will be available for ~6-10 hours this week to work on this issue.
My estimated ETA for completing this issue: I plan to complete this issue one week from now, so by Friday, September 22nd, if not earlier.

@segbuniwe
Copy link
Member

How many hours did it take you to finish the pre-work up to and including adding your initial ETA and availability for your good first issue, including attending your first meetings?

It has taken me about ~6-7 hours to complete all the prework material and a good first issue. I have not yet been able to attend a meeting, but I hope to attend a Sunday meeting soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) P-Feature: Projects page https://www.hackforla.org/projects/ p-feature: Projects-check We use this page to check to make sure that teams are using the Technology section correctly role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.25pt Can be done in 0.5 to 1.5 hours
Projects
Development

Successfully merging a pull request may close this issue.

2 participants