Help write the manual you wish you'd had.

If you've ever explained something to a teammate and watched it click - that explanation belongs here.

The Missing Manual is open and community-written. Every guide is plain Markdown, so contributing is mostly writing clearly and opening a pull request.

How it works

1. Guides live as Markdown in the guides/ directory - one folder per guide, one file per phase.
2. Each file carries simple front-matter: title, category, difficulty, and a one-line summary.
3. Write the guide, open a pull request, and it goes through review for accuracy and voice.

The voice

This is the whole point, so it's worth getting right:

• Human-friendly. Write like you're explaining it to a smart friend, not lecturing a room.
• Example-driven. Show the real command, the real output, the real gotcha - not abstractions.
• No hand-waving. If a thing is confusing, say why it's confusing, then make it un-confusing.
• Phased. Build understanding in order; each phase earns the next.

What we need most

Web Fundamentals is the newest category and still filling in - HTML, CSS, and how the browser actually works, ahead of any framework. If you can explain the DOM or the box model without hand-waving, that's the gap to fill.

Beyond that: most categories are built out end to end but could go deeper. Advanced, "go deep" material past the beginner path is always welcome - the harder half of a topic, not just the first day of it. So are sharper cheat sheets and small build-along projects.

Not sure what to write? Readers request specific guides that don't exist yet - ping us and we'll point you at one waiting in the queue.

You don't need to be famous. You need to have been confused by something, figured it out, and be willing to save the next person the trouble.