Article Bundle Laravel Package

Product Decisions This Supports

• Build vs. buy for editorial content: evaluates whether to adopt a pre-built “article overview/detail” content section versus modeling Article + Category + listing pages ourselves. Given the package’s state, the decision it most strongly supports is build or buy elsewhere — but it’s a useful reference point for scoping what an article module must contain (listing/overview page, detail page, routing, admin scaffolding).
• Stack-fit gate for the roadmap: this is a Symfony 2-era Kunstmaan CMS bundle, not a Laravel package. That makes it a live input to the “do we standardize content tooling on Laravel or adopt a Symfony/CMS dependency?” decision — and argues for keeping the content layer framework-native.
• Time-boxed content-marketing features: if the roadmap needs a blog/news/press section for a marketing site, this shows the minimum viable surface area (overview template, detail template, generator-driven scaffolding) so we can price an in-house build instead of paying for a CMS migration.
• Technical due-diligence precedent: 10 stars, 0 dependents, last release April 2014, no security posture — a clean example for a “maintenance health” checklist we apply to every third-party evaluation.
• Deprecation/legacy triage: if any existing property is on Kunstmaan, this is evidence for a migration plan off Symfony 2.x rather than an investment target.

When to Consider This Package

Consider it only when all of the following hold:

• The application is already a Kunstmaan CMS / Symfony 2.x codebase and you are not migrating soon.
• You specifically want the KunstmaanGeneratorBundle workflow to scaffold an overview/detail article section quickly.
• The content need is genuinely simple: static-ish editorial pages, no workflow, no multichannel delivery, no modern SEO/i18n requirements.
• You accept unmaintained code — no PHP 8 support, no security patches, no community to lean on.

Look elsewhere (or build) when:

• The stack is Laravel — this bundle will not integrate; a native Article model + Eloquent resources + Filament/Nova admin is cheaper than any bridging work.
• You need maintained dependencies, PHP 8.x, Composer audit-clean installs, or a supported LTS path.
• You need headless/API-first content for web + app + email, or editorial workflow, scheduling, versioning, previews.
• You need SEO, structured data, localization, or taxonomy beyond a flat listing.
• The content section is on a revenue or brand-critical surface where an abandoned dependency is unacceptable risk.

For a Laravel product, the realistic shortlist is: build a small in-house content module, or adopt a maintained CMS (Statamic, Craft, or a headless option like Strapi/Contentful) — not this bundle.

How to Pitch It (Stakeholders)

For executives: This package promises an article/news section for a website, but it is an abandoned Symfony CMS add-on from 2014 with a negligible user base and zero dependent projects. It does not fit our Laravel stack and carries unpatched security and compatibility risk. Recommendation: do not adopt. The cost of adoption is not the install — it’s the inevitable rewrite.

For engineering: It’s a Kunstmaan CMS bundle, framework-mismatched and unmaintained; treat it as a design reference for what an article module needs (overview list, detail view, admin scaffolding), not a dependency.

The decision we’re asking for: approve a small in-house content module (or a short evaluation of one maintained CMS) and close out this package as “reviewed, rejected,” with the criteria documented so we don’t re-litigate it next quarter.