Weave Code
Tomato Cms Laravel Package
tomatophp/tomato-cms
Tomato CMS is a Laravel package from the TomatoPHP ecosystem that adds content management to your app: pages, posts, menus, and media, with a Filament admin panel. It plugs into TomatoPHP's module system for quick setup. Early-stage and lightly adopted, so review before production use.
Tomato CMS is a modular content management package for Laravel built on the TomatoPHP ecosystem. It gives you a ready-made admin layer for managing pages, articles, menus, and media, so you can ship a complete site without hand-building every CRUD screen.
- Page & post management with draft and publish states
- Menu and widget builder for dynamic layouts
- Media library with uploads and thumbnails
- SEO fields for titles, descriptions, and slugs
- TomatoPHP admin integration out of the box
Frequently asked questions about Tomato Cms
- What is tomatophp/tomato-cms and what does it add to a Laravel application?
- Tomato CMS is a modular content management package for Laravel from the TomatoPHP ecosystem. It provides a ready-made admin layer for managing pages, posts, menus, and media, including draft and publish states, a menu and widget builder, a media library with thumbnails, and SEO fields for titles, descriptions, and slugs. It is designed to integrate with the TomatoPHP admin suite rather than stand alone, so it assumes Filament and several sibling Tomato packages are present.
- How do I install tomatophp/tomato-cms in a Laravel project?
- Installation is a Composer require followed by publishing the package config and migrations, running migrate, and registering the Filament resources. Because the package depends on the TomatoPHP admin layer, Filament, and sibling packages such as settings, roles, translations, and media, the resolved dependency tree is usually larger than the single Composer line suggests. Always publish configuration first and inspect the config keys and schema before running migrations in any shared or production environment.
- Which Laravel and Filament versions does tomato-cms support?
- The last release was in May 2024, which predates several Laravel and Filament major versions. Treat Filament major-version alignment as a hard gate: run composer why-not against your installed versions before anything else. On a current stack you should budget time to patch or fork for Filament compatibility rather than assuming a clean install.
- Do I need the full TomatoPHP ecosystem to use this CMS?
- In practice, yes. Tomato CMS is built on TomatoPHP conventions and expects packages like admin, settings, roles, translations, and media to be installed, so the real adoption surface is that whole dependency tree. If your application is not already inside the TomatoPHP ecosystem, the decision becomes a program-level commitment rather than a single-package trial. Get a written answer on ecosystem adoption before starting an evaluation spike.
- How does Tomato CMS handle pages, posts, drafts, and publishing?
- The package ships CRUD screens for pages and posts with draft and publish flags, so editors can control URL slugs and publish state from inside the admin panel. Content is stored in the package's own tables and rendered on your front end, typically through Blade or Inertia. Publishing behavior, slug generation, and locale handling should be verified during a spike because they are the parts most likely to need customization.
- How do I add SEO fields and slugs to content in Tomato CMS?
- Tomato CMS includes SEO fields for page and post titles, meta descriptions, and slugs out of the box, editable from the Filament admin panel. Slugs drive front-end routing, so confirm how the slug source is configured and whether it is generated automatically or entered manually. Wrap reads behind your own interface so SEO metadata remains portable if you later swap the package out.
- Will tomato-cms migrations conflict with my existing pages or posts tables?
- There is a real risk of collisions if your application already has pages, posts, or categories tables, and the impact is contained but real. Diff the package migrations and models against your existing schema before running migrate anywhere shared. Publishing configuration and reviewing table names ahead of time is the recommended mitigation.
- Is tomato-cms actively maintained and safe for production use?
- Adoption signals are weak: roughly one GitHub star, zero dependents, a single maintainer, and no vendor backing or upgrade roadmap aligned to current Laravel and Filament majors. Issues are unlikely to be answered, so anything your team does not understand by the end of an evaluation spike becomes yours to own permanently. Name an internal maintenance owner and allocate capacity for dependency bumps and Filament patches before approving it for production.
- How does the media library and menu builder work in Tomato CMS?
- The package provides a media library with uploads and thumbnail handling, plus a menu and widget builder for composing dynamic layouts without hand-coding every admin screen. These features rely on the TomatoPHP media and admin packages, so the behavior you get is tied to the versions resolved in your dependency tree. Test uploads, thumbnails, and menu rendering on your actual stack rather than relying on the README.
- What are the alternatives to Tomato CMS for a Laravel admin panel?
- The honest comparison is against a thin custom content model built on native Filament resources, not against Strapi or Drupal. If you are already inside the TomatoPHP ecosystem, this package is a genuine accelerator that delivers page, post, category, and SEO CRUD in day-scale effort. If you are not, estimate the custom Filament build first so your evaluation spike has a benchmark to beat or lose against.
Weaver
How can I help you explore Laravel packages today?