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

Create new issues to refactor Tools data in project md files #4777

Closed
30 tasks done
Tracked by #4960
t-will-gillis opened this issue Jun 3, 2023 · 2 comments
Closed
30 tasks done
Tracked by #4960

Create new issues to refactor Tools data in project md files #4777

t-will-gillis opened this issue Jun 3, 2023 · 2 comments
Assignees
Labels
Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Dependency An issue is blocking the completion or starting of another issue epic Feature: Refactor JS / Liquid Page is working fine - JS / Liquid needs changes to become consistent with other pages good first issue Good for newcomers Issue Making: Level 1 Make issues from a template and a spreadsheet ready for dev lead Issues that tech leads or merge team members need to follow up on role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 1pt Can be done in 4-6 hours

Comments

@t-will-gillis
Copy link
Member

t-will-gillis commented Jun 3, 2023

Dependency

Overview

As part of the sequence of steps to revise the filters to include a dropdown menu for Tools (issue #4427), once the above dependencies are released, we need to create new issues for editing each of the following project .md files in the _projects folder: when the above dependencies are released, move each issue below from the "Ice Box" to "New Issue Approval", remove the Dependency label and add Ready for prioritization label.

Action Items

  • For each of the above issues, click on the target icon that appears to the far right when hovering on the line to "Convert to issue".
  • Edit the issue title by prepending Refactor Tools data for in front of current issue title. For example:
    • if the new issue created is called access-the-data.md then
    • the new issue title will be Refactor Tools data for access-the-data.md
  • Add the labels role: front end, role: back end/devOps, good first issue, size: 0.5pt, P-Feature: Project Info and Page, P-Feature: Projects page, p-feature: Projects-check
  • Add to the Projects Board in the "Ice Box"
  • Add the milestone 03.02 Onboarding flow <<Confirm
  • Use the template below in the body of the new issue. Be sure to replace "PROJECT_NAME" with the correct md file name, and replace "<SHOW_3_BACKTICKS>" with 3 backticks.
### Dependency

- [4777]

### Overview

We need to revise the filter dropdown menu on the [projects-check] page to include a dropdown for Tools, so that we can use this page to see where we might need to move projects values from tools to technologies, and vice versa. In order for the filter to work properly, we need to refactor the `tools` data in the .md file from a string to a list.

### Action Items

- [ ] Refer to the [PROJECT_NAME.md](https://github.com/hackforla/website/blob/gh-pages/_projects/PROJECT_NAME.md) file and find the entry for `tools:`
- [ ] Change the `tools` data from a string into a list: 

`tools: tool_1, tool_2, tool_3`  becomes:
<SHOW_3_BACKTICKS>
tools: 
  - tool_1
  - tool_2
  - tool_3
<SHOW_3_BACKTICKS>
- [ ]  

### Resources/Instructions

- [Homepage](https://www.hackforla.org)
- [Projects](https://www.hackforla.org/projects/) page
- This issue is part of an epic: #4777

For Merge Team/Tech Leads/PMs

Resources/Instructions

@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 Dependency An issue is blocking the completion or starting of another issue Feature: Refactor JS / Liquid Page is working fine - JS / Liquid needs changes to become consistent with other pages Complexity: Small Take this type of issues after the successful merge of your second good first issue size: 1pt Can be done in 4-6 hours Draft Issue is still in the process of being created Issue Making: Level 1 Make issues from a template and a spreadsheet epic labels Jun 3, 2023
@t-will-gillis t-will-gillis removed the Draft Issue is still in the process of being created label Jun 3, 2023
@github-actions
Copy link

Hi @t-will-gillis, 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 :)

@t-will-gillis
Copy link
Member Author

I have moved the dependencies for each of the issues that were created to #4427 because when the 18 issues above are completed, opening #4427 is the next step. Therefore, closing this issue as completed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Dependency An issue is blocking the completion or starting of another issue epic Feature: Refactor JS / Liquid Page is working fine - JS / Liquid needs changes to become consistent with other pages good first issue Good for newcomers Issue Making: Level 1 Make issues from a template and a spreadsheet ready for dev lead Issues that tech leads or merge team members need to follow up on role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 1pt Can be done in 4-6 hours
Projects
Development

No branches or pull requests

2 participants