Community guidelines
DevPath is a learning workspace. Contributions should help another person understand a decision, verify a result, or make measurable progress.
Write for learning
- Ask focused questions. Include the relevant context, what you tried, what happened, and the result you expected.
- Explain reasoning instead of dropping an unexplained solution. Help the learner understand how to reach and verify the answer.
- Show evidence with showcases: a working link, reproducible steps, tests, screenshots, or a clear description of the result.
- Cite material you did not create. Do not present copied lessons, roadmaps, code, or project work as your own.
Keep participation safe
Harassment, hateful conduct, threats, sexual exploitation, doxxing, malware, credential theft, spam, deceptive promotion, and instructions intended to cause unauthorized harm are not allowed. Never publish secrets, access tokens, private customer data, or another person's identifying information.
Protect honest assessment
Discuss concepts and review work, but do not impersonate another learner, submit someone else's project as your own, or provide answers intended to bypass an active exam, hiring assessment, or course rule. Feedback should improve the learner's work, not replace it.
How moderation works
Signed-in members can privately report a post or reply with a structured reason and optional context. Moderators review the reported item, may dismiss unsupported reports, or hide content that violates these guidelines. Moderation actions are recorded in an internal audit trail. Reports are not public trust signals and do not increase a contributor's standing.
Questions and appeals
Use the support workflow for questions about a moderation decision. Include the community post title and the decision you want reviewed; do not repost hidden material to contest an action.