website icon indicating copy to clipboard operation
website copied to clipboard
verified publisher icon hackforla

Initiative: homepage launch

Open ExperimentsInHonesty opened this issue 4 years ago • 100 comments

Overview

We need to track and support the final wrap up items for the homepage launch, so that it can be completed.

Details

The homepage launch is overdue by at least a year, because we have not been actively monitoring its final issues.

Action Items

  • [x] List all the areas that will need to be in good shape before the homepage launch
  • [x] Identify what needs to be done to fix the area
  • [x] Link any issues reference in the this epic
  • [x] Make new Epic issues for each section and link them in the epics and below
    • [x] Add a link to each epic below
  • [ ] Review each epic and add issues with label
  • [ ] Classify into MoScoW
  • [ ] Updating all epic issues with template changes
  • [ ] Review all epic, and determine if all the issues needed for the epic have been created
    • [ ] if it needs issues
      • define new issues to create
      • create issues
    • [ ] When all the epics have all issues
      • review the status of the issues
        • resolve blockers
        • refine monitoring cadence
      • [ ] estimate time to completion across all

Final tasks once issue is completed

Resources/Instructions

Desktop
Mobile

Issues created

  • [ ] #7662
    • [x] #7663
  • [ ] #7666
  • [ ] #7667
  • [x] #7670
  • [ ] #7671
  • [ ] #7672
  • [ ] #7673
  • [x] #7674
  • [ ] #7675
  • [x] #7676
  • [x] #7678
  • [x] #7679
  • [ ] #7904
  • [x] #7680
    • [x] #7677

Epics that need issues to be made

  • [ ] #7664

Epics that have all issues made

Additional links

Homepage image

Group 737

ExperimentsInHonesty avatar Nov 14 '21 18:11 ExperimentsInHonesty

  • [ ] About page - Bonnie to define updates to about page
    • [ ] Letter from ED #860
    • [x] Accomplishments update #2585
      • [ ] Figure out how we are going to display 2020 and 2021 accomplishments on the page
        • https://github.com/hackforla/website/blob/gh-pages/_data/internal/accomplishments.yml (has the 2020 content in it)
        • https://github.com/hackforla/website/blob/gh-pages/_includes/about-page/about-card-accomplishments.html controls how it appears in the accomplishments section
          • [x] Have asked Phu to make an issue for design to reimagine this section.
    • [ ] SDGs list from projects #2037
      • [ ] Saumil will make an issue for adding the sdg info to the site (small issues)
    • [x] Formatting of press section is not responsive #1498
  • [ ] Dashboard
    • [ ] #2776
    • [ ] add Google Analytics to the dashboard to show how many people we reach (Could Have)
  • [ ] Program Areas Pages
    • [ ] - Program areas page mini cards need to be delivered dynamically so that they match the results from the project filters. #2485
  • [ ] Projects Technologies being up to date
    • [x] - We need the technologies field to be free of languages https://www.hackforla.org/projects/?technologies=Python,SASS,SCSS,TypeScript
    • [x] D on above - add languages to the technologies filter so that they can appear together change title of filter to Technologies / Languages
    • [ ] Create a second project page for checking quality of lang vs tech, and it just lists all the projects and has those two filters separated. #2502
  • [ ] Communities of practice page up to date
    • [x] Needs to have github for all CoPs https://github.com/hackforla/website/issues/2357#issuecomment-968349565
    • [ ] Needs to be reviewed to see if updates are required
  • [ ] Join us page issues
  • [ ] wins - see more issue not resolved
    • [ ] https://github.com/hackforla/website/issues/2339
  • [ ] https://www.hackforla.org/about/#news
  • [ ] in order for the footer to work, there needs to be anchor tags on the join us page https://www.hackforla.org/join#volunteer
    • [ ] https://github.com/hackforla/website/issues/3026
  • [ ] revise order on footer to match the join page #2958
  • [ ] ~ask Sarah to~ make an anchor to the contact us section of the homepage: https://github.com/hackforla/website/issues/3023
  • [ ] make a new issue for revising the events page --> The issue is written and this is the issue: https://github.com/hackforla/website/issues/3027
  • [ ] Toolkit gets removed from site for launch if not ready
    • [ ] https://github.com/hackforla/website/issues/2802
  • [ ] update site map
  • [ ] https://github.com/hackforla/website/issues/3377
  • [x] https://github.com/hackforla/website/issues/2211

Post launch

  • [ ] Wins randomizer (has not yet been added to about)
    • [x] https://github.com/hackforla/website/issues/2304
    • [ ] will need to add it to the page after homepage launch (its already coded for the homepage but stuck on the branch).
    • [ ] will need to add code to about page

ExperimentsInHonesty avatar Nov 14 '21 19:11 ExperimentsInHonesty

  • [x] Is Contact Us is supposed to go to the Get In Touch section of redesigned homepage? Yes
Get In Touch get-in-touch

  • [ ] Differences between #2455 and #2393. We should be consistent. Which do you prefer? Probably title capitialization but reach out to zzhoje about the discrepancy to confirm.

    • [ ] Submit your pitch vs Submit your Pitch (nav bar vs footer)
    • [ ] Get in touch vs Get in Touch (nav bar vs footer)
Header Nav Bar (partial) submit-your-pitch-and-get-in-touch-in-nav-header
Footer submit-your-pitch-and-get-in-touch-in-footer

JessicaLucindaCheng avatar Apr 03 '22 09:04 JessicaLucindaCheng

@zzhoje I noticed discrepancies in the capitalization of certain words in the menu design for our navigation bar header compared to the menu design for the footer.

Partial Screenshot of Header Nav Bar Design submit-your-pitch-and-get-in-touch-in-nav-header
Screenshot of Footer Design submit-your-pitch-and-get-in-touch-in-footer

However, I think the capitalization should be the same for the header and footer menus. Thus, I just want to confirm with you the following:

  • There is a difference in capitalization for the word pitch. Should it be Submit your pitch or Submit your Pitch?
  • There is a difference in capitalization for the word touch. Should it be Get in touch or Get in Touch?

Thank you.

JessicaLucindaCheng avatar Apr 07 '22 19:04 JessicaLucindaCheng

@JessicaLucindaCheng I think it would make more sense for these navigation menu items to be in title case, which it seems like the footer is already going for. In title case, the two examples you pulled would be “Submit Your Pitch” and “Get in Touch”. I just think it will be easier for us to keep all of the titles/headers/footers/buttons consistent this way, and title case tends to give more symmetry and visual prominence. One way to check if a phrase is in title case is by using https://capitalizemytitle.com/ . Please let me know what you think! Thanks!

zzhoje avatar Apr 10 '22 15:04 zzhoje

I noticed discrepancies in the capitalization of certain words in the menu design for our navigation bar header compared to the menu design for the footer.

Partial Screenshot of Header Nav Bar Design submit-your-pitch-and-get-in-touch-in-nav-header
Screenshot of Footer Design submit-your-pitch-and-get-in-touch-in-footer

However, I think the capitalization should be the same for the header and footer menus. Thus, I just want to confirm with you the following:

  • There is a difference in capitalization for the word pitch. Should it be Submit your pitch or Submit your Pitch?
  • There is a difference in capitalization for the word touch. Should it be Get in touch or Get in Touch?

Thank you.

Decision made by Bonnie: It is going to be "Submit your Pitch" and "Get in Touch"

After the website homepage launch, research will look into a global change for all the menu items and their corresponding page/section titles.

SAUMILDHANKAR avatar Apr 16 '22 22:04 SAUMILDHANKAR

Decision made by Bonnie: It is going to be "Submit your Pitch" and "Get in Touch"

After the website homepage launch, research will look into a global change for all the menu items and their corresponding page/section titles.

DR made for this decision: DR: Capitalization of menu items in nav bar and header

Not sure if this was passed on to research: "After the website homepage launch, research will look into a global change for all the menu items and their corresponding page/section titles."

JessicaLucindaCheng avatar Jun 03 '22 04:06 JessicaLucindaCheng

  • All overview links work correctly. #2211

abdiaz2018 avatar Sep 16 '22 03:09 abdiaz2018

  • [ ] About page - Bonnie to define updates to about page
    • [ ] Letter from ED #860
    • [x] Accomplishments update #2585
    • [ ] Figure out how we are going to display 2020 and 2021 accomplishments on the page #3035
      • https://github.com/hackforla/website/blob/gh-pages/_data/internal/accomplishments.yml (has the 2020 content in it)
      • https://github.com/hackforla/website/blob/gh-pages/_includes/about-page/about-card-accomplishments.html controls how it appears in the accomplishments section
        • Waiting on content for acomplishments
    • [ ] SDGs list from projects #2037
      • [ ] Saumil will make an issue for adding the sdg info to the site (small issues)
    • [x] Formatting of press section is not responsive #1498
  • [ ] Dashboard
    • [ ] #2776
    • [ ] add Google Analytics to the dashboard to show how many people we reach (Could Have)
  • [x] Program Areas Pages
    • [x] - Program areas page mini cards need to be delivered dynamically so that they match the results from the project filters. #2485
    • [ ] Update all the pages that list Diversity, Equity & Inclusion incorrectly
      • [ ] https://github.com/hackforla/website/issues/4284
      • [ ] https://github.com/hackforla/website/issues/4286
      • [ ] https://github.com/hackforla/website/issues/4287
  • [ ] Projects Technologies being up to date
    • [x] - We need the technologies field to be free of languages https://www.hackforla.org/projects/?technologies=Python,SASS,SCSS,TypeScript
    • [x] D on above - add languages to the technologies filter so that they can appear together change title of filter to Technologies / Languages
    • [x] Create a second project page for checking quality of lang vs tech, and it just lists all the projects and has those two filters separated. #2502
  • [x] Communities of practice page up to date
    • [x] Needs to have github for all CoPs https://github.com/hackforla/website/issues/2357#issuecomment-968349565
    • [x] https://github.com/hackforla/website/issues/4239
    • [x] Needs to be reviewed to see if updates are required
  • [x] Wins randomizer
    • [x] https://github.com/hackforla/website/issues/2304
  • [x] Join us page issues
  • [x] wins - see more issue not resolved
    • [x] https://github.com/hackforla/website/issues/2339
  • [x] https://www.hackforla.org/about/#news
  • [x] in order for the footer to work, there needs to be anchor tags on the join us page https://www.hackforla.org/join#volunteer
    • [x] https://github.com/hackforla/website/issues/3026
  • [x] revise order on footer to match the join page #2958
  • [ ] ~ask Sarah to~ make an anchor to the contact us section of the homepage: https://github.com/hackforla/website/issues/3023
  • [x] make a new issue for revising the events page --> The issue is written and this is the issue: https://github.com/hackforla/website/issues/3027
  • [x] Toolkit gets removed from site for launch if not ready
    • [x] https://github.com/hackforla/website/issues/2802
  • [x] update site map
  • [ ] https://github.com/hackforla/website/issues/3377
  • [x] https://github.com/hackforla/website/issues/2211

ExperimentsInHonesty avatar Jan 11 '23 17:01 ExperimentsInHonesty

@ExperimentsInHonesty

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

github-actions[bot] avatar Jan 27 '23 07:01 github-actions[bot]

@ExperimentsInHonesty

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 30, 2023 at 11:17 PM PST.

github-actions[bot] avatar Feb 03 '23 07:02 github-actions[bot]

@ExperimentsInHonesty

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, February 6, 2023 at 11:17 PM PST.

github-actions[bot] avatar Feb 10 '23 07:02 github-actions[bot]

@ExperimentsInHonesty

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, February 13, 2023 at 11:17 PM PST.

github-actions[bot] avatar Feb 17 '23 07:02 github-actions[bot]

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' 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, February 20, 2023 at 11:17 PM PST.

github-actions[bot] avatar Feb 24 '23 07:02 github-actions[bot]

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' 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, February 27, 2023 at 11:17 PM PST.

github-actions[bot] avatar Mar 03 '23 07:03 github-actions[bot]

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' 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, March 6, 2023 at 11:17 PM PST.

github-actions[bot] avatar Mar 10 '23 07:03 github-actions[bot]

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' 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, March 14, 2023 at 12:16 AM PST.

github-actions[bot] avatar Mar 17 '23 07:03 github-actions[bot]

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' 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, March 21, 2023 at 12:15 AM PST.

github-actions[bot] avatar Mar 24 '23 07:03 github-actions[bot]

Features that need to be finished or parts finished

About Us page

  • URL: https://hackforla.org/about
  • About Us issues on project board
  • Sections
    • ED Letter
      • [ ] #860
    • Sustainability
      • See SDG section below, the content for this, should be dynamic and be pulled from each project file.
    • Accomplishments
      • [ ] Find all the other accomplishment content that has been written and identify what is missing
        URLs for technical issues

        - https://github.com/hackforla/website/blob/gh-pages/_data/internal/accomplishments.yml (has the 2020 content in it) - https://github.com/hackforla/website/blob/gh-pages/_includes/about-page/about-card-accomplishments.html controls how it appears in the accomplishments section

    • Metrics (dashboard)
      • URL: https://hackforla.org/dashboard
      • Org Dashboard Issues on the project board
      • [ ] Review survey results and identify what might need to be changed
      • [ ] Add Google Analytics to the Dashboard https://github.com/hackforla/website/issues/4537
    • Partners
      • [ ] Change title to be Current and Past Partners
    • Sponsors
      • [ ] Change title to be Current and Past Sponsors

Wins

Join Us

Program Areas

Projects Page

  • [ ] URL: https://www.hackforla.org/projects
  • [ ] Projects page Issues on the project board
    • The drop downs have to have consistent content in them (problems with languages, technologies and tools).
      • https://github.com/hackforla/website/issues/6709
      • https://github.com/hackforla/website/issues/6327
      • https://github.com/hackforla/website/issues/6138
      • https://github.com/hackforla/website/issues/4593
      • https://github.com/hackforla/website/issues/4434
      • https://github.com/hackforla/website/issues/4262
    • They need to look better. The chevron we currently have is unattractive. See http://civictechindex.org/about/faq and make an ER to improve ours
    • Make an ER to address the difference between
      • https://www.hackforla.org/projects-check/?technologies=Docker
      • https://www.hackforla.org/projects-check/?languages=Dockerfile

CoPs

Events

Toolkit

  • URL: https://www.hackforla.org/toolkit
  • [ ] Remove the toolkit from the menu. Bring it back when its ready

Sitemap

  • URL: https://www.hackforla.org/sitemap
  • [ ] find or make new issue to update sitemap

On many pages

SDGs

Sitewide

  • [ ] https://github.com/hackforla/website/issues/6140
  • all spelling issues
    • https://github.com/hackforla/website/issues/5450
  • [ ] confirm that all links on the header and footer work

Additional links

Homepage image

Group 737

ExperimentsInHonesty avatar Mar 27 '23 07:03 ExperimentsInHonesty

  • Finish going over the Jan 11th post (items below) and make sure there is an issue or ER for each item mentioned
  • Add the rest of the features that are important to the launch to the 2023-03-27 post
  • Review the board for each feature area and identify any items still missing
    • make ERs for missing items
  • Weekly check the pages to see and report progress (i.e., none of the outstanding issues or ERs are blockers to launching, or X number of points for this to be ready)
  • [ ] Projects Technologies being up to date
    • [x] - We need the technologies field to be free of languages https://www.hackforla.org/projects/?technologies=Python,SASS,SCSS,TypeScript
    • [x] D on above - add languages to the technologies filter so that they can appear together change title of filter to Technologies / Languages
    • [x] Create a second project page for checking quality of lang vs tech, and it just lists all the projects and has those two filters separated. #2502
  • [ ] https://www.hackforla.org/about/#news
  • [ ] in order for the footer to work, there needs to be anchor tags on the join us page https://www.hackforla.org/join#volunteer
    • [ ] https://github.com/hackforla/website/issues/3026
  • [ ] revise order on footer to match the join page #2958
  • [ ] ~ask Sarah to~ make an anchor to the contact us section of the homepage: https://github.com/hackforla/website/issues/3023
  • [ ] Toolkit gets removed from site for launch if not ready
    • [ ] https://github.com/hackforla/website/issues/2802
  • [ ] update site map
  • [ ] https://github.com/hackforla/website/issues/3377
  • [x] https://github.com/hackforla/website/issues/2211

ExperimentsInHonesty avatar Mar 27 '23 08:03 ExperimentsInHonesty

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' 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. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Tuesday, May 9, 2023 at 12:15 AM PST.

github-actions[bot] avatar May 12 '23 07:05 github-actions[bot]

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' 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. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Tuesday, May 16, 2023 at 12:16 AM PST.

github-actions[bot] avatar May 19 '23 07:05 github-actions[bot]

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' 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. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Tuesday, May 23, 2023 at 12:17 AM PST.

github-actions[bot] avatar May 26 '23 07:05 github-actions[bot]

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' 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. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Tuesday, May 30, 2023 at 12:15 AM PST.

github-actions[bot] avatar Jun 02 '23 07:06 github-actions[bot]

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' 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. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Tuesday, June 6, 2023 at 12:16 AM PST.

github-actions[bot] avatar Jun 09 '23 07:06 github-actions[bot]

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' 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. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Tuesday, June 13, 2023 at 12:16 AM PST.

github-actions[bot] avatar Jun 16 '23 07:06 github-actions[bot]

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' 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. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Tuesday, June 27, 2023 at 12:17 AM PST.

github-actions[bot] avatar Jun 30 '23 07:06 github-actions[bot]

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' 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. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Tuesday, July 4, 2023 at 12:18 AM PST.

github-actions[bot] avatar Jul 07 '23 07:07 github-actions[bot]

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' 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. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Tuesday, July 11, 2023 at 12:18 AM PST.

github-actions[bot] avatar Jul 14 '23 07:07 github-actions[bot]

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' 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 Questions/In Review column of the Project Board 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. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Tuesday, July 18, 2023 at 12:16 AM PST.

github-actions[bot] avatar Jul 21 '23 07:07 github-actions[bot]

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' 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 Questions/In Review column of the Project Board 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. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Tuesday, July 25, 2023 at 12:15 AM PST.

github-actions[bot] avatar Jul 28 '23 07:07 github-actions[bot]