Suggestions
In one line: This guide is read-only on the maintainer's side. Suggestions are welcome via GitHub Issues — the maintainer reviews them and decides whether to incorporate them.
How it works
The Modern Web Dev Guide is maintained by a single person. To keep voice and accuracy consistent, the source is not open to drive-by pull requests. But spotting clarifications, factual corrections, and stale "2026" claims is exactly the kind of feedback that makes the guide better — so there's a structured way to submit those.
📝 To submit a suggestion
- Click the button below. It opens a pre-filled GitHub issue with a short form.
- Fill in: which page, what kind of suggestion, what you'd change, and why.
- Submit. You'll get notified if/when the change lands.
→ Open a suggestion on GitHub
You'll need a free GitHub account. There's no other way to submit — this isn't a bottleneck, it's a deliberate filter.
What gets a quick "yes"
- Typos and broken links. Almost always merged.
- Factual corrections with a source. "Vercel's free tier is now X, see [link]" — merged once verified.
- Out-of-date claims. The guide is reviewed periodically (last review: May 2026). If a tool/price/version has shifted, please flag the specific sentence.
- Clarification requests. If a paragraph confused you, that's a signal — saying "I read this three times and didn't get it" is useful even without a proposed fix.
What gets a "thanks, but no"
- Stylistic preferences ("I'd phrase this differently") — the maintainer holds the voice intentionally.
- Adding niche tools. The guide focuses on the dominant 2026 choices; "you should mention X" usually doesn't fit unless X has clearly become mainstream.
- Whole new chapters or restructuring. Open a discussion first; that's a much bigger conversation than a single issue.
- Drive-by pull requests. Please don't open a PR without first opening an issue and getting an explicit ack. They'll be closed.
See existing suggestions
You can browse what others have already suggested (and what's been merged or rejected) here:
Reporting something else
| Kind | Where |
|---|---|
| Suggestion / correction | Open a suggestion issue |
| Site bug (broken link, layout) | Open an issue and label it bug after submission |
| Security concern about the site | Use GitHub's private security advisory — please don't open a public issue |
Thanks for caring enough about the guide to suggest something. Keeping it accurate and beginner-friendly is a moving target, and outside eyes catch things the maintainer can't.