FreeDomain
Free domain registration and practical DNS learning resources for everyone.
- 209k
- Markdown
- AGPL-3.0
- 3 mo ago
Official Rocky Linux documentation repository.
Repo rocky-linux/documentation, read from GitHub 1 min ago. rocky-linux has not joined Take My Repo.
rocky-linux/documentation is a public repo on GitHub by rocky-linux. Official Rocky Linux documentation repository. It declares the CC-BY-SA-4.0 license on GitHub. It is written mainly in Shell, has 483 stars and last changed on 2026-11-22. Nobody has reviewed it on Take My Repo yet, which says nothing about its quality. Read from GitHub on 2026-11-22.
In the maintainer's words. Shown from GitHub; Take My Repo does not keep a copy.
With Rocky Linux (RL) emerging as a popular RHEL-compatible distribution, this is an exciting time in the open source community. Rocky Linux’s mission is to provide companies and individuals with a stable foundation of open source software for their enterprise and High Performance Computing (HPC) needs. We are here to support that mission with excellent documentation.
To us, excellent documentation hits these marks:
We welcome anyone who wants to be part of this mission. No specific degree, years of experience, or company affiliation is required. Be bold! We promise, you won’t break anything even if you fumble your first attempt.
Documents written by the Rocky Linux documentation team are published under the Creative Commons CC-BY-SA license. This means you are free to copy, distribute and transform the works, while respecting the authors' rights.
The documents and their sources are freely downloadable from:
We host our media sources at github.com. Our team created this document in this source code repository, and stores all other documents there too.
Our standards for Rocky documentation.
The RL Style Guide outlines standards for wording within our documents.
Rocky Linux uses GitHub to manage its code and files, including documentation. Login to GitHub and follow the official Rocky Linux documentation repository.
Documentation is welcome in whatever format you create it in. It does not need to be perfect, just submit what you have and the team will give you feedback to help get it in line with our voice and tone.
That said, RL Documentation uses Markdown format. It is easy to learn and use. Run a text converter on your content or start from scratch with this guide on writing Markdown with proper formatting.
As you become a regular contributor, you will need to create a local repository. See our guide for how to install a Markdown editor and create a local repository on your own computer.
The actual process of reporting an issue, revising, or creating a doc. See the "Notes" section for translations, links, and meta content.
Maybe you have found a broken link or incorrect information while exploring the Rocky docs. We call this an issue, and we want to know about it. You can mention it on the Mattermost Documentation channel, or visit GitHub and make a proper issue report. GitHub has a handy guide for how to create an issue.
Add a missing word, correct an error, or clarify a confusing bit of text. You will not break anything because someone will review your contribution before it goes live. Here is the basic process.
Start on the page you want to update on https://docs.rockylinux.org/
Click the “Edit” pencil in the upper right corner of the document. This takes you to the original document stored on GitHub.
The first time you contribute to the RL repository, you will receive a prompt with a green button to “Fork this repository and propose changes.” This creates a duplicate copy of the RL repository where you make your suggested edits. Click the green button and continue.
Make your changes
Follow the existing Markdown formatting. Make the necessary change.
Propose changes
At the bottom of the page, write a brief description in the title of the block entitled Propose changes.
Then click Propose changes, which will Commit your changes to a completed document within your forked repository.
Review changes
Now you can review your changes, line by line. If you missed anything, back up to the previous page and correct it again (you will have to start over), then click Propose Changes again.
Once the doc is the way you want it, click the green button that says Create Pull Request (PR). This provides one more chance to double check your changes and confirm the doc is ready.
Create Pull Request
So far you have been working in your own repository. Next you submit it to the documentation team to merge your version into the main version of the document.
Click the green button that says Create Pull Request, which sends it to the RL documentation team for review.
Wait
Once the RL team reviews your request, they will respond in one of three ways.
If you have to make changes, you will see why you need a local repository. The team can talk you through what to do next. In good news, it is still fixable.
Need more in-depth explanation? Here are the same directions with more elaboration under the heading, "Submit an update."
Success? Welcome to the team, you are officially a Rocky Linux documentation contributor. We will add your profile to the contributor list at the bottom of this document shortly.
For more than a word or two of occasional edits, we recommend that you setup a local repository on your own machine. From there, you can revise documentation from your clone of the RL repository, Commit it to your online GitHub repository, and then create Pull Requests to merge with the main repository.
Advanced users might want to create a complete documentation server on your local Linux workstation or VM. We have guides to set that up with Docker or LXD. We also have a fast documentation system with special caveats if you are using Python on the same server.
Rocky Linux documentation includes Guides, Books, Labs, and Gemstones. Your original contributions are welcome in any of these categories.
Please include the following meta information at the top of all new documentation:
---
title: Document title
author: the author of the source (English) version of the document.
contributors: a comma separated list of contributors to the source document.
tested with: a comma separated list of Rocky Linux versions, for example 8.6, 9.0
tags:
- displayable tags
- these are also searchable
- they are two-space indented and start with a "-" as shown here
- generally, they should each be one word
---
To add more advanced elements to your Markdown-formatted document beyond text, visit the formatting guide. It covers admonitions, tables, quotes, and more.
The process for submitting original content is similar to updating an existing document from your local repository. Create a new document within your Markdown editor, Commit it to your GitHub repository, then submit a Pull Request to merge into the main branch of the repository. The documentation leads will decide where the new document will live.
For information about the Rocky Linux documentation policy on AI-assisted contributions, review our AI-assisted contributions policy.
Links can be internal (other docs within our domain), external (publicly hosted URLs), or lab-based (used as examples within your document).
The (Markdown) format for links within the documentation is square brackets around the descriptive name or label: [our site], followed by your link in parentheses: (https://example.com)
To help lab-based URLs pass our automatic URL checker, there is a list of excluded domain names you can use. You can request the addition of a new exclusion if none in the current list works. An editor might adjust your lab-based URL, or add an exclusion if warranted.
Please note the IEEE recommendations for local domain names RFC #8375 Special-Use Domain 'home.arpa.' published in May 2018:
!!! warning "Problems occur when changes are made to translated files outside of Crowdin"
When changes are made directly to translated files in GitHub PR, if they are approved and merged, they cause issues with Crowdin's tracking of the document changes. If you are making changes to an English (source) document, do not include the other languages where the file may exist (For example `index.fr.md` or `index.uk.md`) just make the change to the English source document and the translators will pick up the change in Crowdin and fix it in the other languages.
We add to these docs in new languages as fast as we can get translators on board, and seek contributors for this area especially. We use Crowdin for updates.
Translators, if you find a word in the source document that does not translate well into your language, or an error that prevents a perfect translation, please fix that in the source document and make a Pull Request. In that case, add yourself as a contributor in the meta content of that source (English) document.
Translators may add themselves to the metadata if desired. Example:
title: This document title author: Sam Spade contributors: Some New Guy translators: Add this meta tag and your name
We want to make sure we acknowledge you (contributor or translator) in the all-contributors section at the bottom of this page. This is a list of everyone who has been part of this documentation project, whether creating content, spotting and fixing errors, or translating. If you have been missed and your name or handle does not appear, you can request to be added) here. We appreciate your contributions.
For reporting issues, asking questions, getting support, and getting to know the documentarians.
For general questions about installing and using Rocky Linux, visit our community forums. For questions about behind-the-scenes stuff like documentation, we have other channels.
To ask real-time questions create a Rocky Linux Mattermost account if necessary, then navigate to the Rocky Linux General or Documentation channel -- or whichever seems appropriate to your question. You should get a response within hours.
Welcome aboard! Meet the rest of our awesome contributors below: (emoji key):
This project follows the all-contributors specification. Contributions of any kind are welcome!
rocky-linux/documentation is a public repo on GitHub by rocky-linux. Official Rocky Linux documentation repository.
It declares the CC-BY-SA-4.0 license on GitHub.
Its maker tagged it for macOS, Windows and Linux, or as Docker or cross-platform. That is declared by the maker; Take My Repo has not tested it.
Open "Take it" on its page: Take My Repo writes an install plan for your machine and hands it to your AI agent (Claude Code, Codex or Cursor), which asks you before each step. Take My Repo has not tested it on any machine.
Its last change on GitHub was on 2026-11-22. GitHub counts 18 open issues and pull requests. Take My Repo does not judge from that whether it is maintained.
Nobody has reviewed it on Take My Repo yet, which says nothing about its quality.

Free domain registration and practical DNS learning resources for everyone.
OpenVPN road warrior installer for Ubuntu, Debian, AlmaLinux, Rocky Linux, CentOS and Fedora
Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Mirror available at: https://gitlab.com/89luca89/distrobox
Storybook is the industry standard workshop for building, documenting, and testing UI components in isolation
Rocky Linux is a community enterprise Operating System designed to be 100% bug-for-bug compatible with Enterprise Linux created in response to the effective discontinuation of CentOS.
The infrastructure monorepo for the Rocky Linux project. This project will be archived/deprecated in the future.
The official website of the Rocky Linux Project.
The official website of the Rocky Linux project.
Cloud-native build and release tools tailored to building, releasing and maintaining Linux distributions and forks
This page is also available as structured data, with the same sources and dates.
/api/v1/resources/gh/rocky-linux/documentationTake My Repo has not tested this on your machine. Requirements come from the project's own documentation.