Weave Code
Tomato Sections Laravel Package
tomatophp/tomato-sections
Laravel package for TomatoPHP that lets you create and manage dynamic page sections from the admin panel. Build reusable content blocks with customizable views, ordering, and localization—no code changes needed to update site layouts.
Sections For Tomato Themes To build any app with Theme Builder
Frequently asked questions about Tomato Sections
- What is tomatophp/tomato-sections used for?
- It is a TomatoPHP package for creating and managing dynamic page sections from a Laravel admin panel. It lets you build reusable content blocks with customizable views, ordering, and localization so site layouts can be updated without code changes. It is aimed at Tomato themes and theme-builder style applications.
- How do I install tomatophp/tomato-sections with Composer?
- Install it with composer require tomatophp/tomato-sections and let Laravel package auto-discovery register the service provider where supported. Then publish the package migrations, config, and assets, run migrations, and register the Filament plugin in your panel provider. Pin a specific version during evaluation rather than using a wide caret range.
- Does tomato-sections require Filament?
- The package is described as a Filament and Laravel admin-surface package for managing sections, so a Filament panel is the expected integration point. It is a poor fit for headless, Nova, or decoupled SPA front ends without additional work. If your admin layer is not Filament, evaluate another approach.
- Which Laravel, PHP, and Filament versions are supported?
- The provided overview and changelog excerpt do not give verified minimum PHP, Laravel, or Filament version constraints. Check the package composer.json and upgrade notes before adopting it, especially because Filament v3 versus v4 compatibility can matter. Record the confirmed versions in your spike notes and lock the Filament major version alongside the package.
- How do I publish tomato-sections migrations and assets?
- Use the package publish commands after Composer installation to expose migrations, config, views, and frontend assets, then run php artisan migrate. The exact publish tags are not stated in the provided excerpt, so confirm them from the package README or vendor:publish prompt. Test migrate and migrate:rollback on a scratch database to confirm the schema is additive and reversible.
- How do I add tomato-sections to a Filament panel?
- Register the package Filament plugin in your panel provider, following the plugin registration pattern used by the TomatoPHP package. Then publish and run its migrations, confirm assets load, and verify the sections resource appears in the admin navigation. Do this first in a throwaway branch or scratch panel to catch stylesheet and view conflicts.
- Does tomato-sections support RTL and dark mode?
- Version 1.0.6 adds RTL and dark mode support at the UI layer. The provided notes do not confirm whether these are opt-in via config or auto-detected from the Filament panel, so verify the behavior in your own theme. Also check whether the release changes published CSS that could collide with custom design tokens.
- Can I customize section views, ordering, and localization?
- Yes, the package is described as supporting reusable content blocks with customizable views, ordering, and localization. Plan to publish views and override them carefully, because future package updates can overwrite customized published files if you are not tracking changes. Keep custom view overrides in version control and re-test after upgrades.
- How should I test tomato-sections before production?
- Run a spike in a throwaway branch, publish config, migrations, and assets, and register the plugin on a scratch Filament panel. Verify the v1.0.6 RTL and dark mode behavior against your theme, and confirm the migration is additive and reversible with migrate and migrate:rollback. Only then introduce it to shared staging behind a feature flag with the package version pinned.
- What are alternatives to tomato-sections and what maintenance risks should I consider?
- Alternatives include static Blade partials, a small custom sections model, or a dedicated Laravel CMS package if your needs are broader than Filament-managed blocks. Main risks are single-vendor governance, fast UI-layer releases that can affect published views and CSS, and coupling to Filament major versions. Avoid it if you need a headless CMS or a non-Filament admin surface.
Weaver
How can I help you explore Laravel packages today?