Font Manager Laravel Package

Product Decisions This Supports

• Build vs. buy for design token infrastructure: The 0.2.0 export layer (12+ formats including Tailwind Config, TypeScript Definitions, Design Tokens, Style Dictionary) turns this from a font utility into a design-system bridge. This is a genuine buy decision — replicating multi-format token export across CSS/SCSS/JS/design-tooling is weeks of engineering and ongoing maintenance across a moving target (Tailwind, Figma Tokens, W3C spec).
• Multi-brand / white-label roadmap sequencing: Customizable export.output paths per format and per-detected-build-tool output adjustment make it viable to generate brand-specific token bundles from one source of truth. This unblocks white-label and theming epics that would otherwise need bespoke tooling.
• Design–engineering handoff feature work: Figma Tokens Studio and W3C Design Tokens export mean a PM can scope "designers change a token in Figma, engineers get it in code" without building a pipeline. Evaluate as the backbone for a handoff initiative.
• Framework standardization decisions: Auto-detection for AssetMapper, Webpack, and Vite plus Bootstrap/Tailwind integration lets you standardize typography across heterogeneous front-end stacks — relevant when deciding whether to consolidate build tools or tolerate a mixed estate.
• Type-safety as a quality lever: Generated TypeScript definitions for fonts support a "no magic strings in font references" standard, a cheap DX and defect-reduction win to cite in engineering quality goals.
• CI/automation productization: fonts:lock auto-exporting configured formats (with --no-export escape hatch) plus fonts:export --dry-run fits cleanly into CI pipelines. This supports decisions about build reproducibility and whether font/token artifacts are committed or generated.

When to Consider This Package

Consider adoption when:

• You run a Laravel/PHP backend with a JS front end and want font and typography tokens managed server-side but consumed by Vite/Webpack/AssetMapper builds.
• You have or plan a design system and need Tailwind, SCSS, CSS variables, and design-tool formats from one source — the format breadth is the core value here.
• You face multi-brand, multi-theme, or white-label requirements where per-format output paths and repeatable export matter.
• You want framework-native integration (Bootstrap $font-family-base, Tailwind config module, TS types) without hand-maintaining generated files.
• Your team values dry-run and lockfile-style determinism in CI.

Look elsewhere when:

• Your stack is not Laravel/PHP — the value proposition is tied to the PHP configuration and console-command surface.
• You only need to serve web fonts (self-hosting, subsetting, @font-face generation). The export system is the differentiator, not the font serving; a lighter library or plain asset pipeline suffices.
• You need runtime/dynamic theming (user-chosen themes at request time). This is a build-time generation tool, not a runtime token resolver.
• You require mature, stable APIs. This is 0.2.0 with a configuration structure that just changed (build and export sections) — expect churn. Avoid if you cannot absorb breaking config changes.
• You are locked to a single build tool and single output format — the complexity of 12 export formats is overkill; a small custom script is cheaper.
• You need documented long-term support, SLAs, or enterprise backing.

How to Pitch It (Stakeholders)

For executives: A small, focused PHP/Laravel package that now acts as a design-system bridge — it takes typography and font definitions and exports them into the exact formats our front-end, design, and tooling already use (Tailwind, SCSS, CSS variables, TypeScript, Figma, W3C design tokens). It reduces duplicated effort between design and engineering, supports multi-brand theming, and slots into our existing build pipeline. Low integration cost, but note it is pre-1.0.

For engineering leads: 0.2.0 adds a multi-format export system with auto-detection of AssetMapper/Webpack/Vite, framework-native outputs (Bootstrap SCSS variables, Tailwind config, TypeScript types), and three new console commands (fonts:export, fonts:formats, fonts:format:info). fonts:lock now auto-exports configured formats (disable via --no-export), and --dry-run supports safe CI adoption. Configuration gained build and export sections — a breaking config change from prior versions, so plan a migration window. Recommend a spike on one brand/theme before committing, and pin the version given pre-1.0 instability.

For design/product stakeholders: Designers can work in Figma Tokens or W3C Design Tokens and have those values land in the codebase through a repeatable, automated export — less manual transcription, fewer drift bugs, faster theming and white-label experiments. The trade-off is maturity: it is early-stage software, so we should validate against one use case before broad rollout.