Why contribute
Zig is evolving quickly, and so are the ways we teach and learn it. Contributions help keep examples current, refine explanations, and surface perspectives from real Zig users building real projects.
Ways to contribute
- Fix typos, broken links, or formatting issues in existing chapters.
- Suggest clearer explanations for tricky concepts or edge cases.
- Add small, focused examples or exercises that reinforce the text.
- Report bugs or confusing behavior in sample code.
- Propose improvements to the Zigbook site UI and developer experience.
How to contribute
Contributions happen through GitHub. You can start small by opening an issue, or dive in with a pull request if you already have a concrete change in mind.
Content standards
Human-written chapters only
Zigbook's chapter text is written and edited by humans. While UI code and tooling around the book may use automation, AI-generated chapter content is not accepted.
When proposing edits, aim to preserve the existing voice: concrete, practical, and slightly opinionated. Clear explanations, well-documented code, and good tests are always welcome.
Community & support
Zigbook lives alongside the broader Zig community. If you have language questions, performance puzzles, or want to share a project, you might also enjoy these spaces:
- Ziggit – community forum for Zig discussions.
- Zig compiler discussions – design notes, proposals, and deep dives.
- ziglang.org/learn – official learning resources.
If you're not sure whether an idea fits Zigbook, open an issue and start a conversation. Early feedback is encouraged.