Community

Community Guidelines

Last reviewed by the STATE team in May 2025

STATE is built on critique — honest, direct, and useful. These guidelines exist to keep that standard high. Not to protect feelings, but to protect the quality of feedback that makes everyone's work better.

1. Critique the Work, Not the Person

Every piece of feedback should be about the design — not the designer. Attack the problem, not the person who made it.

Do:

• Point to specific elements: layout, hierarchy, color, flow, copy
• Explain why something isn't working, not just that it isn't
• Offer a direction to try, even if you're not sure it's right

Don't:

• Make personal comments about taste, style, or ability
• Write one-line dismissals with no substance ("this is bad")
• Use sarcasm or condescension

2. Be Specific

Vague feedback is not as helpful. "Looks good" and "doesn't feel right" are not constructive.

The critique form has three prompts for a reason: what's working, what's not, and what to try. Using all three is recommended.

3. Post Real Work

STATE is a place to practice getting things wrong the first time. Post things you actually want feedback on — works in progress, experiments, problem areas.

Don't post:

• Work that isn't yours
• AI-generated output without disclosure
• Screenshots of other designers' work without permission
• Placeholder or dummy projects with no intent to engage

4. Engage Back

If someone critiques your work, acknowledge it. You don't have to agree, but you should respond.

5. No Promotion

STATE is not a marketing channel. Don't use it to:

• Recruit for your agency
• Sell products or services
• Promote your own tools, apps, or side projects without context

6. Enforcement

Violations are handled by the STATE moderation team. Depending on severity:

• First offense: warning
• Repeated or severe violations: account suspension

If you see something that violates these guidelines, use the flag button on any project or critique. We review all reports.