Weave Code
Tomato Sections Module Laravel Package
tomatophp/tomato-sections-module
TomatoPHP module that adds reusable section management to Laravel and Filament apps. Create, organize, and reuse content sections, control ordering and visibility, and attach them to pages through an intuitive admin interface.
Sections For Tomato Themes To build any app with Theme Builder
Frequently asked questions about Tomato Sections Module
- What is tomatophp/tomato-sections-module and what does it do?
- It is a TomatoPHP module that adds reusable section management to Laravel applications through a Filament admin interface. You can create, organize, and reuse content sections, control their ordering and visibility, and attach them to pages from the admin panel. It is designed to work alongside Tomato Themes and the TomatoPHP admin stack rather than as a standalone CMS.
- How do I install tomatophp/tomato-sections-module in a Laravel app?
- Install it with Composer via composer require tomatophp/tomato-sections-module, then publish the config and migrations with the package's publish command and run php artisan migrate. The v1.0.3 release adds a register/generate command that scaffolds and registers the module to reduce manual wiring. Pin the version in composer.json instead of using a floating constraint on an early 1.x package.
- Which Laravel, PHP, and Filament versions does this package support?
- The module targets whatever Laravel, PHP, and Filament versions the parent TomatoPHP release expects, but the support matrix is not spelled out in the one-line release notes. Check the constraints in composer.json and confirm the Filament major version matches your TomatoPHP install, and ask whether that matrix is covered in CI. Because v1.0.3 is an early patch, validate on a staging clone before rolling out.
- Do I need Filament or the TomatoPHP admin panel to use this module?
- Yes. The package is a Filament-backed admin module and presumes TomatoPHP/Filament routing and view conventions, so it is a weak fit for headless or API-first services. Teams already on Livewire/Filament but outside TomatoPHP should verify compatibility before committing. For greenfield projects, adopting it means adopting the parent admin stack as a deliberate architectural decision.
- What does the new register/generate command in v1.0.3 do, and is it safe to run?
- The v1.0.3 change adds a register/generate command that typically handles provider registration, config publication, and module scaffolding, improving time to a first working screen. The change is additive and low-risk in isolation, but the release notes are only one line long. Confirm whether the command edits application files in place and whether it is idempotent and reversible, and run it on a non-production branch first.
- Does the module create its own database tables, and are the migrations rollback-safe?
- Like a conventional Laravel package, it publishes migrations that give the module its own section tables. Review the published migration files to confirm they are additive and rollback-safe before running them against a restored production snapshot. Any existing content stored elsewhere needs a one-off import mapping into the sections schema, which the package will not supply.
- How do I control the order and visibility of sections on a page?
- Ordering and visibility control are core features: you arrange sections and toggle which ones render on a given page. Because sections are reusable, the same section can be attached to multiple pages with different ordering and visibility. Verify the front-end rendering paths as well as the admin screens, since the admin UI alone does not prove the output.
- Are sections exposed through an API or authorization policies, or are they only admin UI constructs?
- The module is primarily an admin-UI construct for building pages within Tomato Themes, and the release notes do not document an API surface or policies for sections. If you need programmatic access or fine-grained authorization, plan to read the section models directly or add your own controllers and policies. Confirm the schema and model exposure before designing around it.
- Is tomatophp/tomato-sections-module production-ready and how actively is it maintained?
- Treat v1.0.3 as an early 1.x patch: release notes are minimal and the only cited change is a first-time contributor's pull request, which suggests a small maintainer pool and limited review bandwidth. The dominant risk is maturity and long-term support rather than design. Pin the version, test on staging, and keep a fallback plan in case a major Filament or Tomato upgrade strands the module.
- What are the alternatives if I don't want to adopt the TomatoPHP and Filament stack?
- If you want reusable content blocks without Filament or TomatoPHP, look at block-based CMS packages or roll your own sections model with a custom admin UI. Staying in the TomatoPHP ecosystem makes sense mainly when you already run that admin stack. Weigh the coupling risk, since the module's useful life is tied to the health of the parent platform.
Weaver
How can I help you explore Laravel packages today?