Update Introductory Page for Local Authoring #11
Labels
No labels
Contributors' Guidance
Improve written Material
Contributors' Guidance
technical support measures
effort
high
effort
low
effort
medium
good first issue
help wanted
meeting topic
needs changes
needs reporter feedback
needs review
priority
high
priority
low
priority
medium
priority
on hold
type/content
type/misc
No milestone
No project
2 participants
Notifications
Due date
No due date set.
Blocks
Reference
docs/tickets#11
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Update the "Contributing to Fedora Docs" introductory page to focus primarily on the local authoring workflow to lower the barrier to entry for newcomers.
Background
This issue is Part 1 of 5 in the overarching Ticket #1, which aims to improve and simplify the instructions for the Fedora Local Authoring System. During the February 24, 2026 Docs Team meeting, we agreed that the current "contribution machine" feels too intimidating for newcomers. By breaking this down and focusing on local authoring, we want to make our onboarding experience much more welcoming and accessible.
Details
This is a mentored issue! If you are a newcomer looking to help, please ping @jflory7, @pboy, or @pbokoc in the comments to get started.
To complete this task, please update the Introductory Page with the following:
Outcome
A welcoming, streamlined introductory page that clearly points new contributors toward the recommended local authoring path without overwhelming them with outdated tools.
@jflory7, @pboy, and @pbokoc, keen to help.
Hey @egret, awesome! It would be great if you spent some time working on this one. Do you need any help or pointers on getting started with updating the Introductory Page? Do you have questions that help give you more context before you start revising?
Cool. I'll put some ideas done and bring them to the team. I am very happy to take any pointers you have.