Blost Laravel Laravel Package

Product Decisions This Supports

• Build vs. buy for content surfaces: choose buy for commodity blog needs (public listing/detail, pagination, metadata, scheduling) instead of spending roadmap capacity on CMS plumbing.
• Time-to-market for content-led growth: supports launching announcements, changelog, SEO landing content, and editorial marketing pages within a Laravel 12/13 app in days.
• Editorial operations: scheduled visibility plus UTC publication dates enable an editorial calendar and coordinated launches without custom cron work.
• Authoring architecture: publishing happens through a shared authenticated API from corpuscom/blost-bundle ^1.0—decide explicitly whether authors live in an external tool/service or an internal admin, rather than assuming a Laravel-native CMS UI.
• Content portability and integrations: stable UUID primary keys and a publishable migration make articles easier to reference across services/environments and to migrate or sync later.
• Customization strategy: publishable config and Blade templates let teams own presentation/SEO markup, but create a fork-like surface that must be tracked against upstream changes.
• Security trust boundary: editorial HTML is rendered as trusted content—this forces an explicit decision that only fully trusted publishers can write; it is not a fit for semi-trusted or user-generated content without adding sanitization.
• Media strategy: media URLs are referenced, not downloaded—supports bringing your own CDN/asset pipeline rather than adopting a bundled media library.

When to Consider This Package

Consider adopting when:

• You are building or maintaining a Laravel 12 or 13 application and need a public blog quickly with minimal custom code.
• You want server-rendered Blade listing/detail pages with pagination and metadata suitable for SEO, rather than a headless/SPA-only approach.
• You already have—or plan to build—an external authoring/publishing flow that can use the authenticated Blost API, or you are already in the corpuscom/blost-bundle ecosystem.
• You need scheduled publishing/visibility and consistent UTC publication dates out of the box.
• You are comfortable publishing config/templates and owning that customization surface, with a plan to reconcile upstream changes.
• You can guarantee all publishers are fully trusted (HTML rendered as-is) and you host media elsewhere (URLs only).

Look elsewhere when:

• You need a full CMS: admin UI, media library/ingestion, categories/tags, comments, multi-author roles/permissions, or editorial approval workflows—none are described in v1.0.0.
• You cannot accept the corpuscom/blost-bundle dependency or its shared publishing/auth model, or you need a different authentication/authorization scheme.
• Authors are untrusted or semi-trusted—trusted HTML rendering is a hard blocker without adding a sanitization layer.
• You need media processing/CDN management or asset ingestion rather than URL references.
• You are on Laravel <12, need legacy/LTS support, or require multi-tenant/multi-site, i18n, or advanced SEO (sitemaps, canonical/hreflang) out of the box.
• You require a vendor-neutral, standalone package with no ecosystem coupling.

How to Pitch It (Stakeholders)

Executives: This is a production-ready blog for Laravel 12/13 at near-zero build cost. Public pages, SEO metadata, pagination, and scheduled publishing come standard, so we can ship content marketing and announcements in days rather than a quarter. We buy the commodity CMS parts and keep differentiation in our own templates. Two trade-offs to note: publishing runs through the Blost authenticated API (so access control is a policy commitment), and content HTML is rendered as trusted—meaning we must restrict publishing to trusted authors—while media is referenced by URL rather than hosted by us.

Engineering: A small, stable package: one composer require, auto-discovered service provider, publishable migration/config/templates, UUID-keyed Eloquent articles, and Blade listing/detail pages with pagination, metadata, UTC dates, and scheduled visibility. Publishing is delegated to a shared authenticated API via corpuscom/blost-bundle ^1.0. Treat published templates/config as forked code and budget for upgrade reconciliation. Editorial HTML is intentionally trusted (no sanitization) and media is not downloaded—so the connector token is a high-privilege secret and only trusted authors may publish. The release passed monorepo CI and isolated stable-consumer installation checks, so initial integration risk is low.