-
-
Notifications
You must be signed in to change notification settings - Fork 778
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
Comments
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
Hi @Thinking-Panda, thank you for taking up this issue! Hfla appreciates you :) Do let fellow developers know about your:- You're awesome! P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :) |
Availability: Weekdays |
Questions
Thank you ! |
This comment was marked as resolved.
This comment was marked as resolved.
|
@Thinking-Panda I removed the |
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. |
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 Aside from the blocker, I thought I would also mention that the for loops in 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! |
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
year
project-file
(example:project-file: food-oasis.md
)program-area
(example:program-area: Social Safety Net
)program-area
should be specified only if no project file exists.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
About page, accomplishment section: https://www.hackforla.org/about/#accomplishments
image from current state of website figma
Future State of website after this issue is completed
image from future state of website figma
Web View
Mobile View
The text was updated successfully, but these errors were encountered: