Weave Code
Blog Laravel Package
capell-app/blog
A blog module for the Capell Laravel application framework. It adds posts, categories, and publishing workflows that plug into Capell's admin and content pipeline, giving your app a ready-made blogging layer without building one from scratch.
Editorial publishing for Capell with articles, taxonomy, multilingual output, and growth integrations.
Frequently asked questions about Blog
- How do I install capell-app/blog in a Laravel app?
- Install it as a Composer dependency with composer require capell-app/blog inside a Capell Laravel application, then run the package migrations and any publish steps documented by Capell. The overview describes a module that integrates with Capell's admin and content pipeline, so confirm you already have Capell core and admin available before installing. Check the repository README for the exact service provider, config publish tag, and migration command for your version.
- Does capell-app/blog support Laravel 11 or Laravel 12?
- The provided overview does not list exact Laravel version constraints, so do not assume support for Laravel 11 or 12 from the package description alone. Check the package composer.json for its illuminate or laravel/framework constraints and the Capell core requirements. Because it is a Capell module, the supported Laravel major is also bounded by the Capell core version you run.
- Can I use capell-app/blog in a standalone Laravel app without Capell?
- capell-app/blog is designed as a module for the Capell Laravel CMS, not a generic standalone blog package. The overview says its admin resources and content pipeline plug into Capell, so adopting it in a bespoke Laravel app likely means adopting Capell's admin and content architecture too. If you only need basic blog CRUD, evaluate whether a simpler Laravel package or a custom implementation fits better.
- What features does capell-app/blog add for posts and content organization?
- It adds post management with slugs, excerpts, and rich-text content, plus categories and tags for organizing entries. The module also includes publish states for draft, scheduled, and published content. These features are exposed through Capell admin resources and frontend-ready models and routing.
- How do publishing states work in capell-app/blog?
- The package provides publish states so posts can be drafted, scheduled, or published. That lets authors prepare content and control when it becomes visible through the Capell content pipeline. For exact scheduling behavior, confirm how Capell core handles dates and frontend queries in your version.
- Does capell-app/blog include admin screens for creating and editing posts?
- Yes, the overview states that the module provides admin resources for creating and editing posts in the Capell admin panel. That means authoring happens through Capell's admin surface rather than a separately built blog dashboard. You should confirm the required Capell admin package and authorization setup for your application.
- What database migrations does capell-app/blog run?
- The package ships migrations for its blog content model, which the overview describes as posts plus categories and tags. The provided release evidence does not detail table names, shared-table usage, or database-engine parity. Review the migration files before installing and test on your target database, especially if you use PostgreSQL or SQLite rather than MySQL.
- Is capell-app/blog actively maintained and safe for production?
- The available release evidence shows version 1.0.53, but the supplied note includes only a compare link and no changelog body, PR list, or upgrade notes. That makes the release hard to review and means maintenance cadence, test coverage, CI, and security advisories still need verification. Treat production adoption as gated on inspecting the diff, the Capell core dependency health, and the package test suite.
- How should I test capell-app/blog before adding it to production?
- Install it in a staging Capell environment, run migrations against a copy of production data, and exercise post creation, category and tag assignment, scheduling, and frontend rendering. Check route precedence, view namespace collisions, and authorization rules for authors versus publishers. Also run your application test suite and review the package own tests and CI status if available.
- Can I remove capell-app/blog cleanly if I stop using it?
- The overview does not document an uninstall or rollback path, so removal should be planned and tested rather than assumed. Because the package ships migrations and integrates with Capell admin and content models, removing it may require rolling back tables, removing config, routes, and admin registrations, and checking for shared-table dependencies. Confirm migration ownership and back up your content before attempting removal.
Weaver
How can I help you explore Laravel packages today?