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

Project Description Page: Add Problem, Solution, and Impact Section #3034

Closed
9 tasks done
phuonguvan opened this issue Apr 7, 2022 · 13 comments
Closed
9 tasks done
Assignees
Labels
Complexity: Medium P-Feature: Projects page https://www.hackforla.org/projects/ role: design size: 2pt Can be done in 7-12 hours
Milestone

Comments

@phuonguvan
Copy link
Member

phuonguvan commented Apr 7, 2022

Overview

We need to design an additional section on each individual project page that displays the Problem, Solution, and Impact & SDG info so that development can build the content into the site.

Details

The content design has already been created (sort of), on the Citizen Engagement page. But it may or may not fit onto the current width of the project page

Action Items

  • Review the Citizen Engagement project card display layout (Figma and online)
  • Review the Project Pages layout (Figma and online)
  • See if you can fit the card in between two of the existing cards. If it doesn't fit (the content is too wide, etc.), brainstorm ideas about how you might reformat the content on that card to work with the layout of the project page.
  • Review ideas with the design lead
  • Design low-fi prototypes of the section in mobile and desktop views
  • Decide if it goes before or after the resources section in the project description
  • 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

Resources/Instructions

Current page layouts

Where to find words to use in your mockup

Figma files

@phuonguvan phuonguvan added Complexity: Medium Dependency An issue is blocking the completion or starting of another issue role: design Ready for Prioritization P-Feature: Projects page https://www.hackforla.org/projects/ labels Apr 7, 2022
@github-actions
Copy link

github-actions bot commented Apr 7, 2022

Hi @phuonguvan.

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:

@ExperimentsInHonesty ExperimentsInHonesty added this to the 05. Know HFLA milestone Apr 7, 2022
@ExperimentsInHonesty ExperimentsInHonesty added size: 2pt Can be done in 7-12 hours and removed Ready for Prioritization Dependency An issue is blocking the completion or starting of another issue labels Apr 7, 2022
@gold-o
Copy link
Member

gold-o commented Apr 27, 2022

Availability for this week:

  1. Progress: I have brainstormed ideas for the issue and need to review them with the design lead
  2. Blockers: N/A
  3. Availability: 5 hours
  4. ETA: Second week of May

Images:

image

@ExperimentsInHonesty
Copy link
Member

@gold-o Phu and I reviewed your questions, and you can remove all of the items you suggested
✔️can remove picture
✔️make all text 16 pt
✔️don’t have to have the 311 title
✔️can lengthen card

@github-actions
Copy link

@gold-o

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, May 17, 2022 at 12:21 AM PST.

@github-actions
Copy link

@gold-o

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, May 24, 2022 at 12:21 AM PST.

@gold-o
Copy link
Member

gold-o commented May 29, 2022

Progress: I have completed the low-fi prototypes and the design lead and I had a voting session with the team to decide which prototype to develop into a hi-fi prototype. I am currently in the progess of developing the hi-fi prototype.
Blockers: I have to brainstorm ways to enlarge the SDG icon and fit it into the prototype in progress
Availability: 4-6 hours
ETA: By the 5th of June
Pictures:

Screen Shot 2022-05-29 at 11 44 25 AM

@github-actions github-actions bot added Status: Updated No blockers and update is ready for review and removed 2 weeks inactive labels Jun 3, 2022
@github-actions github-actions bot removed the Status: Updated No blockers and update is ready for review label Jun 10, 2022
@github-actions
Copy link

@gold-o

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
Copy link

@gold-o

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.

@gold-o gold-o added ready for dev lead Issues that tech leads or merge team members need to follow up on and removed 2 weeks inactive labels Jun 19, 2022
@gold-o
Copy link
Member

gold-o commented Jun 20, 2022

Progress: I have completed the hi-fi prototypes.
Blockers: N/A
Availability: N/A
ETA: This issue is completed (06/19)
Pictures:

Screen Shot 2022-06-20 at 12 37 28 AM

This is ready for development

@gold-o gold-o closed this as completed Jun 20, 2022
@kathrynsilvaconway
Copy link
Member

@ExperimentsInHonesty Am I writing an issue to update the project page to the most recent Figma design? Just checking because this one is ready for dev, but it doesn't have any explicit action for me to take.

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Sep 12, 2022

@kathrynsilvaconway Please make an issue for development to take the change to the project pages layout and make it into new code for the project pages. Do this in a new feature branch. Here is the page that they will edit https://github.com/hackforla/website/blob/gh-pages/_layouts/project.html

@blulady
Copy link
Member

blulady commented Oct 28, 2022

@blulady blulady 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 28, 2022
@bishrfaisal bishrfaisal added ready for dev lead Issues that tech leads or merge team members need to follow up on and removed Ready for Prioritization labels Oct 30, 2022
@ExperimentsInHonesty ExperimentsInHonesty removed the ready for dev lead Issues that tech leads or merge team members need to follow up on label Oct 30, 2022
@ExperimentsInHonesty
Copy link
Member

Moving back to done and archiving. It was in the new issue approval column because an issue had not been made, you just didn't see it until the day you mentioned it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Medium P-Feature: Projects page https://www.hackforla.org/projects/ role: design size: 2pt Can be done in 7-12 hours
Projects
Development

No branches or pull requests

6 participants