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

About Page: Allowing users to see highlights from each year in the Accomplishments Section #3035

Closed
8 tasks done
phuonguvan opened this issue Apr 7, 2022 · 50 comments
Closed
8 tasks done
Assignees
Labels
Complexity: Medium Discussion Starting point for gathering further information and/or feedback P-Feature: About Us https://www.hackforla.org/about/ role: design size: 5pt Can be done in 19-30 hours
Milestone

Comments

@phuonguvan
Copy link
Member

phuonguvan commented Apr 7, 2022

Overview

We need to have visitors who see the accomplishments in the about page, be able to understand the full breadth of what we have accomplished over the last two years, while not making the section so huge that no one looks at it.

Details

  • It should be broken up by year
  • There should also be a way for product to be able to add the orgs achievements without having to send it back to design for reformatting each year

Action Items

  • Interview Product to understand why we think we need all the previous accomplishments
  • Brainstorm ideas for designs
  • Review ideas with the design lead
  • Design low-fi prototypes of the section in mobile and desktop views
  • Review low-fi designs with the design and product lead
  • Design hi-fi prototypes of the section
  • Review hi-fi designs with the design lead
  • Review the final designs with the design lead

Resources/Instructions

Current page layouts

Accomplishments Section

Figma files

@github-actions

This comment was marked as outdated.

@ExperimentsInHonesty ExperimentsInHonesty added this to the 05. Know HFLA milestone Apr 7, 2022
@ExperimentsInHonesty ExperimentsInHonesty added time sensitive Needs to be worked on by a particular timeframe and removed Ready for Prioritization labels Apr 7, 2022
@sijiapitts

This comment was marked as outdated.

@ExperimentsInHonesty ExperimentsInHonesty added the size: 5pt Can be done in 19-30 hours label May 11, 2022
@github-actions github-actions bot added the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label May 20, 2022
@github-actions

This comment was marked as outdated.

@sijiapitts

This comment was marked as outdated.

@github-actions github-actions bot added Status: Updated No blockers and update is ready for review and removed 2 weeks inactive An issue that has not been updated by an assignee for two weeks Status: Updated No blockers and update is ready for review labels May 27, 2022
@github-actions

This comment was marked as off-topic.

@github-actions github-actions bot added the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Jun 3, 2022
@sijiapitts
Copy link
Member

  1. Progress: Confirmed the final design for web and mobile. What's left: Check the margins. Design screens for 2019 and 2020 accomplishment
  2. Blockers: No blockers
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: By the next meeting

@sijiapitts
Copy link
Member

  1. Progress: Completed the final design for web and mobile except for a few blockers.
  2. Blockers: - Missing 2019 accomplishments. - Missing program area for two projects (indicated on the figma file). - Heading is inconsistent (H4 on web, but H5 on mobile)

Solved Blockers: Font size on the dropdown menu is 14.4px. I have confirmed with Phu and changed them to 16px.

@github-actions github-actions bot added Status: Updated No blockers and update is ready for review and removed 2 weeks inactive An issue that has not been updated by an assignee for two weeks labels Jun 10, 2022
@sijiapitts
Copy link
Member

  1. Progress: Reviewed and confirmed the final design for web. Next step: Will do an audit on all the drop down menus (mobile view), then create an consistent drop down menu design.
  2. Blockers: Waiting for copies for: 2019 accomplishment National Day of Civic Hacking (NdoCH)
  3. Availability: 5 hours
  4. ETA: By the next meeting

@sijiapitts
Copy link
Member

sijiapitts commented Jun 21, 2022

  • Working on ticket #3277

@github-actions github-actions bot added 2 weeks inactive An issue that has not been updated by an assignee for two weeks and removed Status: Updated No blockers and update is ready for review labels Jul 1, 2022
@github-actions

This comment was marked as outdated.

@github-actions

This comment was marked as outdated.

@sijiapitts
Copy link
Member

@ExperimentsInHonesty Hope you had a great holiday break too Bonnie.

I reviewed everything and have updated the program areas.

But we are still missing one thing: I noticed we don't have the copies for 2019 National Day of Civic Hacking (NdoCH). All the copies on this file are for 2021 and 2020 projects. In 2019, we have two projects: National Day of Civic Hacking (NdoCH) and Slack Redactor. I found the copies for the Slack Redactor project on this design file , but it seems like copies for the 2019 NdoCH is missing.

@github-actions github-actions bot added Status: Updated No blockers and update is ready for review and removed 2 weeks inactive An issue that has not been updated by an assignee for two weeks labels Jan 13, 2023
@github-actions github-actions bot added 2 weeks inactive An issue that has not been updated by an assignee for two weeks and removed Status: Updated No blockers and update is ready for review labels Jan 20, 2023
@github-actions
Copy link

@sijiapitts

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 Monday, January 16, 2023 at 11:16 PM PST.

@sijiapitts
Copy link
Member

  1. Progress: Design completed. Waiting for the missing content.
  2. Blockers: No blockers. Justing waiting for the content.
  3. ETA: After the missing content is provided, the project can be completed within 1 day.

@ExperimentsInHonesty
Copy link
Member

National Day of Civic Hacking (NdoCH)
In 9/2019 Hack for LA joined Code for America brigades to work on Justice issues. During this day long event, we developed a Journey map of the record clearance process which led to the launch of the Hack for LA Record Clearance project, now called Expunge Assist.

@sijiapitts
Copy link
Member

Completed. Ready for development. The final design can be found here

@sijiapitts sijiapitts added Ready for Prioritization ready for product and removed 2 weeks inactive An issue that has not been updated by an assignee for two weeks labels Jan 24, 2023
@ExperimentsInHonesty
Copy link
Member

@sijiapitts It looks amazing! Thanks.

We will make a dev issue to build it.

@ExperimentsInHonesty ExperimentsInHonesty added Discussion Starting point for gathering further information and/or feedback ready for dev lead Issues that tech leads or merge team members need to follow up on and removed Ready for Prioritization labels Feb 13, 2023
@jdingeman
Copy link
Member

jdingeman commented Feb 19, 2023

I think it would look best to keep highlights grouped by program area rather than having each project listed with it's program area subheader. I think it'll give a cleaner look and naturally more categorical. I think this would also emphasize that there are multiple highlights per program area, rather than 1 highlight per project.

@blulady
Copy link
Member

blulady commented Mar 3, 2023

Just wondering how the yearly wins will be selected for display...

@ExperimentsInHonesty
Copy link
Member

We will be sorting by program area for display

@ExperimentsInHonesty ExperimentsInHonesty added P-Feature: About Us https://www.hackforla.org/about/ and removed P-Feature: Projects page https://www.hackforla.org/projects/ labels Mar 21, 2023
@ExperimentsInHonesty
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Medium Discussion Starting point for gathering further information and/or feedback P-Feature: About Us https://www.hackforla.org/about/ role: design size: 5pt Can be done in 19-30 hours
Projects
Development

No branches or pull requests

5 participants