First off, thank you for considering contributing to the Word Counter Vault! It's people like you who make the open-source community such an amazing place to learn, inspire, and create.
By participating in this project, you agree to maintain a professional and respectful environment for everyone.
- Check the Issues tab to see if the bug has already been reported.
- If not, open a new issue. Clearly describe the problem, including steps to reproduce the bug and your operating system/browser details.
- Open an issue with the tag
enhancement. - Explain the "Why" behind the feature and how it would benefit users.
- Fork the repository.
- Create a branch for your feature (
git checkout -b feature/AmazingFeature). - Commit your changes (
git commit -m 'Add some AmazingFeature'). - Push to the branch (
git push origin feature/AmazingFeature). - Open a Pull Request.
- Database Seeding: If you modify
word_data.json, you must run the seeding script (python -m counter.services.seed_origins) to verify the DuckDB file updates correctly. - Environment: Ensure you are using a virtual environment and update
requirements.txtif you add new dependencies. - Style: Follow PEP 8 guidelines for Python code.
Before submitting a PR, please ensure:
- The Django server starts without errors.
- The DuckDB etymology lookup returns results for standard test words (e.g., "house", "logic", "banana").
- PDF and Word exports generate correctly.
If you have any questions, feel free to open an issue or contact the maintainer at [reory35@hotmail.com].