Frontend and UI
Interface clarity, interaction design, and workflow usability improvements.
Contributing
CrowdCAD welcomes practical contributions from developers and operational teams. Useful contributions include code, documentation, deployment guidance, feature suggestions, and workflow feedback from real events.
How people contribute
- • Code contributions across frontend, workflow, and architecture improvements.
- • Documentation updates that make setup and operations clearer.
- • Bug reports and reproducible issue descriptions.
- • Feature suggestions tied to practical operational needs.
- • Event workflow feedback from EMS and first-aid organizations.
Contribution categories
Multi-dispatch workflows
Coordination patterns, role clarity, and shared-board improvements for multiple dispatchers.
Field login and team correspondence
Field-team login, messaging, and communication workflow improvements.
Mobile experience
Responsive behavior and field-focused mobile interaction quality.
Docs and onboarding
Clear setup guidance, glossary improvements, and practical onboarding content.
Deployment and self-hosting guidance
Operational deployment docs, setup tradeoffs, and maintainable host guidance.
Privacy and data-handling clarity
Language and documentation clarity around data responsibilities and deployment tradeoffs.
Internationalization and localization
Language and regional support improvements for broader organizational adoption.
Operational feedback from EMS and first-aid teams
Real workflow feedback from organizations using or evaluating CrowdCAD during events.
Where to start
- • Review good-first issues and scoped tasks in the public repository.
- • Pick small UX or documentation fixes to learn project patterns.
- • Align larger feature work with roadmap themes where practical.
- • Open a discussion if your organization has a workflow need not yet represented.
Contribution principles
- • Build for real volunteer operational needs.
- • Keep workflows clear under event conditions.
- • Prefer improvements that can help more than one organization when possible.
- • Document tradeoffs and assumptions clearly.
Working from your organization's fork
Many teams adapt CrowdCAD to local constraints. When possible, upstream improvements that may benefit other volunteer organizations, especially in workflow clarity, reliability, and documentation.
Upstream sharing helps reduce duplicated maintenance burden across organizations and improves the baseline for future adopters.
Related links
Source-of-truth note
Release history and selected project documentation are sourced from the public CrowdCAD repository submodule when available.