- Laravel 13
- PHP 8.5
- Filament 5.x
- Livewire 4
- PostgreSQL / MySQL support
- Queue-driven architecture
- API-first design
- Fully modular package system
- Event-driven architecture
- Headless + traditional CMS support
Repository:
https://github.com/liberu-cms/cms-laravel
- WordPress (CMS + ecosystem)
- Drupal (enterprise modularity)
- Joomla (structured CMS + extensions)
- OctoberCMS (Laravel-native CMS design)
The CMS must be fully modular and distributable so that every feature can be:
- Installed independently
- Removed safely
- Versioned independently
- Reused in other applications (CRM, Billing, ERP, etc.)
- Pages module
- Posts module
- Media module
- Menu builder module
- Theme engine module
- Template engine module
- SEO module
- Blocks / components module
The CMS must support:
- Standalone CMS application
- Embedded CMS inside:
- Billing systems
- CRM systems
- ERP systems
- SaaS applications
- Package-based architecture
- Service provider isolation
- Event-based communication
- API-first access layer
- Decoupled UI layer
- Single-site mode
- Multi-site mode
- Multi-tenant CMS networks
- Shared theme repositories
- Shared plugin repositories
- Hierarchical pages
- Drag-and-drop page tree
- Page revisions
- Draft / publish workflow
- Scheduled publishing
- Page templates
- Dynamic page routing
- Slug management
- Redirect handling
- Page lifecycle tests
- Routing tests
- Draft/publish state tests
- Blog posts
- Categories
- Tags
- Author management
- Featured posts
- Scheduled posts
- Content versioning
- Excerpt generation
- Post publishing workflows
- Taxonomy tests
- SEO metadata tests
- Custom post types
- Schema builder
- Field builder
- Flexible content blocks
- JSON-based content schemas
- Portfolio items
- Products
- Case studies
- Documentation pages
- Central media repository
- Folder-based organization
- Tagging system
- Metadata storage
- Search indexing
- Duplicate detection
- Image uploads
- Video uploads
- Audio uploads
- Document uploads (PDF, DOCX, etc.)
- Automatic resizing
- Thumbnail generation
- WebP conversion
- Lazy loading support
- CDN integration support
- Upload validation
- Storage integrity tests
- Image processing tests
- Drag-and-drop menu builder
- Multi-level menus
- Menu locations
- Conditional menu items
- Role-based menus
- Header menus
- Footer menus
- Sidebar menus
- Mobile menus
- Menu rendering tests
- Permission-based menu tests
- Blade-based theme system
- Theme switching
- Child themes
- Theme inheritance
- Theme overrides
- Page templates
- Post templates
- Layout templates
- Component templates
- Verified themes
- Community themes
- Premium themes (future extension)
- One-click installation
- Theme rendering tests
- Override resolution tests
- Reusable content blocks
- Drag-and-drop builder
- Prebuilt blocks
- Custom blocks
- Nested blocks
- Text blocks
- Image blocks
- Video blocks
- Form blocks
- Code blocks
- CTA blocks
- Visual editor
- Live preview
- Grid layout system
- Responsive editing
- Component insertion
- Block rendering tests
- Layout consistency tests
- CMS users
- Authors
- Editors
- Administrators
- Contributors
- Role-based access control (RBAC)
- Content-level permissions
- Media permissions
- Module permissions
- Authorization tests
- Role restriction tests
- Meta titles
- Meta descriptions
- OpenGraph support
- Twitter cards
- Canonical URLs
- Sitemap generation
- Robots.txt management
- Google Analytics
- Matomo integration
- Custom tracking scripts
- Metadata rendering tests
- Sitemap validation tests
- Drag-and-drop form builder
- Contact forms
- Lead forms
- Survey forms
- Conditional logic
- Email notifications
- CRM integration hooks
- Spam protection (reCAPTCHA, hCaptcha)
- Submission validation tests
- Email dispatch tests
- REST API
- GraphQL API (optional module)
- Authentication (OAuth2, tokens)
- Rate limiting
- JSON content delivery
- Structured content API
- Frontend framework compatibility (Vue, React, Next.js)
- API contract tests
- Authentication tests
- Installable plugins
- Enable/disable plugins
- Plugin versioning
- Dependency resolution
- Plugin marketplace
- Content plugins
- UI plugins
- Integration plugins
- SEO plugins
- Media plugins
- Plugin isolation tests
- Dependency tests
- Sidebar widgets
- Dashboard widgets
- Footer widgets
- Custom widget builder
- Recent posts
- Search widget
- Newsletter signup
- Social links
- Modular admin dashboard
- Role-based dashboard widgets
- Customizable layouts
- Quick actions
- System health overview
- Admin panel access tests
- Widget rendering tests
- Page revisions
- Post revisions
- Media version history
- Draft
- Review
- Published
- Archived
- Scheduled publishing
- Workflow state transitions
- Revision rollback tests
- In-app notifications
- Webhooks
- Slack / Teams (optional)
- Content published
- User registration
- Plugin updates
- System alerts
- Full-text search
- Content indexing
- Media search
- Tag-based filtering
- Elasticsearch / Meilisearch support
- Page caching
- Fragment caching
- API caching
- CDN integration
- Lazy loading
- Queue-based rendering tasks
- Optimized asset delivery
- CSRF protection
- XSS protection
- Secure file uploads
- Rate limiting
- Audit logging
- GDPR compliance tools
- Cookie consent management
- Data export tools
- Local storage
- AWS S3
- Cloudflare R2
- DigitalOcean Spaces
- Multi-language support
- RTL support
- Translation management
- Locale-based content
- Content import/export
- JSON export
- XML export
- WordPress migration tools
- Database seeding tools
- Content models
- Services
- Business logic
- Permissions
Target:
- 90%+ coverage
- Page rendering
- Post workflows
- Media uploads
- Plugin lifecycle
- Page builder interactions
- Admin panel workflows
- Theme switching
- Menu builder interactions
- Storage providers
- Email systems
- API integrations
- Search engines
- PHPStan (max level)
- Laravel Pint
- Rector
- Infection Mutation Testing
- CI/CD pipelines
- Security scanning
- Performance benchmarks
To create a fully modular enterprise CMS ecosystem that can operate:
- As a standalone CMS
- As an embedded content engine inside any Laravel application
- As a headless CMS backend for modern frontend frameworks
Unlike WordPress, Drupal, Joomla, or OctoberCMS, this platform is designed to:
- Be fully modular at the package level
- Be reusable across unrelated systems (CRM, Billing, ERP)
- Be API-first and headless-ready by default
- Provide enterprise-grade testing and architecture standards
- Maintain simplicity in UI/UX while supporting extreme extensibility
The CMS should become a shared content infrastructure layer across the entire Liberu ecosystem:
- CRM
- Billing
- Accounting
- ERP
- SaaS platforms
All sharing:
- Pages
- Media
- Menus
- Themes
- Blocks
- Content APIs