TypiCMS is a multilingual content management system built with Laravel 4.2. Bower and gulp are used for assets management and user interface is build with Bootstrap 3 with Less.
Demo
- Back office (login:
admin@example.com
, password:admin
) - Front office
- 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.4.0
- MCrypt PHP Extension
- Memcached or Redis or APC
-
Create an empty MySQL database
-
Create a new project
composer create-project sdebacker/typicms mywebsite
-
Enter newly created folder
cd mywebsite
-
DB Migrate and seed, create user, npm install, bower install and directory rights
php artisan typicms:install
-
Go to http://mywebsite.local/admin and log in.
-
Create an empty database
-
Download TypiCMS
git clone https://github.com/sdebacker/TypiCMS.git mywebsite
-
Enter newly created folder
cd mywebsite
-
Install dependencies with Composer
composer install
-
Set a new encryption key
php artisan key:generate
-
Change cache prefix in app/config/cache.php
php artisan cache:prefix yourCachePrefix
-
Rename .env.example to .env
mv .env.example .env
-
Fill in your database credentials in .env
-
Migrate and seed Database
php artisan migrate --seed
-
Set permissions
chmod -R 777 app/storage chmod -R 777 public/uploads
-
Go to http://mywebsite.local/admin and log in:
- email:
admin@example.com
- password:
admin
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 default locale in app/config/app.php
- Cache driver is set to memcached, you can change it to another taggable cache system such as redis in app/config/cache.php
Pages are nestable with drag and drop, on drop, uris are generated and saved in database. A page has routes for each translation.
Each menu have nestable entries. One entry can be linked to a module, page, URI or URL.
You can get a menu HTML formated with Menus::build('menuname')
.
An icon can easily be added to a menu item by filling icon class field.
Projects have categories, projects urls follows this pattern : /en/projects/category-slug/project-slug
Categories has many projects.
Tags are linked to projects and use Selectize jQuery plugin. It 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.
Files module allows you to upload multiple files, it uses DropzoneJS. 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 News module is properly set up to support galleries.
Sentry 2 is used to manage users, groups and permissions. Users registration can be enable through the settings panel (/admin/settings).
Blocks are usefull for custom content to display in your views.
You can get content of a block with Blocks::build('blockname')
.
Translations can be stored in 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 generate a sitemap file in xml format. Configure modules to add to the site map in app/config/sitemap.php file.
Change website title, and other options trough the settings panel. Settings are saved in database.
History table records changes and 25 latest are displayed in back office’s dashboard. Logged actions are created, updated, deleted, set online and set offline. It works for each modules excepted Users and Groups.
Modules that have their own Facade: News, Events, Projects, Places, Partners, Galleries, Blocks, Files and Menus.
In your views, 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
- Improve user interface
- Make modules as packages
- Build more tests
Feel free to fork and make pull requests directly on master branch! TypiCMS follows PSR-2 standard.
Thanks to elvendor and jekjek for their contributions!
Some admin controllers are actually tested, more tests needed.
TypiCMS is an open-source software licensed under the MIT license.