## CONTRIBUTING GUIDE

### 1. Contribution Philosophy

At ego.cx, we believe the best ideas come from collaborating with people who share our passion for authentic digital identity and well-crafted design.

**Our principles:**
- **Respect** — all voices are welcome
- **Quality** — every contribution must meet our standards
- **Transparency** — the process is open and clear
- **Learning** — contributing is an opportunity to grow

---

### 2. How to Contribute

#### 2.1. Report an Issue
If you find something that doesn't work as expected:

1. Search existing issues to see if it's already reported
2. If not, create a new one with:
   - **Clear title** (max 70 characters)
   - **Detailed description** (what you expected vs. what happened)
   - **Steps to reproduce** (if applicable)
   - **Screenshots** (if visual)
   - **Context** (browser, OS, version)

#### 2.2. Suggest an Improvement
If you have an idea to improve ego.cx:

1. Describe the improvement clearly
2. Explain *why* it's a good idea
3. If possible, provide an example or prototype

#### 2.3. Submit a Pull Request
If you want to contribute code:

1. **Fork** the repository
2. **Clone** your fork locally
3. Create a **branch** with a descriptive name (`feature/new-feature` or `fix/submit-error`)
4. Make your **changes** following the style guide
5. **Test** your changes (unit, integration)
6. **Document** changes in README or comments
7. **Submit** a Pull Request with a clear description

---

### 3. Style Guide for Contributions

#### 3.1. Code
- Follow the rules in `copilot.md / developer.md`
- Use descriptive names for variables and functions
- Keep functions small and focused
- Write tests for new code

#### 3.2. UX Writing / Copy
- Follow the rules in `copy.md / ux-writing.md`
- Use the brand tone: approachable, optimistic, realistic
- Keep sentences short and clear

#### 3.3. Documentation
- Use Markdown for documentation
- Explain *what* the code does and *why* it's there
- Include examples when possible
- Keep documentation updated with changes

---

### 4. Code of Conduct

All participants must:

- **Be respectful** — of ideas, opinions, and people
- **Be constructive** — focused on solutions, not problems
- **Be open** — to different ideas and collaboration
- **Be responsible** — for their words and actions

**Not tolerated:**
- Harassment or intimidation
- Offensive or discriminatory comments
- Toxic or disruptive behavior

Violators will be blocked from the project.

---

### 5. Review Process

1. **Triage:** A team member reviews the issue or PR
2. **Evaluation:** The proposal or changes are validated
3. **Feedback:** Constructive comments are given
4. **Approval:** If it meets standards, it's approved
5. **Merge:** Integrated into the main repository

---

### 6. Recognition

We value every contribution. Contributors will be recognized in:

- The `README.md` of the repository
- Release notes (changelog)
- Our communication channels (with permission)

---

*Last updated: 2026-07-10*

---

*— Fernando José Caicedo Albarello*  
*Founder, EgoCX*