Operationally grounded product domain
• Features map to concrete dispatch and field coordination needs, not abstract dashboard metrics.
Developers
CrowdCAD is an open-source dispatch project with real event medicine use cases and room for both incremental and ambitious contributions.
Operational Fit
- Developers interested in underserved operational software niches with direct field impact.
- Technical teams supporting event medical organizations and operations.
- Contributors who want practical work spanning UX, data flow, deployment, and documentation.
How CrowdCAD Helps
Open roadmap and release visibility
• Roadmap and changelog pathways are public, so contributors can align work with active priorities.
Range of contribution depth
• The project supports quick improvements and deeper architectural work in the same ecosystem.
Feedback loop from real users
• Operational users provide practical input that can guide implementation quality and relevance.
Recommended Setup
Contributors can start by reading docs and roadmap context, then pick scoped work through contributing guidance and community discussion. For local experimentation, begin with Lite Mode flows. For deeper infrastructure work, evaluate self-hosted paths.
Feature Highlights
- Frontend and interaction improvements for dispatch and event setup.
- Maps and location UX enhancements for practical venue operations.
- Deployment and devops workflow improvements for self-hosted teams.
- Documentation quality improvements for operators and maintainers.
- Data/privacy architecture improvements scoped to event operations.
- Internationalization and terminology improvements for broader global usage.
Contribution areas
- • Frontend and UI implementation
- • Maps and location interaction UX
- • Docs and information architecture
- • Deployment and devops workflows
- • Data and privacy architecture
- • Internationalization
- • Operational feedback from EMS and first-aid users
Where to start
- 1. Read the docs and roadmap to understand current priorities.
- 2. Review the changelog to see recent implementation direction.
- 3. Pick a scoped issue or propose improvements through community channels.
- 4. Align documentation and release notes with source-of-truth content from the public repo submodule.
Source-of-truth content note
Public release, changelog, and docs sourcing should align with the actual public CrowdCAD repository through the submodule-backed content abstraction in later stages.
Expected source paths: core, core/CHANGELOG.md, and core/docs.
Privacy and Deployment Note
Contributions that touch data flow, storage, or access control directly shape each deployment's privacy posture. CrowdCAD does not provide HIPAA or other compliance guarantees out of the box, and privacy posture depends on the implementation and environment controls an adopting organization chooses, not generic claims. When proposing schema, backend, or architecture changes, check how the change behaves across both supported backends (Firebase and self-hosted PocketBase), and review docs/privacy and docs/self-hosting for the governance questions organizations are expected to evaluate before adopting it. Deployment, data-handling, and compliance decisions remain the responsibility of each adopting organization, not the project.