How to edit the wiki

The Simpler.Grants.gov public wiki is a collaborative resource. Any internal team member may submit a change request (CR) to update or add content to the wiki. We created a protocol everyone should follow to ensure the wiki aligns with our needs and quality standards.

Change requests

• Before merging changes, you must request a review from at least one content owner. GitBook will email you when the content owner has approved the CR. At that point, you can merge the changes. Use the following table to identify the correct content owner to tag in your request:

Type of content	Content owners / CR approvers	Content owners by name
Welcome page	Nava Content Strategist	Michelle M.
Get involved section	Nava Open Source Evangelist Nava Content Strategist	Brandon T. Michelle M.
Product section	Nava Product Manager	Max K. Chris W.
Design & Research section	Nava Design Lead Nava Content Strategist	Andy C. Michelle M.
References section	Nava Content Strategist	Michelle M.

• Content owners do not need to request a review for their section.

• A6 manages the GitBook and can update any content. Feel free to add them as additional reviewers, especially if you need a fast response or the primary content owner is out of office.

• Structural changes, such as requests to add or delete pages or sections, always require CR approval from the Nava Content Strategist.

• The Nava Content Strategist can help individuals with wiki and editing consultations.

• Suggestion: When requesting feedback on a change request, it can be helpful to send the reviewer a Slack message with the following information:

  • A link to (1) the change request and (2) the preview of published docs

  • A summary of the changes

  • A list of people you’re requesting feedback from

Git commit history

Our official method and source of truth for tracking changes is GitBook’s commit history. This process automatically captures the person’s name, the changes, and the date/time of the change. GitBook will generate a default title for the CR as [Name’s] [Date] changes. You need to re-title it to match our naming convention.

• Naming convention:

  • [GitHub issue #]: Short description

    • Example: #1234: Altered format of images in brand guidelines

  • Omit the GitHub issue number if none is associated with your changes.

    • Example: Altered format of images in brand guidelines

Rename your change request in the top left of the header

Change logs

Change logs have historically existed on each wiki page. However, as of March 2025, we don't have strict guidelines for using the logs.

• Existing change logs will stay, and anyone can add change logs to pages that don’t have one.

• Any contributor may add entries to the logs if desired.

• Tip: Log significant changes (such as updating out-of-date, stale content, or deleting large sections) but not minor changes (such as improvements to spelling, formatting, or clarity). Generally speaking, significant changes provide helpful context to the reader.

How to use GitBook to make edits

1. Log in to GitBook: https://app.gitbook.com/
2. In the top left corner, it should say Simpler Grants. If not, you're in the wrong workspace—click it to switch to the correct workspace. If you don't see the option, ask Michelle M. or anyone from A6 to give you 'reviewer' permissions.

3. Go to Public Wiki , under the Spaces section of the left nav.

4. Click Edit .

5. Make your changes.

6. Name the change using the instructions in "Git commit history" above.

7. Click the arrow next to Merge to open the option to Request a review .

8. Add reviewers using the "content owners" table above.

9. When you receive an email that your change was reviewed, use the Merge button to publish your changes.