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

Edit Accomplishments in About Page to show different years #4188

Closed
10 tasks done
Tracked by #4146
jdingeman opened this issue Mar 15, 2023 · 18 comments · Fixed by Thinking-Panda/website#1 or #5932
Closed
10 tasks done
Tracked by #4146

Edit Accomplishments in About Page to show different years #4188

jdingeman opened this issue Mar 15, 2023 · 18 comments · Fixed by Thinking-Panda/website#1 or #5932
Assignees
Labels
Complexity: Large P-Feature: About Us https://www.hackforla.org/about/ P-Feature: Program Area https://www.hackforla.org/program-areas role: front end Tasks for front end developers size: 5pt Can be done in 19-30 hours
Milestone

Comments

@jdingeman
Copy link
Member

jdingeman commented Mar 15, 2023

Overview

We want to highlight the accomplishments across HackforLA for the projects across multiple years. Currently, the About page only shows accomplishments for the year 2022. We need to implement a new format so that a user can see highlights from previous years.

Action Items

  • We need to add three fields to _data/internal/accomplishments.yml
    • year
    • project-file (example: project-file: food-oasis.md)
    • program-area (example: program-area: Social Safety Net)
  • If a project file exists, the program area should be retrieved from the project file, by using Liquid to run through the _projects collection and find the program area that matches with the name of the project. Therefore, program-area should be specified only if no project file exists.
  • See most recent Figma design (in resources below) and zoom into the Accomplishments section
  • Navigate to _includes/about-page/about-card-accomplishments.html
  • Implement the design so that when a user clicks on any of the years, the section shows accomplishments from that year
  • Note: The final layout for the Accomplishments section will slightly differ from the Figma design
    • Rather than list accomplishments by project with the program area above as seen in current design (see below),
      we want to list the accomplishments by program area. So the program area (e.g. Citizen Engagement) would be like the black header, and the accomplishments for each project in that program area will be listed. This is so the program areas do not get repeated for each project in that program area.

Resources/Instructions

Current design

Future State of website after this issue is completed

image from future state of website figma

Web View

Mobile View

@jdingeman jdingeman added role: front end Tasks for front end developers Complexity: Large P-Feature: About Us https://www.hackforla.org/about/ ready for dev lead Issues that tech leads or merge team members need to follow up on size: 5pt Can be done in 19-30 hours Draft Issue is still in the process of being created labels Mar 15, 2023
@ExperimentsInHonesty ExperimentsInHonesty added this to the 05. Know HFLA milestone Mar 16, 2023
@ExperimentsInHonesty ExperimentsInHonesty added the P-Feature: Program Area https://www.hackforla.org/program-areas label Mar 27, 2023
@jdingeman jdingeman added ready for product and removed Draft Issue is still in the process of being created ready for dev lead Issues that tech leads or merge team members need to follow up on labels Apr 7, 2023
@jdingeman

This comment was marked as outdated.

@ExperimentsInHonesty

This comment was marked as outdated.

@ExperimentsInHonesty ExperimentsInHonesty added ready for dev lead Issues that tech leads or merge team members need to follow up on and removed ready for product labels Apr 12, 2023
@ExperimentsInHonesty

This comment was marked as outdated.

@github-actions

This comment was marked as outdated.

@roslynwythe roslynwythe added ready for product and removed ready for dev lead Issues that tech leads or merge team members need to follow up on labels Aug 16, 2023
@roslynwythe

This comment was marked as outdated.

@ExperimentsInHonesty

This comment was marked as outdated.

@ExperimentsInHonesty ExperimentsInHonesty added ready for dev lead Issues that tech leads or merge team members need to follow up on and removed ready for product labels Aug 27, 2023
@Josiah-O

This comment was marked as resolved.

@roslynwythe

This comment was marked as resolved.

@roslynwythe roslynwythe added Ready for Prioritization and removed ready for dev lead Issues that tech leads or merge team members need to follow up on labels Aug 28, 2023
@ExperimentsInHonesty ExperimentsInHonesty added ready for dev lead Issues that tech leads or merge team members need to follow up on and removed Ready for Prioritization labels Sep 24, 2023
@roslynwythe roslynwythe added Ready for Prioritization and removed ready for dev lead Issues that tech leads or merge team members need to follow up on labels Oct 15, 2023
@Thinking-Panda Thinking-Panda self-assigned this Oct 17, 2023
@github-actions
Copy link

Hi @Thinking-Panda, 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 :)

@Thinking-Panda
Copy link
Member

Availability: Weekdays
ETA: 10/31/23

@Thinking-Panda
Copy link
Member

Questions

  1. The issue says the current highlights are for year 2022. The published website says the highlights are for the yea 2020. And, the Figma design shows 2019 as the earliest year. Please let me know how far back in years should I include ?
  2. The current code is designed to have 4 accomplishments in each column. Should I continue with that layout or plan for situations when there could be more than 8 accomplishments per year. For example, when there are 9 accomplishments, should the left column have 5 or 4 accomplishments?

Thank you !

@github-actions github-actions bot added the To Update ! No update has been provided label Nov 3, 2023

This comment was marked as resolved.

@Thinking-Panda
Copy link
Member

Thinking-Panda commented Nov 3, 2023

  1. Progress: Added more years to display accomplishments, added code to display the program areas as mentioned for all accomplishments. Working on filtering accomplishments by year and displaying the program area accordingly without repeating code.
  2. Blockers: none at the moment
  3. Availability: Weekdays
  4. ETA:11/10

@ExperimentsInHonesty ExperimentsInHonesty added Status: Updated No blockers and update is ready for review and removed To Update ! No update has been provided ready for product labels Nov 8, 2023
@ExperimentsInHonesty
Copy link
Member

@Thinking-Panda I removed the To Update ! and ready for product labels, now that you have done your update. Thanks for working on this. I am looking forward to seeing it when its done.

@github-actions github-actions bot removed the Status: Updated No blockers and update is ready for review label Nov 10, 2023
@Thinking-Panda
Copy link
Member

  1. The Figma design has "All" included in the dropdown in mobile viewport. But the desktop viewport does not include it. Should I add "All" to show all accomplishments?
  2. The list of years to be displayed is added dynamically. But I notice that it is displayed twice and I'm unable to fix the problem. I am also attaching the console message I get when I tried to track it.
    AccYearConsoleMsg

@LRenDO
Copy link
Member

LRenDO commented Nov 16, 2023

Hi @Thinking-Panda!

Great observation on the difference between the desktop and mobile options. I would think that question would be good for the design team, but it looks like there is no one on the website design team currently from what I can see on GitHub. I would lean towards sticking with the Figma design since we can always create a new issue to add an "All" section, but tagging in @roslynwythe for guidance on whether or not to go ahead and add it now.

I am happy to take a look at what you have for the second issue that you are running into and/or get on Slack to work it out with you. If you push your feature to your forked repo, sometime early next week I can take a look at what you've got.

@LRenDO
Copy link
Member

LRenDO commented Nov 21, 2023

Hi @Thinking-Panda! I was able to take a look at your branch and overall it's looking good so far!

As far as the blocker, It looks like about.js is included in both \pages\about.html and \_includes\about-page\about-card-accomplishments.html. This is likely why there is duplication in the accomplishments section. Only including the script once should resolve the issue. If not, this SO article might be helpful and includes a couple other potential causes/solutions.

Aside from the blocker, I thought I would also mention that the for loops in loadAccomplishmentYears() are missing let in front of i=year.

Again, looks like you're off to a solid start here! Please feel free to ping me here or on Slack if you need any additional help resolving the issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Large P-Feature: About Us https://www.hackforla.org/about/ P-Feature: Program Area https://www.hackforla.org/program-areas role: front end Tasks for front end developers size: 5pt Can be done in 19-30 hours
Projects
6 participants