- What is badaso/content-module and do I need Badaso to use it?
- It is a plugin for Badaso, the Laravel-based headless CMS maintained by uasoft-indonesia. Rather than being a standalone package, it adds content management screens and CRUD features to the Badaso admin dashboard. If you have not adopted Badaso, using this module effectively means adopting the whole Badaso stack.
- How do I install badaso/content-module in a Laravel application?
- Install Badaso core first, then require the module with Composer using composer require badaso/content-module and register it through Badaso's module system. Because the module is version-coupled to Badaso core, pin both packages to exact versions in composer.json instead of using loose caret constraints. After registering, run the module's migrations and seeders and confirm the new admin menus appear in the dashboard.
- Which Laravel and PHP versions does badaso/content-module support?
- The module targets the Laravel versions supported by the Badaso core release you install, and your PHP version must match that same compatibility matrix. There is no independent Laravel support range published for the module itself, so verify against Badaso core's composer.json requirements. Test your runtime against both packages before adopting, and recheck on every Badaso upgrade.
- Can I use badaso/content-module without installing Badaso core?
- No. The module registers entities, migrations, admin CRUD screens, and menu entries through Badaso's module manifest, and it relies on Badaso's permission system. Without Badaso core there is nothing for it to hook into. Treat it strictly as an extension of Badaso rather than a general-purpose Laravel content package.
- How does badaso/content-module store content data, and can I export it later?
- Content is stored through the module's own migrations and models, which become the source of truth for your CMS data. The schema is not heavily documented, so inspect the generated tables after installation and document them as a contract you own. To keep migration options open, wrap access in your own repository or service layer instead of calling module models directly from controllers, so content stays exportable.
- Is badaso/content-module actively maintained and safe to use in production?
- The package still receives releases, with a 2025-06-30 release indicating it is maintained alongside Badaso core. However, it has very few stars, no visible external dependents, and single-vendor maintenance, and there is no evidence of broad production usage. Plan for the realistic possibility that you will eventually own or vendor the code yourself.
- How do I enable or register the content module in the Badaso dashboard?
- Registration happens through Badaso's module manifest, typically by enabling the module so its service provider, migrations, and admin menu entries load. After enabling it, run migrations and seeders and check the dashboard for the new content menus. Then confirm permissions are assigned so only the intended roles can reach the new CRUD screens.
- How do I migrate an existing Laravel app to use badaso/content-module?
- Brownfield retrofits are high friction because you must introduce Badaso core into the existing application, which touches routing, auth, admin layout, and asset builds. Treat that as a separate architectural decision before adding the content module. If you proceed, work on a throwaway branch, enumerate the generated schema and admin routes, and keep application code behind your own interfaces.
- What are alternatives to badaso/content-module for content management in Laravel?
- Alternatives include building content management directly on Laravel models with an admin panel such as Filament or Nova, or choosing a different headless CMS. Because this module only makes sense inside Badaso, the real comparison is Badaso versus your existing admin stack. Evaluate Badaso itself first; if it fits your project, this module is a natural add-on.
- How do I test and secure the admin routes added by badaso/content-module?
- Review the admin routes for authentication, role checks, file upload handling, and rich-text sanitization, since the dashboard is a security-sensitive attack surface. There is little public evidence of test coverage or CI running against Badaso core, so add your own smoke tests for the CRUD endpoints. Also verify in production that every added route sits behind Badaso's permission middleware.