Thank you for helping build Hidden in the Mist. These standards keep every contribution accurate, consistent, safe, and maintainable.

🎯 Purpose of the Program

The goal is to publish high-quality, practical, and accurate technical knowledge. Students, professionals, and hobbyists are welcome to contribute. By contributing, you help build a trusted resource and receive public credit for your work.

📜 Required Rules

Failure to follow these rules may result in edits being reverted or contributor access being revoked.

1. 📝 Use Markdown

All submissions must be written in Markdown. Do not submit HTML, Word documents, PDFs, or rich-text content.

Use standard Markdown for headings, lists, tables, inline code, and fenced code blocks:

## Section Heading

Inline command: `ls -la`

```bash
ls -la
```

Include this metadata block at the top of every contributor page:

> **Author:** Name or handle  
> **Difficulty:** Beginner | Intermediate | Advanced  
> **Status:** Draft | Review | Submitted
{.is-info}

2. ©️ Submit Original or Attributed Work

• Content must be your own work, or properly attributed when it references external material.
• Include useful sources in a References section.
• Plagiarism will result in permanent removal of contributor access.

3. ✅ Choose Accuracy Over Speed

• Verify commands, configurations, and technical claims.
• State relevant operating systems, versions, assumptions, and environments.
• Clearly label anything experimental or untested.

4. 🤝 Keep a Professional Tone

• Do not use offensive language, personal attacks, or gatekeeping.
• Avoid excessive opinion unless it is clearly identified as commentary.
• Write as a technical reference, not a social-media post.

5. 🛡️ Protect People and Systems

• Do not submit malware intended for real-world harm.
• Never include leaked credentials, private data, or exploit kits.
• Educational security research is permitted only when framed responsibly.

6. 🗂️ Follow the Wiki Structure

• Do not restructure core directories without approval.
• Place content in the correct category.
• Keep each page focused and appropriately scoped.
• If you are unsure where something belongs, begin in Contributor Drafts.

⭐ Best Practices

• Assume the reader is technical, but does not know your environment.
• Explain why, not only how.
• Prefer clarity over cleverness.
• State prerequisites before the procedure.
• Use screenshots sparingly; the text should stand on its own.
• Validate links, rendering, and copy-and-paste safety before submission.

🧱 Suggested Page Structure

> **Author:** Name or handle  
> **Difficulty:** Beginner | Intermediate | Advanced  
> **Status:** Draft | Review | Submitted
{.is-info}

## 🎯 Summary
Briefly explain the topic, purpose, or objective.

## 📋 Prerequisites
List required access, systems, versions, and tools.

## 🛠️ Content
Organize the procedure or explanation with clear headings,
numbered steps, tables, lists, and labeled code blocks.

## ✅ Validation
Explain how the reader can confirm the expected result.

## 🔗 References
- [Source name](https://example.com)

For a more complete starting point, use the Knowledge Base Article Template.

🏅 Recognition

High-quality contributors may receive:

• Public attribution
• Early access to new features
• Invitations to paid contribution programs
• Future revenue-sharing opportunities

🆘 Need Help?

Review existing pages and the template library, or ask a question in the relevant page’s discussion area. The Contributor Hub explains the complete workflow.