Tomato Sections Laravel Package

Product Decisions This Supports

• Feature: admin-managed, reusable page sections. Enables marketing/CMS-style pages where content blocks ("sections") are authored and reordered by non-developers instead of shipped in code — a direct enabler for content velocity and reducing engineering involvement in copy changes.
• Roadmap: localization and internationalization. The v1.0.6 RTL support is the concrete signal that this package is intended for Arabic/Hebrew/Persian-language markets. If RTL locales are on the roadmap, this moves the admin-side i18n work from "build" to "buy/borrow."
• Roadmap: theming and brand consistency. Dark Mode support in the same release means the admin surface can match a product's design system without custom CSS overrides — relevant if you plan to white-label or resell the admin experience.
• Build vs. buy: content modeling. A section/block abstraction is a commodity capability. Adopting this package avoids building and maintaining a bespoke section builder, schema, and reorder UI — reserve custom build effort for the parts that are actually differentiated.
• Use cases: corporate/marketing sites on Laravel, multi-locale landing pages, internal content portals, and any Filament-based admin that needs structured page composition. Not a fit for headless/API-only content delivery or editorial workflows requiring versioning, scheduling, and approval chains.

When to Consider This Package

Adopt when:

• You are on Laravel + Filament and already inside or adjacent to the TomatoPHP ecosystem; the integration cost is close to zero.
• Your product needs structured, reusable content sections with an admin UI, and the alternative is a multi-week custom build.
• RTL locales or dark-mode admin UI are on the near-term roadmap — v1.0.6 delivers both without custom work.
• You can tolerate a v1.x, single-maintainer package: pin the version, review upgrades, and keep the section model thin enough to migrate off if needed.

Look elsewhere when:

• You need a full CMS (workflow, scheduling, revisions, roles) — evaluate a dedicated CMS or a headless approach instead of composing several small packages.
• Your frontend is not Filament/Laravel-rendered (e.g., Next.js or Nuxt consuming an API); the value here is largely the admin UI.
• You require long-term support guarantees, security SLAs, or a large contributor base — a one-line patch release like v1.0.6 is a reminder that release cadence is small and informal.
• The site is static or trivially small; a section builder adds configuration surface you will not repay.

How to Pitch It (Stakeholders)

For executives: This release is a small, low-risk UI update that adds RTL and dark-mode support to the section-management admin. Strategically it matters because it removes a blocker to shipping in right-to-left language markets and to offering a branded/white-labeled admin — both of which would otherwise be custom engineering work. It is a patch-level change: no migration, no breaking API change, minimal regression exposure. Recommendation is to adopt where we are already on Laravel/Filament, pin the version, and treat it as a time-to-market accelerator rather than a platform commitment.

For engineering: v1.0.6 is a UI-layer release — RTL layout handling and dark-mode theming, no schema or public API changes, so upgrade risk is contained to templates and styles. Before adopting, confirm it fits the Filament version in use, check the rendered section model for lock-in (how sections are stored and related to pages), and add a smoke test around the admin render path. Because the package is small and actively patched, pin to 1.0.x, review diffs on upgrade, and keep our own section definitions in application code so a future swap stays cheap.