← DevManiac

Community Guidelines

How we keep DevManiac a place worth building in public.

Last updated · May 28, 2026

1. What DevManiac Is For

DevManiac exists so your real work can speak for you. Here, your build history is your portfolio — the commits, the projects, the messy middle, the things you shipped. That only works if the community treats the place with care.

These guidelines describe the kind of community we’re building. They work alongside our Terms of Service, which set the binding rules. When in doubt, build in good faith and treat other developers the way you’d want your own work treated.

2. Keep It Real

Authenticity is the whole point. Your build history should reflect work you actually did.

  • Show real projects and honest progress — including the rough parts.
  • Don’t fabricate, inflate, or manipulate commits, contribution activity, or other portfolio signals.
  • Don’t pass off someone else’s work as your own. Forking, following a tutorial, or building on a template is fine — claiming you wrote it from scratch is not.

3. Give Credit

Good developers stand on others’ shoulders and say so.

  • Attribute code, designs, and ideas you borrow. Link the source when you can.
  • Respect open-source licenses — honor attribution, copyleft, and other terms of any code you reuse or publish.
  • Don’t post code you don’t have the right to share, including an employer’s or client’s proprietary or confidential work.

4. Build Each Other Up

The best part of building in public is the feedback. Make it the kind people want to receive.

  • Critique the code, not the coder. Be specific and constructive — point at the line, suggest the fix.
  • Assume good intent, especially with beginners. Everyone’s build history starts somewhere.
  • Share what you learned, not just what you shipped. Process helps the next person.

5. Respect People

There’s no version of this community that includes the following:

  • Harassment, threats, bullying, or sustained targeting of any individual.
  • Hate speech or discrimination based on who someone is.
  • Posting someone’s private information (doxxing) or impersonating others.

6. Keep It Safe

This is a place for builders, not for harm.

  • No malware, exploits, or code designed to attack, deceive, or gain unauthorized access to systems.
  • Don’t use the platform to leak secrets, credentials, or stolen data.
  • If you find a security issue in DevManiac itself, please report it privately to [report@DevManiac.dev] rather than posting it publicly.

7. Don’t Game the System

Reputation on DevManiac should be earned. Don’t shortcut it.

  • No spam, mass self-promotion, or unsolicited advertising.
  • No fake engagement — vote rings, star/follow manipulation, bot accounts, or coordinated inauthentic activity.
  • No scraping, crawling, or bulk-harvesting data, and no circumventing rate limits or access controls.

8. Keep It On-Topic & Appropriate

DevManiac is a developer community. Keep content relevant to building and learning. No sexually explicit material, no content promoting violence or illegal activity, and no flooding feeds with off-topic noise. We’d rather have a focused community than a loud one.

9. Reporting & Enforcement

If you see something that breaks these guidelines, report it — use the in-product report option where available, or email [report@DevManiac.dev]. Reports are reviewed and kept confidential where possible.

Depending on severity and context, we may issue a warning, remove content, limit features, suspend an account, or — for serious or repeated violations — permanently remove it. We aim to be fair and proportionate, and we may act immediately when there’s a risk to people or the platform. These actions are taken under our Terms of Service.

10. A Final Word

Rules can only do so much — the rest is on all of us. Ship honest work, give credit generously, help the person a few commits behind you, and assume the best of each other. That’s the community worth building in public.