#Contributing to ContentVeritas
We welcome contributions to ContentVeritas Technologies! Whether you're fixing bugs, improving documentation, or building new features, your help makes a difference.
- Be respectful and inclusive
- Focus on clear, useful, and testable contributions
- Follow code style conventions for the language (Python, JS, etc.)
- File issues before starting large features
- Fork the repository
- Clone your fork:
git clone https://github.com/your-username/repo-name cd repo-name - Create a feature branch:
git checkout -b feature/your-feature-name
- Make your changes (be sure to test!)
- Commit and push:
git add . git commit -m "Add: brief description of change" git push origin feature/your-feature-name
- Open a pull request with a clear summary and reference to issues (if applicable)
| Repo | Standards |
|---|---|
python-sdk |
Follow PEP8 |
javascript-sdk |
Use ESLint defaults or extend Airbnb |
api-docs |
Use valid Markdown and JSON examples |
examples |
Keep code short, well-commented, and language-idiomatic |
Use meaningful commit messages and submit small, focused PRs.
- Lint and format your code before submitting
- Include unit or integration tests where appropriate
- Use
.env.examplefor any required configuration
If you discover a security vulnerability, please DO NOT submit an issue or PR.
Instead, report it privately to security@contentveritas.com and we'll coordinate a response.
- General: contact@contentveritas.com
- API Support: api-support@contentveritas.com
- Documentation: docs.contentveritas.com
Thank you for helping make ContentVeritas better!