Contributing
RunEntLinux is a documentation project. This page describes how to report problems and the writing conventions.
Ways to Contribute
Section titled “Ways to Contribute”Report Issues
Section titled “Report Issues”If you find content errors, outdated commands, or inaccurate descriptions, please report it to the site maintainers, with the page address, system version and observed output (remove credentials and private information).
Add Content
Section titled “Add Content”Content is maintained by the site maintainers. When adding tutorials or improving existing content:
- Follow the conventions in
WRITING_GUIDE.md; new pages must be provided in both Chinese and English - Register the new page in the
sidebarsection ofastro.config.mjs - State what changed and which official sources it relies on
Writing Guidelines
Section titled “Writing Guidelines”File Format
Section titled “File Format”- Use
.mdfor plain text tutorials; use.mdxwhen component interaction is needed - Use English kebab-case for file names:
dnf-basics.mdx - Every file must have
titleanddescriptionfrontmatter
Command Examples
Section titled “Command Examples”$prefix indicates a regular user;#indicates root- Prefer using
sudoover switching to root - Add a
titleto each code block explaining its purpose - Note the applicable distribution and version
- Address the reader as “you”
- Keep paragraphs short — no more than 5 lines each
- Avoid using two admonitions in a row
- Use consistent terminology: DNF, SELinux, systemd, firewalld, NetworkManager
Content Structure
Section titled “Content Structure”Recommended structure for tutorial pages:
- One-sentence introduction
- “What you will learn” list
- Prerequisites
- Step-by-step body
- Common questions
- Further reading
For detailed guidelines, see WRITING_GUIDE.md in the project.
Local Development
Section titled “Local Development”$ npm install$ npm run devVisit http://localhost:4321/ in your browser to preview.
$ npm run build