Ways to Contribute
- Open an Issue
- Submit a Pull Request
Before opening a new issue, search the GitHub Issues page to see whether someone has already reported the same problem or request.A good issue usually includes:
- a clear title
- background and problem statement
- reproduction steps and environment details
- code snippets, logs, or screenshots when helpful
Development Process
Prepare the environment
Make sure Python 3.12+ and Poetry are installed locally, then install dependencies.
Sync the latest code
Start from the latest upstream code before creating a branch, so you are not building on stale state.
Implement changes and add tests
Add or update tests and documentation for any user-facing behavior change.
If your change affects user workflows, configuration, or example code, update the corresponding documentation pages as part of the same pull request.
Development Environment Setup
Requirements
- Python 3.12 or later
- Poetry
Install development dependencies
Documentation i18n Workflow
Mintlify documentation internationalization is handled by script-driven locale page synchronization.Core idea
Core idea
- Chinese root pages remain the default source docs
- Target language pages are generated under
mintlify_docs/<lang>/... - Scripts can synchronize locale pages and navigation structure in batch
- Missing content can be filled iteratively as translation content improves
Audit current locale coverage
Audit current locale coverage
Sync the English page skeleton
Sync the English page skeleton
Use a model to fill missing segments
Use a model to fill missing segments
Write Mintlify language switcher config
Write Mintlify language switcher config
It is usually best to run an audit or a
--sync-pages pass first so you can verify page structure, locale output, and navigation before refining translated wording.Code Standards
Code style
Code style
Follow PEP 8 and prefer the style already established in the repository.
Type annotations
Type annotations
Add type annotations to new or modified public interfaces whenever practical.
Documentation requirements
Documentation requirements
- Public APIs should have clear docstrings
- Docstring style should stay consistent with the existing codebase
- If a feature changes, update the relevant docs and examples as well
Code of Conduct
Please treat all contributors with respect. Harassment, discrimination, or abusive behavior is not acceptable.Get Help
If you need help while contributing:- ask in GitHub Issues
- contact the project maintainer