Thank you for your interest in contributing to Journify! We welcome community contributions to make Journify the most dependable, private, and distraction-free journaling app.
Please take a moment to review this guide before submitting issues or pull requests.
By participating in this project, you agree to abide by our Code of Conduct. Please treat everyone with respect and kindness.
- Search existing GitHub Issues before opening a new one to avoid duplicates.
- Clearly describe the issue, the reproduction steps, expected behavior, and actual behavior.
- Include browser/operating system environment details if relevant.
- Open an issue tagged
enhancement. - Describe the motivation behind the suggestion and provide mockups or user workflow examples when applicable.
- Fork the repository and create your branch from
main:git checkout -b feature/amazing-feature
- Install dependencies:
npm install
- Ensure local development works cleanly:
npm run dev
- Verify TypeScript and production builds:
npm run build
- Follow our commit message guidelines (e.g. Conventional Commits:
feat:,fix:,docs:,perf:). - Open a Pull Request pointing to the
mainbranch with a clear title and description of the changes.
- TypeScript: Strict typing is enabled. Avoid
anytypes wherever possible. - Code Style: Follow ESLint and formatting standards present in the repository.
- Privacy & Security: Never log sensitive user journal content or personal authentication tokens.
- Offline-First Resilience: Any features altering data persistence must respect the
IndexedDBandSyncEnginearchitecture.
By contributing to Journify, you agree that your contributions will be licensed under the project's MIT License.