Ui Laravel Package

Product Decisions This Supports

• Content-type roadmap for feeds: v0.10.0 adds Code and Callout bodies across Blade, Vue and React, so the feed can now carry developer-facing content (snippets, warnings, release notes, deprecation notices) without a bespoke renderer. This directly supports decisions about whether a single feed component can serve both marketing and engineering audiences.
• Build vs. buy on the feed UI layer: Payload v1 reaching 1.0 (alongside core's RC) plus cross-kit parity means the integration surface is stabilizing. That shifts the buy case: adopting the package is now a contract-level decision, not an experiment.
• Brand and typography control without opening an XSS hole: the headline formatting seam (Blade HeadlineText, Vue FEED_HEADLINE_TEXT, React headlineText) lets product/design apply inline-code styling to templated headlines while keeping output escaped by default. Useful where headlines contain identifiers, API names or version numbers.
• Design-system alignment: custom Image renderers can now pass payload to FeedMedia, inheriting the feed's image-size limits and per-body overrides including full. This supports decisions about whether to reuse an existing image component rather than fork the kit.
• Integration cost and AI-assisted delivery: the bundled Boost guideline and storyfeed-ui skill mean php artisan boost:install teaches an app's coding agent the kit setup (Blade/Vue/React install, Tailwind @source lines, Vite alias, token retuning via @theme, feed props, FEED_* provides, FeedMedia replacement). This is a concrete input to estimates for onboarding and to any "can we ship this in a sprint" call.
• Documentation-as-contract: tests fail when the Boost files name components, props, exports, provide keys, classes or paths the package doesn't ship. That reduces the risk of stale guidance driving support load, which matters when deciding to standardize on the package across teams.
• Kit selection / stack flexibility: identical feature coverage in Blade, Vue and React supports decisions to keep a PHP-rendered fallback while a front-end migrates, rather than committing to one rendering path.

When to Consider This Package

• You are on Laravel/PHP, use Tailwind, and need a feed UI layer rather than a full CMS or content-authoring product.
• You want a headless-ish core (Storyfeed core) with maintained UI kits, and you may serve the same feed through Blade, Vue or React.
• Your content includes code blocks (with a language-<name> class hook for a host highlighter) and callouts (note/info/success/warning/danger with light/dark palettes).
• You want controlled headline formatting — e.g. inline code in headlines — without adopting a full Markdown pipeline or letting raw HTML through.
• You are standardizing on AI-assisted development and want the package to ship agent guidance rather than writing onboarding docs yourself.
• You need renderer-level customization (custom Image renderers) that still respects feed-level image sizing.

Look elsewhere when:

• You are not on Laravel/PHP or cannot adopt Tailwind.
• You need rich body authoring (full Markdown, embeds, tables, WYSIWYG). The shipped inlineCode formatter parses only paired single backticks — no other Markdown — and custom Blade callbacks return trusted HTML and must escape text themselves.
• You require a 1.0-stable core. This is v0.10.0 against a core release candidate; headline formatting depends on Storyfeed core 0.21 and degrades to plain headlines on older core.
• You need a formal accessibility conformance statement; nothing in this release asserts one.
• You want the package to own highlighting or media processing — the Code body exposes a class hook for a host highlighter and does not bundle one.
• Your build imports a kit through a Vite alias and you cannot add the documented Tailwind scan of vendor/storyfeed/ui/resources/js; without it, styles will be missing.

How to Pitch It (Stakeholders)

For executives: Storyfeed UI v0.10.0 turns the feed component into a broader content surface — code snippets and callout boxes now render consistently in Blade, Vue and React — while stabilizing its payload contract at 1.0. That lowers the cost of serving both customer-facing and developer-facing feeds from one Laravel package, and the bundled Boost guideline plus storyfeed-ui skill means engineering onboarding is largely pre-written for AI-assisted teams. Net: less custom UI work, one integration across three front-end stacks, and a clearer buy-versus-build answer.

For engineering: v0.10.0 adds Code and Callout renderers with escaped content, optional titles, and dark/light intent palettes (language-<name> class is a hook — bring your own highlighter). Headline text can be formatted through a seam in all three kits, with an opt-in inlineCode formatter that only handles paired single backticks and leaves unmatched backticks literal; the Blade callback is trusted HTML and must escape its own text. Custom Image renderers can pass payload to FeedMedia to inherit image-size limits, and media frames now shrink to the full picture rather than leaving a muted box. The Boost guideline and skill are verified by tests that fail if they reference anything the package does not ship — treat that as the integration checklist. Caveats: headline formatting requires Storyfeed core 0.21 and silently falls back to plain text on older core; importing a kit via a Vite alias requires scanning vendor/storyfeed/ui/resources/js for Tailwind; and this remains a 0.x package, so pin versions and read the changelog per bump.