Create a copy of the project page with only two filters: technology and language

[macho-catt]

trafficstars

Dependency

• ~#2488~

Overview

We need a copy of the project page with only the technology and language filter to ensure that the page filters properly

Action Items

• [x] Create a new page based off of the current project page
  • [x] The new page's permalink should be set to /projects-check/
  • [x] The page should only be reachable via permalink
• [x] For the newly created page, update the dropdown filters so there are only two: technologies filter and language filters
  • [x] The technologies filter should filter based on a specific technology
  • [x] The languages filter should filter based on a specific language
  • [x] You may use the ideas of the current existing code: current-projects.js
• [ ] Ensure the new page works, and it should not affect any existing pages on the website

Resources/Instructions

• projects page
• current-projects.js

[github-actions[bot]]

Hi @macho-catt.

Good job adding the required labels for this issue. The merge team will review the issue and add a "Ready for Milestone" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to read and interpret labels

[maybleMyers]

Progress: stuck Blockers: having a hard time understanding assets/js/current-projects.js. I have never used the jekyll/liquid before. Availability: 10 hours/week ETA: not sure

[github-actions[bot]]

@Benji-Montgomery

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures: "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Tuesday, March 29, 2022 at 12:20 AM PST.}

[SAUMILDHANKAR]

@Benji-Montgomery Just wanted to follow up regarding your blocker. Please let us know if you have made progress or need help. Thanks.

[github-actions[bot]]

@Benji-Montgomery

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures: "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Tuesday, April 5, 2022 at 12:20 AM PST.}

[SAUMILDHANKAR]

@Benji-Montgomery Just wanted to share some of the resources on Jekyll/liquid you might find helpful:

• https://github.com/hackforla/website/wiki/Hack-for-LA's-Site-Architecture
• https://jekyllrb.com/docs/liquid/
• https://jekyllrb.com/docs/step-by-step/01-setup/
• https://shopify.github.io/liquid/tags/control-flow/

You can also post your blocker on our slack channel or add help wanted label on this issue if you need help on something specific. Thank you.

[JessicaLucindaCheng]

@jnmrles

• [ ] At the time you self-assign an issue, make sure to write in a comment the following:
• Availability: "How much time will you have this week to work on this issue?"
• ETA: "When do you expect this issue to be completed?"
• [x] Also, please move this to the In Progress column. Edit: I moved this to In Progress because I think this got missed during our checks since it wasn't in the In Progress column.

[github-actions[bot]]

@jnmrles

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures: "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Tuesday, June 7, 2022 at 12:21 AM PST.}

[github-actions[bot]]

@jnmrles

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures: "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Tuesday, June 14, 2022 at 12:19 AM PST.}

[Sparky-code]

@macho-catt Checking in to see if you are still working on this issue or if your availability has changed. Please add your ETA and availability. Thanks!

[github-actions[bot]]

@jnmrles

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Tuesday, June 21, 2022 at 12:20 AM PST.}

[github-actions[bot]]

@jnmrles

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Tuesday, June 28, 2022 at 12:21 AM PST.}

[ExperimentsInHonesty]

@jnmrles We have not heard from you since you self assigned this issue. We are putting it back into the prioritized backlog

[github-actions[bot]]

Hi @Wny-Duong, 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 :)

[Wny-Duong]

Availability: (07/14-07/17): 4 hours, (07/18-07/22): 6 hours ETA: 07/22, Friday.

[github-actions[bot]]

@Wny-Duong

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Tuesday, July 19, 2022 at 12:21 AM PST.}

[Wny-Duong]

Progress: Created projects-check.html file and page with current-projects-check.html and current-projects-check.js files based off of dependencies of the original projects pages. The createFilter function was also reworked to return only a technologies and languages filter based off of the original combined technologies filter, which are visible and can be "used."

Blockers: The languages filter does not work properly (doesn't get a count of the project languages and doesn't filter by the language) and I'm still trying to figure out why and how to fix that. But that should be the only obstacle remaining.

Availability: 6 hours (7/25 - 7/29)

ETA: 7/29/22

Pictures:

[ExperimentsInHonesty]

@Wny-Duong don't forget to remove the 2week inactive label when you do your update. Thanks!

[github-actions[bot]]

@Wny-Duong

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Tuesday, August 2, 2022 at 12:20 AM PST.}

[Wny-Duong]

Progress: Progress has been much slower than I'd like it to be because of personal issues. However, this issue is very close to finished. The Languages and Technologies filter now both work properly. They can be used to filter project cards on the projects-check page and they maintain the frequency of the filter tags in the filter bar themselves, as seen in the images below.

The long delay in delivery has also been a result of needing to read through and trace back the code to deal with the problem of url parameters only working when language parameters treated as technologies parameters. This was fixed by editing the projectCardComponent() function to create a data-languages property to allow for filtering by that data-languages parameter through the url. Languages were previously combined with technologies in the data-technologies property of the project-card class in projectCardComponent().

Blockers: None! Just checking to make sure these changes don't impact other pages on the website.

Availability: 4 hours (8/5 - 8/7)

ETA: 8/7/22

Pictures: