Community guidelines

stackinfolio is a place where developers show what they're building and cheer each other on. Say what you think, freely. Just say it the way you'd say it to someone sitting across the table from you.

• Critique the work, not the person. “The onboarding lost me at step three” helps. “Whoever built this has no idea” doesn't.
• Show your own work. Don't post someone else's project, code or design as yours, even with changes. Credit what you built on. We can't check who made what, so it rests on you (see the Terms).
• No harassment, slurs, threats or pile-ons. Not in replies, not in project names or bios.
• No spam. Replies aren’t a place to promote your own thing. Your profile is.

Think a project copies your work, or someone else's? Email [email protected] with the link and where the original is. A person looks at it; stackinfolio can't settle who made something, but clear copies come down.

Every reply has a Report link. Reports go to a person, not a filter, and nothing is hidden automatically. Project owners can hide replies on their own posts, bring them back, and stop someone replying to them. A reply hidden after a report stays hidden.

First the post is hidden and you hear from us. Keep going and posting gets switched off for a while. Keep going after that and the account is removed. Nothing here is automated, and nothing is permanent on the first mistake.

These guidelines sit alongside the Terms and Privacy Policy. Questions or a report you'd rather not make in public? Use the feedback page.