Add contributing and code of conduct docs for mobile

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: shanerbaner82

resources/views/docs/mobile/3/contributing/_index.md

@@ -0,0 +1,4 @@
+---
+title: Contributing
+order: 70
+---

resources/views/docs/mobile/3/contributing/contributing.md

@@ -0,0 +1,83 @@
+---
+title: Contributing
+order: 1
+---
+
+## Contributing
+
+We welcome contributions to NativePHP for Mobile! Whether it's bug fixes, new features, documentation improvements, or bug reports, every contribution helps make the project better.
+
+### How to Contribute
+
+1. **Fork the repository** on GitHub.
+2. **Clone your fork** locally:
+   ```bash
+   git clone git@github.com:your-username/mobile.git
+   cd mobile
+   ```
+3. **Create a new branch** for your feature or fix:
+   ```bash
+   git checkout -b feature/my-new-feature
+   ```
+4. **Make your changes** and ensure all tests pass.
+5. **Commit your changes** with a clear, descriptive commit message.
+6. **Push your branch** to your fork:
+   ```bash
+   git push origin feature/my-new-feature
+   ```
+7. **Open a Pull Request** against the `main` branch of the NativePHP Mobile repository.
+
+### Pull Request Guidelines
+
+- Keep your changes focused. If you have multiple unrelated changes, please submit them as separate pull requests.
+- Write clear, descriptive commit messages.
+- Include tests for any new functionality.
+- Ensure all existing tests pass before submitting.
+- Update documentation if your changes affect the public API.
+
+### Reporting Bugs
+
+If you discover a bug, please [open an issue](https://github.com/NativePHP/mobile/issues) on GitHub. Include as much detail as possible:
+
+- A clear, descriptive title.
+- Steps to reproduce the issue.
+- Expected behavior vs. actual behavior.
+- Your environment details (OS, PHP version, Laravel version, etc.).
+
+### Security Vulnerabilities
+
+If you discover a security vulnerability, please **do not** open a public issue. Instead, please send an email to [security@nativephp.com](mailto:security@nativephp.com). All security vulnerabilities will be promptly addressed.
+
+## Code of Conduct
+
+The NativePHP community is dedicated to providing a welcoming and inclusive experience for everyone. We expect all participants to adhere to the following standards:
+
+### Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+### Our Standards
+
+Examples of behavior that contributes to a positive environment:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior:
+
+- The use of sexualized language or imagery, and sexual attention or advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+### Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the project team at [conduct@nativephp.com](mailto:conduct@nativephp.com). All complaints will be reviewed and investigated promptly and fairly.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.