demos-europe/demosplan-core
Core library for demosplan, an open-source digital participation platform used in urban planning and public consultation. It provides shared domain models, services, and workflow logic for managing procedures, statements, and planning documents in PHP applications.
demosplan-core is a working implementation of the domain behind formal public consultation — statement capture, categorization/clustering, document publication, procedure phases, participant roles, map/geo layers, and export of decision records. It's a concrete scoping baseline for anyone building a "Statements / consultation" feature, letting the team size effort against reality rather than a whiteboard.NOASSERTION plus an 11-star public repo means the decision is less "should we composer require this" and more "is the DEMOS ecosystem (not this repo) the right base, and who supports it long-term?" Drives due diligence on the underlying EUPL-style copyleft license and vendor/partner availability.Consider it when:
Look elsewhere when:
To executives: demosplan-core is a publicly funded, working implementation of a legally mandated consultation workflow used in German public administration. We are not proposing to adopt it as a dependency. We are proposing to use it as a reference architecture, which buys three things: (1) a de-risked feature scope sized against a real product rather than estimates; (2) avoidance of re-learning compliance, accessibility, and audit requirements the hard way; (3) a credible build-vs-buy baseline we can take to procurement or to a delivery partner. The two risks — ambiguous licensing (NOASSERTION, needs legal review) and a small public maintenance footprint — both argue for study and selectively fork, not ship-and-depend. Note also that it's Symfony, not Laravel, so this is a domain decision, not a stack commitment.
To engineering: treat this as a Symfony/PHP domain model and workflow reference. Most valuable for the statement data model, procedure/phase state machines, and role/permission design. Do not plan on it as a package dependency: no stable public contract, minimal public activity, monorepo structure. Recommend a time-boxed 2–3 day spike to extract the data model and a workflow map into our own spec, plus a parallel legal and architecture review before any code is copied.
How can I help you explore Laravel packages today?