Community guidelines
Ask clearly, diagnose with evidence, protect sensitive information, and leave the next reader with something they can safely use.
These guidelines describe the intended Genesis Code Doctor Community standard. Roles, enforcement levels, appeals, response expectations, and emergency procedures must be tested and approved before the forum opens publicly.
Ask. Diagnose. Repair. Verify. Share.
The forum is intended for website diagnostics, SEO and visibility, performance, accessibility, WordPress and plugins, code and development, build ideas, platform questions, and verified lessons from completed work. It is a peer community—not a substitute for private support, security reporting, legal advice, or guaranteed professional services.
Make the problem understandable without exposing the owner.
- Use a specific title and choose the closest category.
- Explain the expected result, actual result, environment, platform, version, and troubleshooting already attempted.
- Include the smallest safe example needed to reproduce or understand the issue.
- Label assumptions and distinguish measured evidence from estimates or guesses.
- Return to confirm what worked, note remaining limitations, and accept the answer that resolved the question when appropriate.
Redact before you post.
Never publish passwords, API keys, access tokens, private keys, cookies, customer records, private analytics, proprietary source code, billing details, unreleased vulnerabilities, server paths, or other information that could expose a person or system.
Assume a public question, answer, username, profile, vote, and attachment can be seen, indexed, quoted, and shared. Use a private diagnostic or support path for material that cannot safely be public.
Critique the work without attacking the person.
- Be accurate, patient, and direct with beginners and experts alike.
- Explain risks and prerequisites before suggesting commands or code that can alter data or production systems.
- Disclose meaningful affiliations, financial interests, and use of generated content where relevant.
- Cite original documentation or evidence when making consequential claims.
- Do not harass, shame, threaten, discriminate, brigade, spam, manipulate votes, or impersonate others.
- Do not post promotional links or solicit business unless the applicable category and rules expressly allow it.
Badges describe review status—not certainty.
| Label | What it should mean |
|---|---|
| Accepted answer | The question author marked it as the answer that helped them; it is not a Genesis guarantee. |
| Community verified | Members provided repeatable evidence under stated conditions. |
| Genesis suggested | An AI-assisted response that remains subject to human review and testing. |
| Expert reviewed | A qualified role reviewed the response within the scope disclosed; it does not create a warranty. |
Consent and scope must stay visible.
A Genesis diagnostic response should run only when requested or clearly authorized, show what was examined, label confidence and limitations, keep private diagnostic evidence private by default, and never execute untrusted community code on the production service. Members must not present AI output as personally tested when it was not.
Report problems; do not escalate them in public.
Members should use the report control for spam, harassment, unsafe instructions, impersonation, privacy exposure, intellectual-property concerns, or other rule violations. Security-sensitive reports should enter a restricted queue. Moderators should preserve reasons and audit records, avoid public disclosure of sensitive evidence, and provide an appeal route where appropriate.
The final enforcement matrix will define warnings, edits, quarantines, content removal, temporary restrictions, suspensions, role removal, and urgent safety action. Until then, no specific response time or outcome is promised.
The same protections apply across Genesis.
Forum participation is also subject to the draft Terms of Service, Privacy Notice, and Acceptable Use Policy. Questions or appeals should use the Support Center once that workflow is available.