homepage launch

[ExperimentsInHonesty]

Overview

We are down to the last items before the homepage launch

Action Items

• List all the areas that will need to be in good shape before the homepage launch
• Identify what needs to be done to fix the area
• Link issues that are already made
• Make new issues for each section and copy the list of URLs and issues to those issues. List the new issues below

Resources/Instructions

Issues created

• Prepare the About Us page for Homepage Launch
• Prepare the Wins page and wins card randomizer for Homepage Launch
• Prepare the X page for Homepage Launch
• Prepare the X page for Homepage Launch
• Prepare the X page for Homepage Launch
• Prepare the X page for Homepage Launch

[JessicaLucindaCheng]

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."

[ExperimentsInHonesty]

This is the latest list audited and expanded from these prior comments:

• homepage launch #2481 (comment)
• homepage launch #2481 (comment)

This is a list of all the issues related to homepage launch. There may need to be more issues made (see each section)

About Us page

• URL: https://hackforla.org/about
• About Us issues on project board
• Sections
  • ED Letter
    • Revise the letter in this closed issue About us page - Letter from the Executive Director #860
    • make a new issue to add the letter to the site.
  • 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

    • See Wins section below for the wins randomizer issue
  • 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 ER: Add analytics about how many people we reach to the Dashboard #4537
    • See this issue to evaluate if its related Google Analytics #1730
    • See this issue and see if there are any issues on other repositories that might be required to complete the dashboard.
  • Partners
    • Change title to be Current and Past Partners
  • Sponsors
    • Change title to be Current and Past Sponsors

Wins

• URL: https://hackforla.org/wins
• Wins issues on the project board
  • Write an issue to manual pick a new win, and hard code it on the about page. The randomizer can't get worked on until the homepage branch is merged into the gh-pages branch
    • ER: Wins randomizer content management #4282 (has a dependency on 4910 being finished)
    • Wins Randomizer for About page #4190
  • Create an issue to change the WINS form to only offer to use their GitHub image. We will not be able to display people's LinkedIn profile pictures, the LinkedIn API Terms of Service disallows it. So we need to revise the form to reflect that.
  • Improve the drop downs on Wins page to avoid unnecessary wrapping  #6272
  • Write copy explaining "brief overview" question on Wins form #3140
  • ER: Feasibility of tracking the “Share your wins” and “Submit” buttons using Google Analytics #4388

Join Us

• Join us page Issues on the project board
• URL: https://www.hackforla.org/join
  • ER: Fix text alignment on Join Us and About header #5973

Program Areas

• URL: https://www.hackforla.org/program-areas
• Program Areas Issues on the project board
  • Create each program area page automatically using a layout #3328

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).
    • ER: Inconsistent filtering behavior for "Languages/Technologies/Tools" category #6709
    • Epic: Make sure that the data in the project's page filters content is properly categorized #4434
    • Review project data to determine reclassifying requirements for their Technologies and Tools. #4262
      • Make an ER to address the difference between
        • https://www.hackforla.org/projects-check/?technologies=Docker
        • https://www.hackforla.org/projects-check/?languages=Dockerfile
  • 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

Project Pages

• Access the Data
  • Add additional repo(s) for project: Access the Data #5127
  • Rollout Plan: Change code to read data from multiple project repositories #6138
  • Display all the contributions for each person in a project that has 2 or more repos #6144
  • Update Project Profile: Access the Data #5337
• Expunge Assist
  • ER: Update Project Profile: Expunge Assist #6834
  • Update Project Profile: Expunge Assist (Remove Curtis Barber, Add Maria Weissman) #6866
  • ER: Update Project Profile: Expunge Assist #6579
• New Project
  • ER: A project that Hack for LA completed in the past is missing from the website #4342
• All project pages
  • ER: discrepancies in meeting data sourced from API calls to VRMS vs. vrms-data.json #6838
  • Update Project Info Page to show Meeting Description #6930
  • ER: Issue with Public Facing Slack Channel Links for Non members #6129
  • Update Project Info Page to show Meeting Description #6930
  • Update Team Meeting data on the Events page to show meeting frequency #6920
  • Improve accessible naming for resource icons in project pages #6655

CoPs

• URL: https://www.hackforla.org/communities-of-practice
• Communities of Practice Issues on the project board
  • Needs to be reviewed to see if updates are required

Events

• URL: https://www.hackforla.org/events
• Events Issues on the project board
• ER: have the meeting data be more relevant, depending on what page it appears on #6320 (this issue is also relevant to Project info and Project meetings pages
• Refactor the Events page header to replace the iframe element #6749
• Removing instances of "test" as a substring in the events page #6369

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

• SDG issues on project Board
• Issues
  • Evaluate the UN guidelines for SDG usage to determine if we can or cannot round edges of the SDGs.
    • If we cannot, then we need to update the citizen engagement page to have squared corners like this figma: citizen engagement
    • if we can, we need to evaluate if we want to change the
      • About page Sustainability section
      • Citizen Engagement page
  • Epic: Fix size of SDG icons to match Figma design #4229
  • Create issues for new project impact content to be added to project md files #2037
  • ER: Review the project.yml file template and files to fix the section for SDG info #6277
  • Rollout Plan: Move, refactor, and add SDG info and images #4153
    • Creating a yml file for SDG 17 #6223
    • Creating a yml file for SDG 16 #6222
    • Creating a yml file for SDG 13 #6221
    • Creating a yml file for SDG 8 #6220
• Resources
  • Program Area Audit Spreadsheet - has the SDG info for all projects and issue tracking

Sitewide

• ER: Make Civic Tech Structure org title consistent across all instances #6140
• ER: Find all the places that GitHub should be GitHub and fix #6161
• all spelling issues
  • Epic: Create template, spreadsheet and list of issues for spellcheck audit #5248 see this epic issue for details.
• confirm that all links on the header and footer work
  • Implement the new design for the top navigation bar #2455

Additional links

Homepage image

[ExperimentsInHonesty]

CTJ Accomplishments

• Accomplishment Summaries CivicTechJobs#548

[ExperimentsInHonesty]

We have made some issues for projects to give us their accomplishments for the accomplishment page. We have created a new project board to track that Admin: Project Team Tasks, Accomplishment tab

We need to find all the relevant issues for each project and add them to the board . Here is an org search for accomplishment https://github.com/search?q=org%3Ahackforla+accomplishments&type=issues

[HackforLABot]

@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, October 8, 2024 at 12:05 AM PST.}

[HackforLABot]

@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, October 15, 2024 at 12:04 AM PST.}