Emergent Requirement - Problem

We need to update the accomplishments for the Guides team on the about page and there is no template for that

Issue you discovered this emergent requirement in

• none

Date discovered

2025-08-22

Did you have to do something temporarily

• YES
• NO

Who was involved

@ExperimentsInHonesty @yashhR

What happens if this is not addressed

its hard for the teams to update the website
I have no place to put the updates for guides team

Resources

Recommended Action Items

• Make a new issue
• Discuss with team
• Let a Team Lead know

Potential solutions [draft]

Make 2 issues:

• 1) Write one Complexity: Medium issue to make a new issue form template that will allow project teams to add or revise an accomplishment for a specified year.

  • Apply the following labels to the issue you are writing:
    • Complexity: Medium
    • p-feature: accomplishments
    • role: front end
    • time sensitive
    • size: 1pt
  • The form template should
    • Ask the following questions:
      • Project team (should be a drop down)
      • URL on hackforla.org website (should be a drop down)
      • Is this an addition or revision? (should be a dropdown with 2 options: addition, revision)
      • Year of accomplishment (should be a dropdown with options for selecting a year from 2020 to 2025)
      • A summary of the accomplishment (should be a text box)
    • Include the following at the bottom of the issue form template

      ### Resources
      - This is the file that will be edited: https://github.com/hackforla/website/blob/gh-pages/_data/internal/accomplishments.yml
      

  • As a last Action Item to the issue you are writing, add the following:

    #### For Merge Team
    - [ ] Once this issue's pr is merged, find the link to the newly created form on the [Create new issue](https://github.com/hackforla/website/issues/new/choose) page. 
       - [x] Add the link to the form in the "Resources/Instructions" section where it says, "Link to newly created form: [INSERT LINK TO THE NEW FORM]" by replacing ` [INSERT LINK TO THE NEW FORM]` with the link directly to the form.
    

  • When writing this issue, add the following to the "Resources/Instructions" section

    - [Syntax for issue forms](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms)
    - For an example of an issue template form, see the "Project Profile Card review and update"
       - [form](https://github.com/hackforla/website/issues/new?template=project-profile-card-review-and-update.yml)
       - [code](https://github.com/hackforla/website/blob/gh-pages/.github/ISSUE_TEMPLATE/project-profile-card-review-and-update.yml?plain=1)
    - Link to newly created form: [INSERT LINK TO THE NEW FORM] 
    

• 2) Write another issue (small) to add each year's accomplishment summary for the Guides Team by using the new form template, which will require the new form to be filled out for each year's accomplishments. For this issue:

  • In the "Dependency" section, add a link to the issue written in step 1 above.
  • After creating the issue, under "Relationships" on the right side menu, select "Mark as blocked by" and find the issue written in step 1 above. (For more info on dependencies in GitHub: https://github.com/orgs/community/discussions/165749

Guides Team's Accomplishments

2020
HfLA launched an initiative to build a library of open guides and templates that help others replicate what works, sharing proven practices from engineering, UX, product, data, and more. These resources support peer learning, agile collaboration, and better civic tech outcomes.

2021
Streamlined the guide creation process by building a centralized tracker and standardizing templates and Instructions, accelerating development of reusable resources across Hack for LA’s Communities of Practice.

2022
Improved the usability of guide-making resources through small sample size user research and iterative design. Transformed complex instructions into modular workshop presentations with consistent formatting, glossary terms, and guided slide notes, making it easier for contributors to learn, teach, and produce high-quality guides. These improvements lower barriers to contribution, improve onboarding, and empowered volunteers to lead guide development more confidently.

2023
Prepared for scale by standardizing public-facing templates and launching Research Ops infrastructure, including reusable research materials, documentation systems, and open-source workflows, to support 100 upcoming guide-maker workshops.

2024
Began centralizing the storage and tracking of guides and issues, and introduced standardized naming conventions to improve discoverability, enable use of in-progress content, and support long-term collaboration and governance.