Product Decisions This Supports

SEO/discoverability roadmap: A sitemap widget is a table-stakes SEO feature for CMS/page-builder products. This package is useful mainly as a reference for widget scope — page inclusion rules, URL generation, and admin UX — not as a production dependency.
Build vs. buy vs. adopt: With 2 stars, 0 dependents, and a last release in 2019, this is not a viable “buy/adopt” candidate for new products. It supports a decision to build internally or adopt a maintained sitemap generator.
Legacy modernization: If you maintain a Victoire CMS/Symfony application, this package helps frame a keep/isolate/replace decision before PHP or Symfony upgrades.
Vendor and dependency risk: It reinforces the need for dependency policies that require active maintenance, security patches, version support, and ecosystem adoption.
Requirements discovery: Product and engineering can use it to define sitemap requirements — coverage, freshness, multilingual URLs, canonicalization, lastmod, sitemap indexes, caching, and monitoring — without inheriting the package.

When to Consider This Package

Only for existing Victoire/Symfony applications that already use the widget and where removal cost is high and the feature is non-critical.
As a reference implementation, not a Composer dependency, when scoping a small internal sitemap widget.
For a time-boxed proof of concept in a legacy Victoire admin where no support or security patching is expected.
Look elsewhere for Laravel or modern Symfony projects, multilingual sitemaps, sitemap indexes, automated search-engine submission, caching, or production SEO requirements.
Avoid it when dependency hygiene, security review, long-term maintenance, or vendor support are required. Note that this is a Symfony/Victoire bundle, not a Laravel-native package.

Executives: This is a low-adoption, stale widget from 2019. Sitemaps matter for SEO, but this package is not a strategic platform dependency and should not anchor a new product roadmap.
Engineering: Treat it as a reference only. Do not add it to new builds. If it already exists in a Victoire app, isolate it behind an internal interface, document it as technical debt, and schedule replacement with a maintained sitemap generator.
Product: Fund sitemap/SEO as a first-class capability with clear requirements — coverage, freshness, multilingual support, observability, and testing — rather than adopting a micro-package with no ecosystem. The package is a useful prompt that sitemap generation should be owned, monitored, and replaceable.