Community guidelines

1. Keep it about building for the web

Ask about HTML structure, semantic markup, forms, accessibility, images, tables, metadata, embeds, and debugging. CSS and JavaScript are welcome when they help explain an HTML problem. Choose the closest category so the right people can find your question.

2. Make your question easy to reproduce

• Search existing discussions before starting a new one.
• Write a specific title: “Why is my label not focusing the input?” is more useful than “Help please.”
• Explain what you expected, what actually happened, and what you have tried.
• Include the smallest HTML example that still shows the problem. Add the relevant CSS or JavaScript only when needed.
• Mention your browser, device, and any console or validation error that matters. A screenshot can support the explanation; include the code as text too.

3. Share readable code, not private information

Use code formatting and keep indentation readable. Replace private values with placeholders before posting. Never include passwords, API keys, session cookies, database credentials, private customer information, or someone else’s contact details. Check screenshots and linked demos for the same information.

If you accidentally expose a secret, revoke or rotate it with its provider and contact support@htmlcoderunner.com with the post URL. Editing a public post alone does not make an exposed credential safe again.

4. Explain your answer

Answer the actual question, explain why the solution works, and include a focused example when useful. State any assumptions, required server code, browser limitations, or security implications. Prefer accessible native HTML controls and keep client-side validation separate from server-side validation.

Link to relevant documentation and summarize the point that answers the question. A link without an explanation, or the same generic reply posted across many topics, is not a useful answer. If you are unsure, say what still needs checking.

5. Be patient and constructive

Beginners and experienced developers are equally welcome. Critique the code or explanation rather than the person. Ask for missing details kindly. Harassment, threats, hate, personal attacks, and repeated unwanted contact are not welcome. Do not pressure members to provide private support or immediate replies.

6. Keep authorship honest

Share your own work or material you have permission to use, and credit sources. Do not impersonate another person, create accounts to manufacture agreement, invent test results, or describe generated examples as personal experience.

If AI tools helped write a substantial answer, disclose that help and check the answer before posting. Our own HTML learning guides are clearly attributed to HTMLCodeRunner Editorial as AI-assisted teaching material. They are not independent member conversations. Corrections are welcome.

7. No spam or harmful demonstrations

Do not post bulk promotions, unrelated links, affiliate spam, copied keyword-heavy replies, phishing, malicious scripts, or downloads intended to harm others. A relevant link to your own project is fine when it helps answer the question and you explain your connection. Do not repeatedly promote the same link.

Use harmless, isolated examples when discussing security. Never target another person’s account or website, request stolen credentials, or publish private access details.

8. Help keep discussions useful

Keep follow-ups in the original topic when they concern the same problem. Explain what fixed your issue so the next reader can learn from it. Start a new discussion for a different problem and link back for context. Avoid duplicate threads, unrelated replies, and repeated bumps.

9. Moderation and account access

Administrators and moderators may edit, move, close, or remove contributions that break these guidelines, expose private information, or disrupt the community. Depending on the issue, an account may be restricted, banned, or deleted. A ban blocks account access and posting; existing contributions can remain visible.

If you disagree with a moderation decision, email support@htmlcoderunner.com with your username, the relevant URL, and a concise explanation. Do not create another account to bypass a restriction. Never include your password in a support request.

10. Report a problem or request a correction

For spam, harassment, exposed private information, account concerns, or an incorrect guide, contact support. Include the discussion or profile URL and explain what needs attention. Avoid reposting the harmful or private material in another public thread.

Read our editorial approach and forum privacy notice for more about how the community works. Ready to contribute? Start with one clear HTML question.