Extended Api Doc Bundle Laravel Package

Product Decisions This Supports

• Feature / DX polish only. This package changes how endpoints are grouped and ordered in the rendered Nelmio API docs page (sorting by tag) plus minor visual tweaks. It does not affect the OpenAPI spec, runtime behavior, security, or contracts — so it should never be a deciding factor in a roadmap.
• Stack fit is the first decision, and the answer is usually "not applicable." Despite being a PHP/Composer package, this is a Symfony bundle that extends nelmio/api-doc-bundle. A Laravel codebase does not use Nelmio; the equivalents are Scramble, Scribe, or L5-Swagger. For a Laravel team the correct decision is to skip evaluation entirely.
• Build vs. buy skews to build. The entire value is a Twig template override plus some styling. If the underlying problem (dozens of tags, unreadable doc navigation) is real for your team, reproducing it locally is hours of work and removes a third-party dependency with 0 stars, 0 dependents, and a single release (Feb 2024).
• Legitimate use cases if you are on Symfony + Nelmio: internal API catalogs with many tagged controllers, developer portals where doc navigation quality drives support-ticket volume, or onboarding flows where new engineers rely on the docs to find endpoints.
• Signal quality is low. Zero stars, zero dependents, one release, no community. Treat it as a code sample to read, not a dependency to standardize on.

When to Consider This Package

Consider it when all of the following hold:

• You are on Symfony and already run nelmio/api-doc-bundle in production.
• Your generated docs have enough tags that ordering/grouping is a genuine comprehension problem (roughly 5+ tags, or repeated internal complaints).
• You are comfortable pinning a low-adoption dependency — or, better, copying its templates into your app so you own them.
• You have verified template compatibility against your Nelmio major version; Nelmio's view layer changes across majors and an override like this is the first thing to break.

Look elsewhere when:

• You are on Laravel — no Nelmio, no fit. Use Scramble/Scribe/L5-Swagger and fix ordering there.
• You need a maintained dependency with security response or a support path. One release in Feb 2024 and no dependents means you are the maintainer if it breaks.
• Your organization has dependency-approval gates; a 0-star package will (correctly) fail them. Vendor the template instead.
• You actually need capability improvements (auth examples, schema validation, multi-version docs). This is cosmetic; it will not move those problems.

How to Pitch It (Stakeholders)

For executives: This is a small cosmetic add-on for an existing Symfony API documentation tool. It improves how endpoints are sorted and grouped on the docs page — no revenue impact, no risk reduction, no strategic value, and no applicability to our Laravel services. Recommendation: do not adopt it as a dependency. If doc navigation is a real pain point for the Symfony team, engineering can reproduce the effect locally in about a day and we avoid taking on a zero-adoption third-party component.

For engineering: It overrides Nelmio's Twig templates to sort endpoints by tag and apply minor styling corrections. MIT-licensed, small, easy to read in full. Given 0 stars, 0 dependents, and a single release from Feb 2024, the right move is to vendor the template override rather than install the package — same user-visible benefit, we keep control, and we avoid a compatibility landmine when we next upgrade Nelmio across a major version. If we do install it, pin the version and add a note to the Nelmio upgrade checklist.