Community guidelines

Be helpful. Be specific. Be kind.

Discuss ideas with respect. Critique the code or approach, not the person. Harassment, discrimination, and personal attacks do not belong here.

Make questions answerable.

Share your djust and Django versions, what you expected, what happened, and a small reproducible example. Use fenced code blocks. Remove secrets and personal data before posting.

Suggest features with context.

Use Feature requests to explain a problem, propose the behavior you want, and share a concrete use case. Mention current workarounds and search existing requests before opening a duplicate.

Show your work.

Share projects you made or have permission to represent. Explain how you used djust, include working links where possible, and credit collaborators. Clearly identify commercial products.

Keep it useful.

No spam, misleading links, or repeated promotion. Search before opening a duplicate discussion. Mark a helpful reply as the accepted answer when it resolves your question.

Moderation and privacy.

Anyone can read published posts. Your first contributions are reviewed before publication. Reports are visible to moderators; previous post versions are visible to their authors and moderators. Published screenshots are public files. Never post credentials, confidential data, or material you do not have permission to share.

Moderators may hide posts, lock discussions, and suspend posting access. Use the Report link to ask for a review.