I have some notes on how I'd like the contributor's guide to look in the future. It's obviously not set in stone but I think this would be a good start.

• Intro, what do we do, expectations, ...
• How to join the project
  • Make a FAS account
  • Account setup (generate a public key and upload it to pagure)
  • Join the list, introduce yourself
  • Join IRC and/or Telegram, register on IRC (link to FreeNode docs)
  • optionally check out https://discussion.fedoraproject.org/tags/c/project/fedora-documentation
  • Setup: git, podman, text editor
• Finding work to do
  • Working with issues (assign to yourself, fix, sent PR, tag issue # in PR, close it once merged)
  • Small fixes without issues (just make a PR)
• Working with git
  • Some extreme basics: fork a repo and clone your fork, push changes to it, and create a PR, don't forget to pull from upstream often
• Contributing to existing docs (intro that describes the differences between versioned and unversioned docs)
  • How to contribute to Release Notes (those are versioned but a specific case)
  • How to contribute to versioned docs (docs tied to a specific release, e.g. F30 Install Guide)
  • How to contribute to unversioned docs (quick docs, etc. - docs that are only built as "latest" from master)
  • How to build a preview (how to build the local repo only + how to build the whole site with your local changes included)
• Adding new docs (clone the template repo (https://pagure.io/fedora-docs/template), change configs, create repo on pagure, add it to the site config, set permissions (add group fedora-docs as Admin))
• Publishing docs
• Antora internals
  • Site structure (talk about the main repo that pulls in all the others and builds the full site: https://discussion.fedoraproject.org/tags/c/project/fedora-documentation)
    • Frontpage and how to add things to it
  • UI bundle (I still need to get Adam to publish the sources on pagure before we write about this)
• Translations (not available right now but we'll need that in the future)
• Style Guide
  • Writing tips (simple sentences, no passive voice, that kinda stuff)
  • ASCIIDoc style guidelines:
    • one sentence per line
    • xrefs, includes
    • outside links
    • images, figures
    • imagesdir, partialsdir
    • modules, topics
    • admonitions
    • :experimental:, attributes
    • code blocks, commands with attribute replacement
    • titles (use =, one per page, multiple ==, ===; leveloffset when including)
    • lists (numberedlists always start with 1. for each point; can start with an offset, writing multiple paragraph list items...)
    • tables
    • license, readme (mention published URL in README)