Edit a Page Using the Forge Web Interface

Eli R Version F43 and newer Last review: 2026-04-04

This section will guide you through editing a documentation (docs) page using the Fedora Forge web interface.

Use this method for small changes, such as fixing typos or other simple edits that affect a single page.

Preparation

Edit via the Forge web interface

Every documentation page has an Edit this page button in the top right corner. Use this to locate the page’s source repository on Fedora Forge.

Starting from the docs.fedoraproject.org page that you intend to edit:

  1. Click the Edit button in the top right corner to navigate to the source page.

  2. If you are not already signed in, do so with your FAS account.

  3. Click the Fork button (normally top right). If prompted, enter the details to create your new fork. The default values are suitable in most cases.

    If you receive a warning that the branch is behind in commits, click the Sync button so that it matches the upstream repo.
  4. Manually navigate the folder structure to return to the source page you intend to edit (normally in modules/ROOT/pages/).

  5. Click the Edit button, located on the right side above the file contents, and make your changes directly to the AsciiDoc code.

  6. Use the Preview button, located on the left side above the edit field, to see how the document will look. Keep in mind that some AsciiDoc elements may not render accurately in the preview.

  7. Once you are happy with the edit, scroll to the bottom of the page, and optionally add a message describing the nature of the edit.

  8. Check "Create a new branch for this commit and start a pull request". Optionally, rename the new branch.

  9. Click propose file change, which brings you to the New pull request page

  10. Use the first drop-down selector, merge into, to select the upstream repo. This is normally the main branch, but check with the repository maintainers if in doubt.

  11. Ensure the pull from selector is set to your personal fork, on the newly created branch from step 8.

  12. Click New pull request.

  13. Carry out any final checks, then click Create pull request.

It may take a number of days before your pull request is reviewed. If you have not received a response within five days of opening the PR, consider using Matrix to reach out to the team that is responsible for that repo.