Xeed Laravel Package

Product Decisions This Supports

• SEO and content distribution roadmap: If your product depends on search engine discovery (marketing sites, blogs, marketplaces, documentation portals) or syndication (podcasts, news, changelogs), xeed covers the sitemap.xml and RSS/Atom generation layer so your team doesn't hand-roll XML.
• Build vs. buy on "XML plumbing": Sitemaps and feeds are commodity infrastructure. Adopting a small, focused package lets you redirect engineering time to differentiators instead of maintaining XML serialization, escaping, and feed-format edge cases.
• Feature scoping for editorial/CMS work: When planning publishing workflows, scheduled content, or multi-section sites, xeed informs whether "auto-generated sitemap + per-section feeds" is a cheap add-on (it is) versus a bespoke feature.
• Multi-surface syndication decisions: Supports deciding whether to expose one global feed or per-category/per-author feeds, and whether to submit sitemaps to search consoles — both low-effort wins with this package in place.
• Dependency risk tracking: A package that is essentially single-maintainer with infrequent patch releases is a small but real continuity consideration for anything customer-facing and SEO-critical.

When to Consider This Package

Consider it when:

• You're on Laravel and need standards-compliant sitemap.xml and/or RSS/Atom output with minimal configuration.
• Your content set is dynamic and database-driven, and you want routes/controllers that emit feeds rather than static files.
• You want per-section or per-entity feeds (categories, tags, authors) without building a feed abstraction yourself.
• Your team values a small dependency over a large SEO suite; you don't need analytics, redirects, or meta-tag management from the same package.

Look elsewhere when:

• You need a broad SEO platform (meta management, redirects, structured-data tooling) — a fuller suite is a better fit than a single-purpose feed generator.
• You require guaranteed, contract-level maintenance/SLA support; this is a community package with a small contributor base.
• Your sitemap needs exceed simple generation (very large sitemaps requiring index sharding at scale, complex prioritization logic, real-time streaming) — verify fit before committing.
• You're not on Laravel, or you're on a version outside the package's supported range.

Release-specific note (v2.0.2): This is a housekeeping patch — a README icon fix and an internal refactor — with no new features, breaking changes, or deprecations. Treat the 2.x line as functionally stable; the refactor is a reminder that internals can shift between patches, so pin versions and rely on the public API rather than extending internals.

How to Pitch It (Stakeholders)

For executives: This is a small, low-cost Laravel package that handles sitemaps and RSS feeds — the plumbing that gets our content discovered by search engines and syndicated to readers. It replaces custom code we'd otherwise build and maintain, and it's a patch-level, no-risk update.

For engineering: Single-purpose Laravel package covering sitemap.xml and RSS/Atom generation with route-based, database-driven feeds and support for per-section feeds. v2.0.2 is a maintenance release (README fix plus an internal refactor) — no API changes, no migrations required. Recommendations: pin to the 2.x minor, avoid depending on internal classes given the refactor, and add a smoke test asserting your sitemap/feed endpoints return valid XML so future refactors surface immediately. Maintainer concentration is a known, accepted risk; the surface area is small enough that in-house replacement would be a contained effort if needed.