Happy Tuesday, Fedora folks! 
The Fedora Docs Team is back. Here is a summary of the recent meeting of the Fedora Docs Team held on February 24, 2026. The Fedora Docs Team is responsible for creating, maintaining, and organizing documentation for the Fedora Project, ensuring users and contributors have access to accurate and helpful information.
Topics discussed in this meeting:
- Announcements & community news
- Ticket #1: Improvement of the instructions for the Fedora Local Authoring System
- Ticket #8: Creating a Beginner’s Guide to Fedora
Note: AI (Google Gemini) was used to summarize the Meetbot-generated HTML log of the public meeting. I edited the AI-generated output before making this Fedora Discussion topic. If you notice mistakes, please provide a correction as a reply to this topic.
Executive Summary
This meeting focused heavily on Mindshare and Outreach goals, specifically lowering the barrier to entry for new documentation contributors and providing better support for brand-new Fedora users.
The team agreed to break down the complex local authoring documentation (Ticket #1) into five manageable sub-issues to make it easier to tackle. There was a strong consensus that the current “contribution machine” is intimidating for newcomers, and that structured mentoring alongside better-organized issue tracking could improve onboarding. Additionally, the team needs a default issue template for the Forgejo tickets repository.
For end-users, the team reviewed a proposal for a “Beginner’s Guide to Fedora” (Ticket #8). While the initial draft has a KDE focus, the overarching goal is to create a generalized, encouraging root document for absolute beginners. The team discussed whether this content could live as a new Antora component (e.g., docs.fp.o/users) rather than creating a whole new sub-team, bridging the gap between Docs and the Ask Fedora community.
Due to time constraints, discussion on Ticket #6 and Ticket #9 was deferred to asynchronous review.
Action Items
- @jflory7: Post an update in Ticket #1, explaining the meeting discussion and the context of where the discussion has gone so far.
- @jflory7: Create five sub-issues from Ticket #1, following @pboy’s five work packages defined in the ticket.
- @cstrauf: Follow-up on Ticket #1 to follow along with the sub-issue split into five new issues for this project.
- @theprogram: Share a summary of meeting discussion in today’s Docs Team meeting into Ticket #8 to help rally a path forward on publishing the beginner’s guide.
Detailed Meeting Log
Announcements & community news
- The Fedora Council video meeting on the 2026 Strategy Summit is scheduled for February 25, 2026, at 15:00 UTC.
- Migrations are currently underway for Forgejo. Some complex repositories, like the Antora theme and the docs website, are facing challenges, but full details are not yet available.
Ad-hoc agenda triaging
- The team agreed to triage Forgejo tickets during the meeting, prioritizing Ticket #1, Ticket #8, Ticket #6, and Ticket #9 as time allowed.
Ticket #1: Improvement of the instructions for the Fedora Local Authoring System
- The team reviewed @pboy’s proposal to group the local authoring content updates into five distinct work packages: Introductory page, “Create a new documentation module” article, Contributing to Quick Docs, Local Workflow article, and a new “Git for Writers” article.
- Clarification was made that GPG signing commits is not currently mandated or supported by Docs infrastructure, so it doesn’t need heavy emphasis.
- Members highlighted that the technical threshold for new contributors is too high, describing it as an intimidating “contribution machine”.
- Call for Help: The team needs help carrying forward the local authoring content. Once the five sub-issues are created, the team requested a volunteer to write a promotional post on Fedora Discussion (or the Magazine) to invite newcomers and offer mentoring.
- Call for Help: A default issue template is needed for the Forgejo tickets repository.
Ticket #8: Creating a Beginner’s Guide to Fedora
- @cstrauf and @theprogram shared a draft of a Beginner’s Guide focused on using Fedora, written in a personal, encouraging style without difficult terminology.
- Though the draft currently uses KDE as a reference point, the intent is for the guide to be a root document linking to further, non-desktop-specific documentation.
- The team discussed the historical lack of a clear home for user-focused content.
- It was proposed that instead of creating a new User SIG, this content could live as a new Antora component (e.g.,
docs.fp.o/users) with its own modules. This would allow contributors from Ask Fedora and Fedora Discussion to easily contribute to user experience docs.