Weave Code
Webblocks Cms Laravel Package
fklavyenet/webblocks-cms
A modular Laravel CMS package for building block-based websites. It provides editable pages, reusable content blocks, menus, media management, and a flexible admin interface that developers can extend with custom blocks and site-specific functionality.
WebBlocks CMS is a modular, block-based content management system built for Laravel. It lets you compose pages from reusable content blocks, giving editors flexible layouts without touching code while developers retain full control over rendering and data structure.
- Block-based pages — build layouts from reusable, configurable content blocks
- Laravel-native — migrations, models, and views follow familiar conventions
- Flexible templating — map blocks to your own Blade components
- Lightweight admin — manage pages and content from a simple backend
- Extensible — register custom block types and fields
Frequently asked questions about Webblocks Cms
- What is fklavyenet/webblocks-cms used for in Laravel?
- It is an open-source, Laravel-native CMS package for structured, multi-site publishing and automation. It is built around reusable content blocks and provides a modular foundation for managing pages and web content in PHP applications. It suits developers who want a lightweight, extensible starting point for custom content management rather than a full monolithic CMS.
- How do I install webblocks-cms in a Laravel application?
- It follows standard Laravel package consumption: install or upgrade with Composer, use the auto-discovered service provider, publish configuration with vendor:publish, and run php artisan migrate for any package tables. No new queue, search, or cache infrastructure is mandated by the release notes. Check the repository README and composer.json for the exact publish tags and service provider setup.
- Which Laravel versions and PHP versions does webblocks-cms support?
- The package is a Laravel-native Composer package, but the provided context does not list exact Laravel or PHP version constraints. Check the package's composer.json on Packagist or GitHub for the authoritative requirements before installing or upgrading. Use those constraints to confirm compatibility with your application's Laravel and PHP versions.
- How do I configure automatic detail pages for draft content in webblocks-cms?
- Draft automatic detail pages are configured from Dynamic Content by selecting the source, existing design, base path, and visible block field mappings. The configuration is additive and inactive until automatic public routing is activated, so it does not immediately change public URLs. You can prepare draft configurations first and stage activation later.
- Does webblocks-cms support multi-site publishing and site-scoped designs?
- Yes, the package is positioned for structured, multi-site publishing and automation. The v1.102.0 release enforces site-scoped design references, which improves data integrity but may reject cross-site references that were previously tolerated. Audit existing designs before upgrading if you rely on cross-site references.
- How do I register a provider for the provider publication contract 1.0?
- The provider publication contract 1.0 is an optional, versioned interface boundary for third-party content providers. The context does not specify whether discovery is via interface, config map, or service container tag, so check the package documentation for the registration mechanism. Contract 1.0 is optional, so providers can be migrated one at a time rather than all at once.
- How does webblocks-cms handle preview authorization and multilingual content?
- Preview reuses the native multilingual design and avoids copying pages or mutating stored translations, which keeps a single source of truth. Preview access should use the same authorization posture as draft content; confirm whether the host application's policy, gate, or middleware gates preview entry points. Canonical and language links must not become a public back door.
- How should I test a webblocks-cms upgrade before production?
- Upgrade in a staging clone of production data, run the migrations, and confirm that no published page or URL changes. Exercise the release's validation and preview surfaces, including stale-edit conflict detection and multilingual record validation. Test draft detail-page configuration without activating public routing, then stage activation separately.
- Is stale-edit protection optional, and what upgrade risks should I check?
- Stale-edit protection is a behavior change in v1.102.0; the context does not state whether it is opt-out per content type, so verify that in the package documentation. It can cause save failures in editorial flows that previously used last-write-wins, especially with multiple editors or long-lived tabs. Also audit site-scoped design references and dormant draft configurations for base-path collisions and unmapped required fields.
- What alternatives to webblocks-cms should I consider?
- The provided context does not name direct alternatives, so compare other Laravel CMS packages against your block-based, multi-site requirements. Look for reusable content modeling, multi-site support, multilingual preview, provider extensibility, and a clear upgrade path. Webblocks-cms is a good fit if you want a lightweight, extensible Laravel-native foundation rather than a monolithic CMS.
Weaver
How can I help you explore Laravel packages today?