- What is badaso/post-module and what does it do?
- It is a Badaso CMS module that adds blog and news post management to a Laravel application already using Badaso. The overview promises admin CRUD, post listings, and API-ready data for headless frontends, but it is not a standalone Laravel CMS. Adoption is very low, so treat it as an accelerator or reference implementation rather than a proven platform dependency.
- How do I install badaso/post-module in Laravel?
- Install it with Composer inside an existing Badaso project, register or auto-discover the service provider, publish migrations, config, and assets, then run migrations and assign permissions. Verify Composer constraints and the generated tables, routes, and admin screens in a sandbox first because it is not guaranteed to be drop-in. Pin exact versions and commit the lockfile before testing upgrades.
- Does badaso/post-module require Badaso to work?
- Yes. It is a Badaso module, not a general Laravel package, and it assumes Badaso's service provider, admin UI, auth and permission model, and Vue asset pipeline. That makes it a reasonable fit only for a Laravel monolith already standardized on Badaso. It is an architectural mismatch for a plain Laravel app or a headless-only CMS.
- Which Laravel, PHP, and Badaso versions are supported by badaso/post-module?
- The supported version matrix is not documented in the provided context, so you must inspect composer.json constraints and test against your target stack. Pin exact Composer versions, verify PHP extensions and database versions, and confirm the Badaso core version. A Badaso or Laravel upgrade can silently break module views, routes, or migrations, so test every bump in staging.
- Is badaso/post-module production-ready?
- The technical risk is high: low adoption signals, no mentioned automated tests, and undocumented details around authorization, media handling, and database schema. It can be used in production only after hardening validation, output escaping, upload rules, and permission checks, plus adding integration tests for install, migrate, publish, edit, and delete flows. Keep a fork or replacement exit plan because forking shifts maintenance to your team.
- Does badaso/post-module provide APIs for headless frontends?
- The blurb says it offers API-ready data for headless frontends, but the evaluation notes it is unclear whether content is exposed through APIs or only through the admin UI. Before relying on it, inspect the package routes and controllers and verify authentication and authorization on any endpoints. Do not assume API coverage until you have tested it against a real frontend.
- What features does badaso/post-module include for categories, tags, media, SEO, and scheduling?
- The overview only guarantees admin CRUD, post listings, and API-ready data. Categories, tags, media handling, SEO fields, multilingual content, drafts, scheduling, and role-based permissions may live in Badaso core or may not be present at all. Verify the actual database schema and admin screens with real content samples before committing to the package.
- What are the security concerns with badaso/post-module?
- Known risks include incomplete authorization around post and media endpoints, XSS or file-upload exposure in blog content, migration conflicts with existing content tables, and silent breakage from upstream upgrades. Harden permission checks, input validation, output escaping, and upload restrictions before exposing it to editors. Add integration tests and review the package code because the evaluation found no security policy or test suite.
- Can I use badaso/post-module in a non-Badaso Laravel app or multi-tenant SaaS?
- It is an architectural mismatch for a general Laravel app, headless CMS, or multi-tenant SaaS because adopting the module means adopting Badaso's conventions, admin patterns, and upgrade cadence. Strict tenant isolation would require additional work. If your platform is Laravel but not Badaso, compare the cost of adopting Badaso against implementing a small content model directly.
- How do I migrate existing blog content to badaso/post-module?
- First inspect the generated schema with a disposable database, then map existing content into the package's tables and build import scripts. Use feature flags, rollback migrations, and a backup and restore plan, and do not migrate production content until authorization, media handling, and URL and SEO behavior are validated. If upstream stops releasing, you need a documented exit plan or a fork.