TypiCMS is a multilingual content management system built with Laravel 5. npm, Bower and gulp are used for asset management and the user interface is built with Bootstrap 3 with Less.
- Features
- Requirements
- Installation
- Modules
- Facades
- Artisan commands
- Roadmap
- Contributing
- Testing
- Licence
This kind of URLs are managed by the CMS:
Modules:
- /en/events/slug-in-english
- /fr/evenements/slug-en-francais
Pages:
- /en/parent-pages-slug-en/subpage-slug-en/page-slug-en
- /fr/parent-pages-slug-fr/subpage-slug-fr/page-slug-fr
- PHP >= 5.5.9
- OpenSSL PHP Extension
- Mbstring PHP Extension
- Tokenizer PHP Extension
- Memcached, Redis or APC
First install Node.js, Bower and gulp
-
Create a new project
composer create-project typicms/base mywebsite
-
Enter the newly created folder
cd mywebsite
-
DB migration and seed, user creation, npm installation, bower installation and directory rights
php artisan typicms:install
Go to http://mywebsite.local/admin and log in.
In order to work on assets, you need to install Node.js, Bower and gulp, then cd to your website folder and run these commands:
-
Install bower packages according to bower.json (directory app/assets/components)
bower install
-
Install gulp packages according to gulpfile.js (directory node_modules)
npm install
-
Compile admin and public assets
gulp
- Set available locales and the default locale in config/translatable.php
- Cache driver is set to memcached. You can change it to another taggable cache system such as redis in your .env file
This example is for the News module. After these steps, the module will appear in the sidebar of the back office.
-
Install module with Composer
composer require typicms/news
-
Add
TypiCMS\Modules\News\Providers\ModuleProvider::class,
to config/app.php, beforeTypiCMS\Modules\Core\Providers\ModuleProvider::class,
-
Publish views and migrations
php artisan vendor:publish
-
Migrate the database
php artisan migrate
Pages are nestable with drag and drop, on drop, URIs are generated and saved in the database. Each translation of a page has its own route. A page can be linked to a module.
Each menu has nestable entries. One entry can be linked to a page or URL.
You can return a HTML formated menu with Menus::build('menuname')
.
Projects have categories, projects URLs follows this pattern: /en/projects/category-slug/project-slug
Categories have many projects.
Tags are linked to projects and use the Selectize jQuery plugin. The tags moudle has many to many polymorphic relations so it could easily be linked to other modules.
Events have starting and ending dates.
Simple news module with linked files/images galleries.
Frontend contact form and admin side records management.
A partner has a logo, website URL, title and body content.
The files module allows you to upload multiple files. It uses DropzoneJS to upload them. Thumbnails are generated on the fly with Croppa.
You can create as many galleries as you want, each gallery has many files. Galleries are linkable to any module item through a polymorphic many to many relation, for now only the news module is properly set up to support galleries.
User registration can be enabled through the settings panel (/admin/settings).
Blocks are useful to display custom content in your views.
You can get the content of a block with Blocks::build('blockname')
.
Translations can be stored in the database through the admin panel (/admin/translations).
You can call DB translation everywhere with Lang::get('db.Key')
, trans('db.Key')
or @lang('db.Key')
.
Route sitemap.xml generates a sitemap file in XML format. To add modules to the site map configure app/config/sitemap.php.
Change website title, and other options trough the settings panel. Settings are saved in the database.
History table records changes and 25 latest records are displayed in the back office’s dashboard. Logged actions are created, updated, deleted, set online and set offline. It works for all modules except users and groups.
Each modules has a facade that give you access to the repository, you can call for example News::latest(3)
to get the three latest news.
Check available methods in each module’s repository.
Commands are located in app/TypiCMS/Commands
-
Initialisation of TypiCMS
php artisan typicms:install
-
Set cache key prefix in app/config/cache.php
php artisan cache:prefix yourCachePrefix
-
Initial migration and seed
php artisan typicms:database
Feel free to fork and make pull requests directly on the master branch! TypiCMS follows the PSR-2 standard.
Thanks to elvendor and jekjek for their contributions!
TypiCMS is an open-source software licensed under the MIT license.