Contribute a Guide
Help build the world's largest free library of practical knowledge.
How It Works
Every guide on Praxis is written by someone with knowledge and verified by qualified peers. Here's the process:
Write
Create a guide following the B.L.U.E. format and hierarchy rules.
Submit
Submit your guide using the template system.
Verify
A jury of qualified verifiers reviews your guide.
Published
Verified guides go live on the platform.
Guide Requirements
To be accepted, guides must follow these rules:
📚 Follow the Hierarchy
Level N guides can only assume knowledge from Level N-1 and below. Don't skip prerequisites — if a concept is needed, link to the guide that covers it.
🎯 Be Practical
Guides teach how to do things, not just understand them. Include steps, materials, and actionable instructions.
📋 Use the Template
Follow the standard guide template with frontmatter, sections, and method tabs. Consistency makes the site usable.
✓ Be Verifiable
Write about things you actually know. AI-generated content is prohibited — guides must be human-authored and verifiable.
Guide Format
Every guide has:
- Frontmatter — Title, subject, level, author, methods, prerequisites
- Introduction — What this guide covers and why it matters
- Methods — Multiple approaches as tabbed sections
- Steps — Numbered, clear, actionable steps
- Prerequisites — Links to lower-level guides needed
- Next Steps — Links to where to go after completing
Ready to Submit?
All guides live in the content repository on Codeberg. The process is the same as any open-source project: fork, write, PR, review, merge.
Fork the repo
Go to codeberg.org/praxisknowledge/content and fork it to your account.
Write your guide
Create a .md file in the right subject/level directory (e.g. guides/homelab/L2/). Follow the frontmatter schema — title, subject, level, author, prerequisites, methods. See existing guides or the template in internal/templates/ for reference.
Open a pull request
Push your fork and open a PR to the main repo. The PR title should match your guide title. In the PR description, note what subject and level the guide is for.
Review and merge
Verifiers review the PR. They may leave comments asking for changes. Once approved, the PR is merged and the site auto-builds within minutes. Your guide goes live at /subject/guide-slug.
Found a Problem?
If a guide has an error, missing steps, or something that doesn't work, open an issue on the content issue tracker. Include the guide title, what's wrong, and the correct information if you know it.
Small fixes (typos, broken links) can go straight in as a pull request — no need to open an issue first.
Questions?
If you have questions about contributing, check the About page, open an issue on the content issue tracker, or join the discussion on Codeberg.