Weave Code
Demosplan Core Laravel Package
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 is a web application for public participation in planning processes
Frequently asked questions about Demosplan Core
- Is demosplan-core a Laravel package or a Symfony/Doctrine domain core?
- demosplan-core is best understood as the domain core of the DEMOS Plan participation platform, not a thin Laravel utility. Its lineage is Symfony/Doctrine-oriented, and the package carries workflows for procedures, statements, roles, documents, maps, and publication processes. If the current release is Laravel-native, verify the service provider, config publishing, and migration story instead of assuming Eloquent models exist.
- What is demosplan-core used for?
- It supports formal digital participation and public consultation, especially German urban planning and Bauleitplanung workflows. The domain covers procedures, statements (Stellungnahmen), planning documents, roles, publication workflows, and map or GIS bindings. It is relevant when you are building a governed participation product, not when you need a generic PHP helper library.
- How do I install demosplan-core with Composer?
- Install it with composer require demos-europe/demosplan-core, but treat installation as only the first step. Because the package is an application core, you should expect host-application assumptions around routing, authentication, persistence, file storage, search, and mail. Stand up the documented DEMOS Plan environment in a container before attempting to wire it into an existing application.
- Does demosplan-core support Laravel 10 or 11?
- The context does not confirm a supported Laravel version matrix, and the historical orientation is Symfony/Doctrine rather than Laravel/Eloquent. Confirm the framework reality and PHP version support from the upstream composer.json, CI, and release notes before planning a Laravel 10 or 11 integration. Do not assume Laravel service-provider auto-discovery or publishable migrations.
- What license does demosplan-core use, and can I use it commercially?
- GitHub reports NOASSERTION, meaning no recognised standard license was detected in the repository metadata. For a public-sector-adjacent codebase this may be EUPL-1.2, a bespoke arrangement, or another vendor-specific license, but you must not assume permission. Treat legal clearance as a hard gate before reading the code into your repository or distributing a derivative, and confirm commercial and closed-redistribution rights in writing.
- What runtime dependencies does demosplan-core require?
- Expect a database schema owned by the core plus external services such as search indexing, object storage, mail, queue workers, and map or tile services. GIS and PostGIS requirements are plausible given the map bindings, but exact versions must be confirmed from upstream documentation. A faithful deployment is closer to running the DEMOS Plan application than installing a single Composer dependency. GDPR/DSGVO handling of citizen submissions and BITV accessibility obligations are likely inherited rather than optional.
- Can I embed demosplan-core inside an existing Laravel application?
- Embedding is technically possible only after confirming the framework and ORM alignment, but it is moderate-to-poor as an in-process dependency. You would be accepting the core's database schema and request lifecycle inside your Laravel app, which creates upgrade and transaction-boundary risk. A sidecar or standalone DEMOS Plan deployment integrated over HTTP or events is materially less risky.
- How should I integrate demosplan-core with Laravel?
- Prefer runtime separation: let DEMOS Plan own its schema and domain lifecycle while your Laravel application owns identity, presentation, and surrounding business logic. Integrate through a documented HTTP or API boundary if one exists, with events or queues for asynchronous work. Use a strangler-style rollout rather than a lift-and-shift into Laravel.
- Is demosplan-core production-ready and actively maintained?
- It comes from a running public-participation platform, so the domain logic may be production-used, but 11 GitHub stars indicates a vendor-published product codebase rather than a community-maintained library. Expect vendor-paced releases and thin third-party documentation. Check test coverage, CI status, release cadence over the last 12 months, and commercial support terms from demos-europe before committing.
- What are alternatives to demosplan-core for participation workflows?
- If you do not need DEMOS Plan's specific German planning and consultation domain, a purpose-built Laravel workflow for procedures, submissions, and document publication may be simpler to own. Running DEMOS Plan as a standalone service and integrating via API is the closest alternative when you want its domain logic without embedding it. Other participation platforms may fit broader civic engagement cases, but compare licensing, GDPR obligations, accessibility, and hosting requirements before choosing.
Weaver
How can I help you explore Laravel packages today?