# Contributing

Thank you for your interest in contributing to the **Zabbix Enterprise Monitoring Guide**.

This project aims to provide clear, technically accurate and enterprise-focused documentation for designing, operating and maintaining Zabbix monitoring environments.

---

## Ways to Contribute

Contributions are welcome in the following areas:

- technical corrections;
- documentation improvements;
- grammar and language corrections;
- clarification of existing recommendations;
- updated monitoring practices;
- additional enterprise considerations;
- broken link reports;
- outdated information reports.

---

## Documentation Principles

Contributions should follow these principles:

- prioritize technical accuracy;
- use clear and professional English;
- focus on enterprise environments;
- explain the reasoning behind recommendations;
- avoid unnecessary complexity;
- minimize version-specific configuration examples;
- remain consistent with the existing structure and tone;
- avoid customer-specific or confidential information.

---

## Before Submitting

Before opening a Pull Request, please:

1. Review the existing documentation.
2. Confirm that the proposed change is not already covered.
3. Verify technical claims against reliable sources.
4. Check Markdown formatting and internal links.
5. Keep the contribution focused on a specific improvement.

Small and clearly defined changes are preferred over large unrelated modifications.

---

## Pull Requests

Each Pull Request should include:

- a clear title;
- a concise description of the change;
- the reason the change is needed;
- affected chapters or files;
- supporting references where applicable.

Pull Requests may be revised or rejected if they:

- introduce inaccurate information;
- conflict with the project's enterprise focus;
- rely excessively on version-specific details;
- contain unrelated changes;
- reduce documentation consistency.

---

## Issues

Use GitHub Issues to report:

- technical inaccuracies;
- outdated recommendations;
- missing information;
- broken links;
- unclear sections;
- unsafe guidance.

When opening an Issue, include:

- the affected file or chapter;
- a description of the problem;
- the expected correction;
- supporting information where available.

---

## Security-Related Findings

Potentially unsafe or incorrect security recommendations should be reported according to the process described in [SECURITY.md](SECURITY.md).

Avoid publishing sensitive operational information or production credentials.

---

## Contribution Review

All contributions are reviewed for:

- technical accuracy;
- clarity;
- relevance;
- consistency;
- operational safety;
- long-term maintainability.

Submission of a contribution does not guarantee acceptance.

---

Thank you for helping improve the Zabbix Enterprise Monitoring Guide.