Skip to main content
Voidcore Wiki exists because practitioners share what they know. Every article, correction, and clarification in the wiki was written by someone who ran into the same problem you are solving today and decided to document the solution. You do not need to be an expert to contribute — a small fix to a broken command or a clearer explanation of a confusing step is just as valuable as a brand-new article.

​
Ways to Contribute

​
Suggest an edit to an existing article

The quickest way to improve the wiki is to fix something you notice while reading. At the bottom of every article, click the Edit this page link. Fill in the form describing what you want to change and why. The maintainer team reviews all suggestions and merges accurate ones, usually within a few days.
When you suggest an edit, include the corrected text in your message rather than just describing the problem. “The flag should be -r not -R” is faster to act on than “the flag listed is wrong.”

​
Report an error or outdated information

If something is incorrect but you are not sure of the right fix, open an issue instead. Use the Report an issue link at the bottom of the relevant article and describe:
  • What the article currently says
  • What you expected or observed when you followed the instructions
  • The Linux distribution and version you are running, if relevant

​
Submit a new article

To propose an entirely new article, use the New Article Request form linked in the sidebar under Contributing. Outline the topic, the audience it targets, and a rough list of what you plan to cover. A maintainer will confirm whether the topic fits the wiki’s scope and assign it so two people are not writing the same thing at the same time.
New articles go through a technical review before publication. Submit a draft even if it is incomplete — early feedback saves time for everyone.

​
Writing Style Guidelines

Follow these conventions so your contribution feels consistent with the rest of the wiki.
  • Write in second person. Address the reader as “you” throughout. Avoid “we”, “the user”, or passive constructions like “it should be noted that.”
  • Use imperative mood for instructions. Start steps with a verb: “Run the following command”, “Open the configuration file”, “Verify the output.”
  • Keep sentences short. Aim for one idea per sentence. If a sentence runs past 25 words, split it.
  • Prefer concrete examples over abstract descriptions. Show the exact command, flag, and expected output rather than describing what the command does in theory.
  • Spell out acronyms on first use. Write “Secure Shell (SSH)” the first time, then “SSH” thereafter.
  • Use code blocks for all commands, paths, and output. Never present a command inline in flowing prose without a code block.
Do not copy content from man pages, other wikis, or third-party tutorials. Paraphrase and verify every command yourself. Plagiarized content will be rejected and removed.

​
What Makes a Good Wiki Article

Strong articles on Voidcore Wiki share a few qualities. They are task-oriented. The title names what the reader can accomplish after following the article — “Configure UFW on Ubuntu 22.04” rather than “UFW Overview.” Readers arrive with a goal; meet them where they are. They state prerequisites upfront. Tell the reader what software version, permission level, or prior knowledge they need before the first step. This prevents half-completed setups and frustrated readers. They verify success. After the final step, show the reader how to confirm that everything worked. A command with expected output, a service status check, or a connectivity test all work well here. They anticipate common errors. Add a Troubleshooting section listing the two or three errors readers are most likely to hit and how to recover from each one. They stay in scope. One article, one task. If covering a topic fully would require fifteen steps across three separate tools, split it into linked articles rather than writing a single sprawling page.

​
The Review Process

After you submit a suggestion, edit, or new article draft, the following process applies:
1

Submission confirmation

Once you submit, you will receive a confirmation that your contribution has been received and is queued for review. Check that your submission includes all the details requested in the form — the more context you provide, the faster the review goes.
2

Technical review

A maintainer reads your contribution and verifies the technical accuracy of every command and claim. They may ask questions or request changes via the submission thread.
3

Style review

A second reviewer checks for consistency with the writing guidelines above. Minor style edits may be applied directly without asking you — you will be credited regardless.
4

Publication

Once both reviews pass, your contribution is merged and goes live. Your name appears in the article’s contributor list at the bottom of the page.
Most contributions are reviewed within three to five business days. High-priority corrections — security-related errors, dangerous commands — are fast-tracked and resolved within 24 hours. Flag your submission as urgent if it falls into this category.