Twig Extension Bundle Laravel Package

Product Decisions This Supports

• View-layer formatting without controller bloat. lcfirst and ucfirst filters let Blade templates capitalize or decapitalize strings inline ({{ $label | ucfirst }}), which reduces one-off helpers, custom directives, and duplicated formatting logic across views.
• Copy and label consistency. Useful for feature work involving generated headings, badge/label text, notification and email templates, seeded demo content, and admin-panel column labels — places where the string is dynamic but the casing rule is presentation-only.
• Build vs. buy: buy, at low cost. The capability is trivial to hand-roll, but so is the maintenance. Adopting a small filter package is defensible when it standardizes a convention across a team; it is not defensible if it becomes a transitive dependency of the design system.
• Roadmap signal: maintenance, not strategy. 1.1.0 is a hygiene release (code style, composer constraints, README fix) plus two string filters. Treat it as a healthy-maintenance indicator, not as a reason to schedule roadmap work.
• Localization caveat to log now. ucfirst/lcfirst on names and copy is not locale-aware in the general case. Turkish dotted/dotless i, German ß, and other casing rules will not be handled correctly by naive first-character transforms. If the roadmap includes markets where this matters, the decision is to use Str::ucfirst/Str::lcfirst (multibyte-aware) in application code and reserve these filters for non-localized, ASCII-safe presentation strings.

When to Consider This Package

Adopt when:

• The product renders primarily through Blade templates and the team wants a single, chainable convention for string presentation.
• The formatting needs are cosmetic and confined to views — casing labels, tags, headings — not business logic.
• You are already carrying a small set of view-layer dependencies and this replaces bespoke directives rather than adding to them.
• You can pin the version and absorb the composer requirement update in 1.1.0 after confirming it against your PHP/Laravel support matrix.

Look elsewhere or skip when:

• Your content is multilingual and user-generated; locale-aware casing is required, and mb_*/Str:: equivalents should be used directly.
• Your frontend is largely Inertia/React/Vue — formatting belongs in the component layer, and this adds a dependency with no consumer.
• Formatting logic is already centralized in view models, presenters, or API resources; a second convention creates drift.
• The package's raised composer floor conflicts with the oldest PHP/Laravel version you must support for on-premise or long-term-support customers.

How to Pitch It (Stakeholders)

For executives: This is a small, low-risk template utility. Release 1.1.0 adds two string-formatting filters and refreshes dependency constraints — no architectural, security, or infrastructure impact. The value is developer throughput on presentation work, not new product capability. Recommendation: allow it in the view layer, pin the version, and revisit only if we expand into locales with non-trivial casing rules.

For engineering: 1.1.0 is a maintenance release — code style, composer requirement changes, a README link fix — plus lcfirst and ucfirst filters. No deprecations or breaking changes are indicated, but the composer constraint bump is the only item that can break a build, so validate it against our PHP and Laravel version matrix in CI before merging the upgrade. Standardize usage in Blade only; keep locale-sensitive and data-level transforms in Str:: helpers so we don't inherit silent i18n bugs. Add a lint or review note so the filters don't leak into domain code.