[Repo alignment] Write a common README for all docs projects and set it everywhere #36

Closed
opened 2026-05-05 10:21:06 +00:00 by pbokoc · 7 comments
Owner

Subset of #18.

We need to come up with a shorter README for docs repos. The new README should:

  • Have a short explanation of the repo's topic
  • Link to where the docs are published (the output URL)
  • Link to contributor docs
  • Contain info about who is responsible for said docs and a contact link (Matrix channel, mailing list, team page in docs, ...)
  • NOT include the part about repo structure etc. - that belongs in contributor docs so we can maintain it in one place

And in order to close this issue, all repositories in the docs organization (except "service" repos like tickets) should use it. Published repositories outside the docs org should be left to do whatever they want, though we should let them know they might want to follow our lead.

Subset of #18. We need to come up with a shorter README for docs repos. The new README should: - Have a short explanation of the repo's topic - Link to where the docs are published (the output URL) - Link to contributor docs - Contain info about who is responsible for said docs and a contact link (Matrix channel, mailing list, team page in docs, ...) - NOT include the part about repo structure etc. - that belongs in contributor docs so we can maintain it in one place And in order to close this issue, all repositories in the [docs](https://forge.fedoraproject.org/docs) organization (except "service" repos like tickets) should use it. Published repositories outside the docs org should be left to do whatever they want, though we should let them know they might want to follow our lead.
pbokoc self-assigned this 2026-05-05 10:21:06 +00:00
pbokoc added this to the (deleted) project 2026-05-05 15:07:33 +00:00
Member

Here's my suggestion for the common README. Let me know what do you think. ;)

# Fedora [NAME] Documentation

[SHORT DESCRIPTION – 1-2 sentences about what the documentation covers]

## Published documentation

The published version of this documentation is available at:
[docs.fedoraproject.org/en-US/...](https://docs.fedoraproject.org)

## Contributing

We welcome contributions! Whether it's fixing a typo, reporting an outdated
page, or writing new content — every little bit helps.

See the [Fedora Docs Contributor Guide](https://docs.fedoraproject.org/en-US/fedora-docs/contributing-docs/)
for how to get started.

Please report **content issues** in this repository.
For general site/publishing issues, use the
[Fedora Docs Website repository](https://forge.fedoraproject.org/docs/docs-fp-o).

## Contact
- **Matrix:** [#docs:fedoraproject.org](https://matrix.to/#/#docs:fedoraproject.org)
- **Private comms:** Use our FAS emails for anything that shouldn't be public.
- **Discussion forums:** [discussion.fedoraproject.org](https://discussion.fedoraproject.org/tag/docs-team/337)
Here's my suggestion for the common README. Let me know what do you think. ;) ``` # Fedora [NAME] Documentation [SHORT DESCRIPTION – 1-2 sentences about what the documentation covers] ## Published documentation The published version of this documentation is available at: [docs.fedoraproject.org/en-US/...](https://docs.fedoraproject.org) ## Contributing We welcome contributions! Whether it's fixing a typo, reporting an outdated page, or writing new content — every little bit helps. See the [Fedora Docs Contributor Guide](https://docs.fedoraproject.org/en-US/fedora-docs/contributing-docs/) for how to get started. Please report **content issues** in this repository. For general site/publishing issues, use the [Fedora Docs Website repository](https://forge.fedoraproject.org/docs/docs-fp-o). ## Contact - **Matrix:** [#docs:fedoraproject.org](https://matrix.to/#/#docs:fedoraproject.org) - **Private comms:** Use our FAS emails for anything that shouldn't be public. - **Discussion forums:** [discussion.fedoraproject.org](https://discussion.fedoraproject.org/tag/docs-team/337) ```
Member

I like it.

As it is for totally new people, I do not think they will know what 'including a local preview' means. So we could leave that out, and make sure the links are there from the Contributor Guide.

I like it. As it is for totally new people, I do not think they will know what 'including a local preview' means. So we could leave that out, and make sure the links are there from the Contributor Guide.
Member

Good point. I'll remove it.

Good point. I'll remove it.
Author
Owner

A couple more things @jonashub

If you don't mind, please edit it into the post above so I can copypaste it later and not worry about it :)

A couple more things @jonashub * Replace the Matrix room name with this link: https://matrix.to/#/#docs:fedoraproject.org * Add a link to the forums: https://discussion.fedoraproject.org/tag/docs-team/337 If you don't mind, please edit it into the post above so I can copypaste it later and not worry about it :)
jonashub referenced this issue from a commit 2026-06-02 17:48:47 +00:00
Member
Here is a list of repos where I believe we should implement this: - [x] https://forge.fedoraproject.org/docs/quick-docs - [x] https://forge.fedoraproject.org/docs/release-notes - [x] https://forge.fedoraproject.org/docs/team-docs - [x] https://forge.fedoraproject.org/docs/accounts-docs - [x] https://forge.fedoraproject.org/docs/beginners-guide Here I'm not completely sure: - [x] https://forge.fedoraproject.org/docs/site-frontpage - [x] https://forge.fedoraproject.org/docs/release-docs-home
Author
Owner

Yeah, let's do the latter three as well.

E: Sorry, not the Contributor's Guide, that's the archived one and we have team-docs already covered.

Actually I'll just move that into the graveyard.

Yeah, let's do the latter three as well. E: Sorry, not the Contributor's Guide, that's the archived one and we have team-docs already covered. Actually I'll just move that into the graveyard.
jonashub referenced this issue from a commit 2026-06-03 19:48:24 +00:00
pbokoc referenced this issue from a commit 2026-06-04 11:38:24 +00:00
jonashub referenced this issue from a commit 2026-06-05 06:24:51 +00:00
jonashub referenced this issue from a commit 2026-06-05 06:38:05 +00:00
Author
Owner

All right, looks like we're all done. Thanks @jonashub!

All right, looks like we're all done. Thanks @jonashub!
pbokoc 2026-06-05 08:29:12 +00:00
Sign in to join this conversation.
No milestone
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
docs/tickets#36
No description provided.