Requirements Gathering for 'Suggest a Guide' Button Link on Toolkits Page

[Sparky-code]

Dependency

• When we are ready to prioritize the toolkit again

Overview

We need to gather requirements for developing how people on the toolkit page can suggest new guides so that we always have a queue of guides to work on and that we are responsive to the community's needs.

Detail

The Suggest a Guide button on the page does not resolve (dev says there is no reference link, since there is no page to link to).

Action Items

• Read through the Suggestion for user experience below.
• Go to the Toolkit page and document (either in comments or in the Google doc provided) the process of searching for information in these sections
  • Guides
  • External Resources
• Go to the Guide Resources wiki and read about how to suggest a guide.
  • Document (either in comments or in the Google doc provided) the process of creating and/or submitting new guides or resources.
• Post recommendations for improvement as a comment on this issue
• Review with Product
• Add label: ready for design so that they can create a mockup of approved recommendation

Resources/Instructions

Preliminary Suggestion for user experience

The 'suggest a guide' buttons could link to a page that

• lays out the process for creating/submitting a guide or documenting access to an external resource.
• has prerequisite information communicating how to do a comprehensive search so that they don't suggest a guide we already have in progress, both on public facing sites and internal sites.

Link to

• HfLA website, Toolkit page: https://www.hackforla.org/toolkit/
• HfLA website, About page, executive letter: https://www.hackforla.org/about/#letter
• Guides Team Wiki, Guide Resources

Information to carry over into the design issue

• Notes about Style:
  • The link should be made in the style of the about page 'Letter From the ED' section of the About Page.
  • That section gets its styling from the executive_letter.yml file, our new page will as well.

Information to carry over into the development issue

• Executive Letter .yml

Document where assignee is putting their notes

• Toolkits Page Suggest a Guide UX Research notes

[github-actions]

Hi @Sparky-code.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:
Feature

NOTE: Please ignore the adding proper labels comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards.
To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Milestone" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels

[JessicaLucindaCheng]

@Sparky-code Please add this Issue to the Project Board. Thanks.