GITBOOK-174: No subject

documentation/wiki/README.md

@@ -20,21 +20,27 @@ layout:
 
 # 👋 Welcome
 
-{% hint style="warning" %}
-**In Progress** :construction:
+This website is a resource for internal Simpler.Grants.gov team members, external collaborators, and community members.
 
-Pardon the construction dust! We're still setting up our public wiki, so pages may be changing names or getting moved. 
-{% endhint %}
-
-Looking to join the Simpler Grants community? Start here:
+Under the Get Involved section, you'll find all the resources you need to participate in open-source development. We recommend starting here:
 
 {% content-ref url="get-involved/get-involved.md" %}
 [get-involved.md](get-involved/get-involved.md)
 {% endcontent-ref %}
 
+The Product section is helpful in understanding how past development and process decisions were made and getting information on the work that is currently in development.
+
+
+
+
+
+
+
+Are you looking to join the Simpler Grants community? Start here:
+
 ## Find the information you need
 
-* [I want to meet the team that is working on the Simpler.Grants.gov initiative](about/team.md)
 * [I want to learn more about the features the team is planning to build for simpler.grants.gov](product/product-roadmap.md)
 * [I want to learn more about the tools the team is using to collaborate](get-involved/communication-channels/)
 * [I want to figure out how I can get more involved with the project](get-involved/get-involved.md)
+

documentation/wiki/SUMMARY.md

@@ -2,16 +2,11 @@
 
 * [👋 Welcome](README.md)
 
-## About
-
-* [Team](about/team.md)
-* [Terminology](about/terminology.md)
-
 ## GET INVOLVED
 
 * [Why open source?](get-involved/get-involved.md)
 * [How to contribute code](get-involved/github-code.md)
-* [How to contribute issues](get-involved/github-planning/README.md)
+* [How to create tickets](get-involved/github-planning/README.md)
   * [Report a bug](get-involved/github-planning/filling-out-a-bug-report.md)
   * [Request a feature](get-involved/github-planning/filling-out-a-feature-request.md)
   * [Report a security vulnerability](get-involved/github-planning/reporting-a-security-vulnerability.md)
@@ -116,6 +111,11 @@
   * [Typography](design-and-research/brand-guidelines/typography.md)
   * [Iconography](design-and-research/brand-guidelines/iconography.md)
   * [Photos and illustrations](design-and-research/brand-guidelines/photos-and-illustrations.md)
-* [Voice and tone guidelines](design-and-research/voice-and-tone-guide.md)
+* [Content guidelines](design-and-research/content-guidelines/README.md)
+  * [Voice and tone](design-and-research/content-guidelines/voice-and-tone-guide.md)
 * [User research](design-and-research/user-research/README.md)
   * [Grants.gov archetypes](design-and-research/user-research/grants.gov-archetypes.md)
+
+## REFERENCES
+
+* [Glossary](references/terminology.md)

documentation/wiki/design-and-research/content-guidelines/README.md

@@ -0,0 +1,3 @@
+# Content guidelines
+
+Simpler.Grants.gov has developed content guidelines to assist internal and external collaborators as they develop the website. Currently, we have a voice and tone guide available. Additionally, more resources on proper language use within our product are forthcoming.

documentation/wiki/design-and-research/voice-and-tone-guide.md → documentation/wiki/design-and-research/content-guidelines/voice-and-tone-guide.md

@@ -2,7 +2,7 @@
 description: Guidance for writing content and communications in the Grants.gov brand voice
 ---
 
-# Voice and tone guidelines
+# Voice and tone
 
 ## I. Introduction and Definitions
 
@@ -69,7 +69,7 @@ For grants you can apply for using Grants.gov, you’ll be able to track when it
 * We anticipate what our audiences want or need to know and pull out the information that impacts them most.
 
 {% hint style="warning" %}
-_In this example from the Grants.Gov Release Notes page, a user has to open a PDF to understand the changes and whether they affect them._ <img src="../.gitbook/assets/Grants.gov Release Notes Example (1).png" alt="Screenshot of a release notes table entry that includes the release number, a short description of the release, the release date, and a link to the full release details." data-size="original">
+_In this example from the Grants.Gov Release Notes page, a user has to open a PDF to understand the changes and whether they affect them._ <img src="../../.gitbook/assets/Grants.gov Release Notes Example (1).png" alt="Screenshot of a release notes table entry that includes the release number, a short description of the release, the release date, and a link to the full release details." data-size="original">
 {% endhint %}
 
 {% hint style="success" %}

documentation/wiki/design-and-research/user-research/README.md

@@ -1,2 +1,7 @@
 # User research
 
+The Simpler.Grants.gov team regularly conducts user research to inform our design work, including usability tests and user interviews.
+
+You can [sign up to participate in future research](https://ethn.io/91822).
+
+We also use participatory design practices as part of our research toolkit. Over eight months, members of a cohort of real Grants.gov users work with the product and design team sign practices to influence the user experience of Simpler.Grants.gov.

documentation/wiki/design-and-research/user-research/grants.gov-archetypes.md

@@ -1,2 +1,85 @@
 # Grants.gov archetypes
 
+Toward the beginning of the Simpler.Grants.gov project in 2023, we conducted a research study to gather insights from applicants, potential applicants, and grantmakers. As a result, we identified four major archetypes of Grants.gov applicants and identified four themes that cover the problems our work should address. Additionally, we found the most common barriers users face when applying on Grants.gov. We’re using these findings to guide our work.
+
+### The methodology
+
+Applicants and grantmakers were selected for user interviews to understand their experience better using Grants.gov. We recruited equitably to ensure a diverse pool of participants.
+
+Of the interviewed applicants, 26% were first-time, 39% were occasional, and 34% were frequent applicants.
+
+With the findings from these interviews, we defined user archetypes and general themes to guide the Simpler.Grants.gov user experience.
+
+#### Research objectives:
+
+* Examine existing user journeys and behaviors, identifying how Grants.gov fits into their overall approach
+* Learn from user experiences, roles, challenges
+* Identify barriers and how a simpler Grants.gov can create a more intuitive user experience, especially for new users
+
+### Applicant archetypes
+
+Archetypes are compelling summaries that highlight the types of applicants that Grants.gov serves. They’re informed by and summarize user research data and represent user behaviors, attitudes, motivations, pain points, and goals. We’ll use these archetypes to influence our design decisions, guide the product’s direction, and keep our work human-centered.
+
+#### The Novice
+
+Applicants lacking familiarity with the grant application process, including first-time or infrequent applicants and those who never apply
+
+Novices are often new to the grants application process. They face a steep learning curve when finding and applying for funding opportunities. Solving their needs will generate a more inclusive Grants.gov experience.
+
+#### The Collaborator
+
+Applicants who've applied before. They work with colleagues or partner organizations to increase their chances of success.
+
+Collaborators have more familiarity with Grants.gov. However, they face challenges with coordinating application materials and often resort to tools and resources outside of Grants.gov.
+
+#### The Maestro
+
+Frequent applicants familiar with Grants.gov, who are often directly responsible for managing multiple applications at once
+
+Maestros have an established approach to applying, which may include software and tools outside of Grants.gov. Their primary concerns are determining grant feasibility and staying ahead of deadlines.
+
+#### The Supervisor
+
+Applicants who have a more senior role at organizations and have less frequent direct involvement with Grants.gov than Maestros.
+
+Supervisors are responsible for oversight, approvals, final submissions, and keeping registrations current. Their time is limited, as they're often busy with the organization's other needs.
+
+### General themes
+
+The existing Grants.gov website works best for those who use it regularly. Larger organizations and teams of Collaborators and Maestros are typically more familiar with the ins and outs of the system. To create a simpler Grants.gov with an intuitive user experience that addresses the needs of all archetypes, four themes were defined:
+
+#### Frictionless functionality
+
+Reduce the burden on applicants and grantmakers, from both a process and systems perspective, by addressing the pain points that negatively affect their experience
+
+#### Demystify the grants process
+
+Ensure that all users have the same easy access to instructional and educational information that empowers them to have a smoother, more informed, and more confident user experience
+
+#### Sophisticated self-direction
+
+Meet users where they are during crucial moments by providing a guided journey through opt-in contextual support that reduces their need to find help outside the system
+
+#### Create an ownable identity
+
+Create a presence that reflections our mission and supports our users through visual brand, content strategy, and user interface design systems
+
+### Where can we have the most impact?
+
+The most significant burden is on Novice to become an expert on the grants process and system. To execute our mission, there is a need to improve awareness, access, and choice. This requires reaching out to those unfamiliar with the grant application process.
+
+There are many common barriers that users face:
+
+
+
+<table><thead><tr><th width="252">Barrier</th><th>Impact</th></tr></thead><tbody><tr><td><h4>Digital connectivity</h4></td><td>Depending on availability and geography, a stable internet connection is not guaranteed to support a digital-only experience.</td></tr><tr><td><h4>Expertise</h4></td><td>Small organizations face higher turnover, and alumni often take their institutional knowledge and expertise with them when they leave.</td></tr><tr><td><h4>Education</h4></td><td>It often requires a high level of education to comprehend the complexity and language of funding opportunity announcements.</td></tr><tr><td><h4>Confused by announcements</h4></td><td>Novices have difficulty determining their eligibility and understanding the details of the funding opportunity announcement.</td></tr><tr><td><h4>Organization size</h4><p><br></p></td><td>Not all organizations have dedicated resources for seeking grant funding. Many are 1-person shops who are trying to do it all.</td></tr><tr><td><h4>Cognitive load</h4></td><td>Applicants often apply for funding through several agencies, requiring they learn multiple processes and satisfy varying requirements.</td></tr><tr><td><h4>Lost at the start</h4></td><td>Novices don’t see a clear call-to-action for getting started, and they have trouble finding the one-on-one help at the beginning of the process.</td></tr><tr><td><h4>Time</h4></td><td>Most individuals wear a lot of hats (community advocate, program lead, etc.) and "grants applicant" is only part of their responsibilities and requires efficiency.</td></tr><tr><td><h4>Overworked</h4></td><td>New organizations are often too burdened with internal paperwork and infrastructure to support external funding and reporting.</td></tr><tr><td><h4>Language</h4></td><td>Applicants are faced with a lot of jargon without context or definitions, which is especially difficult when English is not their native language.</td></tr><tr><td><h4>Overwhelmed by search</h4></td><td>New applicants misuse the keyword search function and have trouble understanding the acronyms and terminology.</td></tr><tr><td><h4>Blindsided by requirements</h4></td><td>New applicants are caught off guard by SAM.gov registration and often miss the format and file name requirements.</td></tr></tbody></table>
+
+
+
+## Change log
+
+Major updates to the content of this page will be added here.
+
+| Date      | Update          | Notes |
+| --------- | --------------- | ----- |
+| 1/30/2024 | Initial content |       |

documentation/wiki/get-involved/communication-channels/README.md

@@ -9,7 +9,7 @@ description: >-
 {% hint style="danger" %}
 **Warning**
 
-Prohibited activity (e.g. violations of our code of conduct or the Federal Hatch Act) are _**never**_ allowed in _**any**_ channel. Project maintainers have the right and responsibility to moderate and remove prohibited content from all communication channels.
+Prohibited activity (e.g., violations of our Code of Conduct or the Federal Hatch Act) is never allowed in any channel. Project maintainers have the right and responsibility to moderate and remove prohibited content from all communication channels.
 {% endhint %}
 
 ## Public channels
@@ -20,24 +20,12 @@ The following table links to the main channels we use to collaborate on the proj
 
 ## Channel-specific guides
 
-Visit the following pages to learn more about individual communication channels
-
-{% content-ref url="broken-reference" %}
-[Broken link](broken-reference)
-{% endcontent-ref %}
+Visit the following pages to learn more about individual communication channels.
 
 {% content-ref url="slack-community-chat/" %}
 [slack-community-chat](slack-community-chat/)
 {% endcontent-ref %}
 
-{% content-ref url="broken-reference" %}
-[Broken link](broken-reference)
-{% endcontent-ref %}
-
-{% content-ref url="../github-planning/" %}
-[github-planning](../github-planning/)
-{% endcontent-ref %}
-
 {% content-ref url="zoom-public-meetings.md" %}
 [zoom-public-meetings.md](zoom-public-meetings.md)
 {% endcontent-ref %}

documentation/wiki/get-involved/communication-channels/slack-community-chat/README.md

@@ -17,12 +17,12 @@ Please [use this invitation link](https://join.slack.com/t/betagrantsgov/shared_
 ### 1. Joining Slack
 
 * If you need help installing Slack, please use the link below to our step-by-step guide.
-* If you haven't already, sign up for Slack using the provided invitation link above.
-* Once signed up, download the Slack desktop or mobile app for easy access to the workspace.
-* Post a short introduction in [#all-introductions](https://betagrantsgov.slack.com/archives/C05TDLG3M51) please include:
+* If you haven't already, sign up for Slack using the invitation link above.
+* Once signed up, download the Slack desktop or mobile app to easily access the workspace.
+* Post a short introduction in [#all-introductions](https://betagrantsgov.slack.com/archives/C05TDLG3M51). Please include:
   * Name
   * Pronouns
-  * What brings you to the Simpler Grants community
+  * What brings you to the Simpler.Grants.gov community
 
 {% content-ref url="installing-slack.md" %}
 [installing-slack.md](installing-slack.md)

documentation/wiki/get-involved/community-events/README.md

@@ -1,2 +1,14 @@
 # Community events
 
+The Simpler.Grants.gov team periodically hosts public events to engage our community with the ongoing development work.
+
+#### Coding Challenges
+
+Opportunities for external contributors to help the Simpler.Grants.gov team solve problems and develop site functionality.
+
+The format varies. Software engineers of all experience levels are encouraged. Some, but not all, Coding Challenges also have a role for designers and researchers. The event is virtual but can vary from a weekend to several weeks.
+
+#### Simpler.Grants.gov Big Demo
+
+About every four months, our team hosts a public virtual demonstration of the features and work we produced in the previous 4-month development cycle.  
+