Thank you for your interest in contributing to GraceFlow CMS! We welcome contributions from developers, designers, writers, and church tech managers around the globe.
We are committed to maintaining a welcoming, respectful, and encouraging community. Please ensure all interactions adhere to high standards of Christian fellowship, respect, and professionalism.
- Before opening a new issue, check existing issues to avoid duplicates.
- Provide detailed steps to reproduce bugs, including your environment (Node version, browser, database type).
- Suggest new non-financial church management features via GitHub Discussions or Issues.
- Explain the real-world value to local and international ministries.
- Fork the repository and clone your fork.
- Create a topic branch:
git checkout -b feature/membership-export-enhancement
- Make clean, modular commits:
- Write clear, descriptive commit messages.
- Follow standard ESLint and TypeScript rules.
- Ensure code passes build & linting:
npm run lint npm run build
- Push and submit your Pull Request targeting the
mainbranch.
- Clean & Modular: Write self-documenting code with descriptive variable/function names.
- Security First: Never expose private API credentials or raw stack traces. Use sanitization and rate limiting where applicable.
- No Financial Logic: GraceFlow CMS focuses purely on membership, attendance, departments, sermons, and ministry communication.
By contributing to GraceFlow CMS, you agree that your contributions will be licensed under the MIT License.