Weave Code
Base Laravel Package
typicms/base
TypiCMS Base is the core foundation for TypiCMS, a modular, multilingual content management system built on Laravel. It provides shared CMS infrastructure, localization, and module support for building flexible, maintainable websites.
TypiCMS Base is the core foundation of TypiCMS, a modular, multilingual content management system built on Laravel. It provides shared models, repositories, helpers, and admin scaffolding that power pages, modules, and localized content across the CMS.
Use it as the base layer for building flexible, translatable websites with a Laravel-native architecture.
- Multilingual content with per-locale management
- Modular architecture for extending the CMS with custom modules
- Laravel-native Eloquent models, migrations, and service providers
- Admin-ready scaffolding and reusable backend components
- Flexible page and module system for structured content
Frequently asked questions about Base
- What is typicms/base and how does it differ from a Laravel CMS package?
- typicms/base is the application skeleton for TypiCMS, a modular multilingual CMS built natively on Laravel. Rather than a drop-in library you add to composer.json, it is a top-level project you fork or clone and build on. It composes a core plus separate feature modules such as pages, news, events, menus, users, and settings, each shipping its own models, migrations, routes, views, and service provider.
- Which Laravel and PHP versions does TypiCMS support?
- The current tagged release targets PHP 8.x and a Laravel-supported database, but you should verify the exact Laravel major against the release notes before committing. TypiCMS has historically trailed current Laravel majors, which can delay security patches on transitive dependencies. Confirm the supported Laravel and PHP versions for your chosen tag as part of due diligence.
- How do I install typicms/base in a new Laravel project?
- Installation is a fork-and-clone workflow rather than a standard Composer require. Clone the typicms/typicms skeleton, run Composer install, configure your .env for database and storage, and run migrations. Because it is a top-level application, you build your product on top of the cloned codebase rather than adding typicms/base to an existing composer.json.
- Can I add TypiCMS to an existing Laravel application?
- Grafting TypiCMS into a mature Laravel app is possible but materially higher friction than greenfield use. You will need to reconcile authentication, routing, asset pipeline, and migration ordering with your existing conventions, which is typically a multi-week integration with real regression surface. A common pattern is to run TypiCMS as a discrete application on a subdomain or path behind a reverse proxy with shared identity via SSO.
- How do I create a custom module for TypiCMS?
- Custom content types are added as self-contained modules that ship their own models, migrations, controllers, Blade views, routes, translations, and service provider. The module registers into the host app through Laravel's provider and config conventions, following the repository pattern, presenters, and per-module facades used by the core modules. Check that the module contract is documented well enough to build one without upstream guidance before relying on it.
- Does TypiCMS support multilingual content, and how is it stored?
- Yes, TypiCMS is multilingual by design, but the data model typically stores per-locale content as discrete columns such as title_en and title_fr rather than in a translations table. That means adding a new locale generally requires a schema migration. Plan your locale roadmap early if you expect to add languages after launch.
- Is there a headless or JSON API for TypiCMS?
- TypiCMS is primarily a server-rendered Blade and Bootstrap admin application, and the admin panel is the sanctioned interface. There is no guaranteed supported JSON or API surface for headless or mobile clients, so you should confirm whether one exists for your target release. If API-first delivery is a hard requirement, TypiCMS is a poor fit.
- What database and storage requirements does TypiCMS have?
- You need PHP 8.x, MySQL 5.7+/8 or Postgres, and Flysystem-compatible storage such as local disk or S3. Image handling implies GD or Imagick in the runtime image, and front-end asset compilation assumes Node tooling, though the admin does not require a JS framework. It deploys cleanly to conventional PHP-FPM with Nginx and opcache or to containerized platforms.
- How is TypiCMS maintained, and what are the risks of using it?
- The dominant risk is bus factor: the project is maintained by a very small core with a modest star count and no downstream dependents creating backward-compatibility pressure. Secondary risks include Laravel version lag, a jQuery and Bootstrap admin UI, and no published LTS or security-response policy. MIT licensing lets you take a private fork with no upstream obligation, which is the sensible posture for production.
- What are alternatives to TypiCMS for a multilingual Laravel CMS?
- Alternatives depend on whether you want a full editorial back office or a headless CMS. TypiCMS suits teams that want a working multilingual admin on day one and are comfortable with Laravel idioms; it is a poor fit for API-first, SPA-fronted, or DDD-structured codebases. Evaluate Laravel-native options like Statamic or headless platforms if your delivery model is API-first.
Weaver
How can I help you explore Laravel packages today?