Contribute an article
Project Homelab only works if people who run labs write down what they learned. You don’t need to be an expert or a good writer. If you’ve built it, broken it or fixed it, that’s worth an article.
Every page is a plain text Markdown file in a public GitHub repository. You suggest a change, a maintainer reviews it, and once it’s merged the site rebuilds by itself, usually within a few minutes. That review step is what keeps spam off the site.
Fix or improve an existing page
Section titled “Fix or improve an existing page”-
Scroll to the bottom of the page and select Edit page. This opens the page’s file on GitHub. Sign in or create a free account if you’re asked.
-
Make your changes in the editor. Select Preview to check how they look.
-
Select Commit changes…, describe what you changed in a sentence, and choose Propose changes. GitHub copies the project to your account behind the scenes.
-
On the next screen, select Create pull request. A maintainer will review it, may suggest tweaks, and merges it when it’s ready.
Write a new article
Section titled “Write a new article”Pick a topic from the list of wanted articles, or anything homelab-related that isn’t covered yet. Then create a new file in the right section folder under src/content/docs/. The links in the wanted list open GitHub with the file already named for you.
Start the file with this header, then write the article below it:
---title: Proxmox VEdescription: One or two sentences that say what the reader will get from this page. Shown in search results.---
Proxmox VE is an open source hypervisor based on Debian…
## Why use it in a homelab
## Hardware it runs well on
## Getting startedThe file name becomes the page’s address, so hypervisors/proxmox-ve.md is published at /hypervisors/proxmox-ve/. The article appears in that section’s sidebar and on the homepage rack automatically.
Article layout
Section titled “Article layout”There’s no strict template, but most hardware and software articles work best with these sections, in this order:
- Introduction: what it is and who it suits
- Pros and cons
- Costs: new, second-hand, and running costs such as power
- Use cases: the kinds of lab it fits
- Known issues and solutions
- Models or versions worth knowing about
Add images to public/media/ and reference them as . Describe the image in the brackets so screen-reader users get the same information.
Ground rules
Section titled “Ground rules”- Write about your own experience. Link to blog posts, vendor docs and videos when they help, but not to drive traffic to your own site.
- Vendors are welcome to write about their own products. Don’t edit articles about a competitor. Anything that reads like advertising will be removed.
- Only legitimate licensing. No piracy, key generators or license workarounds. See the disclaimer.
- Humour and memes are fine. This is a community site, not an encyclopedia. Expect someone to tidy up your formatting or spelling; don’t take it personally.
Wanted articles
Section titled “Wanted articles”These were started on the old wiki but never written. Each one would fill a real gap. Select a topic to start a new file for it on GitHub.
- Start here
- Hardware
- Housing your lab
- Storage
- Networking
- Hypervisors
- Management
- Security
- Cloud labs
- Community
You’ll also find articles marked Unfinished in each section. They have some content but need someone to finish them.
Work on the site locally
Section titled “Work on the site locally”If you’d rather use your own editor, or want to change the site’s design:
git clone https://github.com/projecthomelab/projecthomelab.org.gitcd projecthomelab.orgnpm installnpm run devThen open http://localhost:4321. Pages reload as you save. Run npm run build before you open a pull request to make sure everything still builds.
Report a problem
Section titled “Report a problem”Spotted something wrong but don’t have time to fix it? Open an issue on GitHub or ask on the forums.