Laradic Themes for Laravel 5

I have started to collaborate on several packages. Laradic/Themes has been merged into Caffeinated\Themes@v3. It features almost all of Laradic\Themes its functionality. We however decided to decouple assets and provide it in a seperate package Caffeinated\Beverage, which is able to compliment Caffeinated\Themes.

Basic asset filesystem and url path resolving is the only asset related thing that still remains in the new Caffeinated\Themes package.

Laradic\Themes will be dropped.

Click here to go to the new repo/v3 branch

Version 0.3

Laravel 5 package providing multi-theme inherited cascading support for views and assets.

Easy and worry free setup Does not conflict with the standard Laravel view system.
Template Languages Works with PHP, Blade, Twig and any other view engine.
Cascading & Inheritance Themes are able to inherit all options from other themes, providing a smart and intuitive way to extend existing themes.
Asset Management Dependable assets or asset groups with caching, minification, filters(scss, less, etc), etc.
And much more...

Overview

Overview
Todo for 1.0
Installation
First time usage guide and explenation
- Inheritance system basics
- Cascade system basics
  - To create a namespace
  - To create package
Views/Themes
- Common methods overview
  - Themes (Facade => ThemeFactory)
  - Theme (instance of a theme)
Assets
- AssetGroup
The theme file
Navigation/Breadcrumbs
Console Commands
Copyright/License

Todo for 1.0

Installation

Composer

"laradic/themes": "0.3.*"

Laravel

Add the ThemesServiceProvider to your config.

Laradic\Themes\ThemeServiceProvider::class

Optionally, you can add any of the Facades below:

array(
    'Themes' => Laradic\Themes\Facades\Themes::class,
    'Asset' => Laradic\Themes\Facades\Asset::class,
);

Configuration

php artisan vendor:publish --tag="config"

<sub>[^](#top)</sub>

First time usage guide and explenation

Open up the laradic.config.php file. For first time use, just change the theme folder path to your desired location.

return array(
    // ...
    'paths'           => array(
        'themes'     => array(
            public_path('themes'), // change this to the desired location
            public_path()
        ),
        // ...
    )
);

Save it and run php artisan themes:init. This will generate a few folders and files matching the default config settings. It only serves as an example, showing the directory structure for a theme and theme view inheritance.

Loading a view file is the same as normal.

// The active theme is 'example/main'.
// It contains the index.blade.php file in the view folder.
// Which can be loaded like:
View::make('index');

Inheritance system basics

Load priority Active Theme View Folder > Parent Theme View Folder(if set) > Default Theme View Folder > Default Laravel View Folder

If you understand that, skip these points. Otherwise, more details about this:

If you open the index.blade.php file, you see it @extends layout.
If there was a layout.blade.php file in the same folder, it would use that one (duhh).
However, that's not the case right now. So the Theme manager will start looking in other theme directories if they have the file (with the same relative path).
It will first check the parent theme of 'example/main', defined in the theme.php file (or not, its optional).
If its not there either, it will check the default theme. Which in this case, has the layout.blade.php file.
If by any chance, the default folder doesn't have that file either, it will lastly check the standard Laravel view folder for that file.

The same goes for loading Views, Assets, etc.

Cascade system basics

To put it simply, every theme can have "sub-themes". Inside a theme folder, you notice the namespaces and packages folder.

To create a namespace

For example:

create the lingo folder inside the namespaces folder of the example/main theme.
Inside that folder, create the assets and views folder.
Create a myview.blade.php inside the view folder

View::make('lingo::myview')

Create a subdir/otherview.blade.php inside the view folder

View::make('lingo::subdir.otherview')

To create package

A package need to be in 2 directories.

So create the foo/bar folder inside the packages folder of the example/main theme.
Inside that folder, create the assets and views folder.
Create a hakker.blade.php inside the view folder

View::make('foo/bar::hakker')

Create a subdir/otherhakker.blade.php inside the view folder

View::make('foo/bar::subdir.otherhakker')

The same goes for assets

Views/Themes

The active and default theme can be set in the configuration by altering the active and default keys.
You can set the active theme on the fly by using Theme::setActive('theme/slug').
You can set the default theme on the fly by using Theme::setDefault('theme/slug').

// public/themes/{active/theme}/views/view-file.EXT
$view = View::make("view-file");

// public/themes/{active/theme}/namespaces/my-namespace/views/view-file.EXT
$view = View::make("my-namespace::view-file");

// public/themes/{active/theme}/packages/vendor-name/package-name/views/view-file.EXT
$view = View::make("vendor-name/package-name::view-file");

Themes::setActive("backend/admin");
$view = View::make("view-file"); // -> public/backend/admin/views/view-file.EXT
// etc

Common methods overview

Check out the API documentation for the full list of methods.

Themes (Facade => ThemeFactory)

Function call	Return type	Description
`Themes::setActive($theme)`	self	Set the active theme, `$theme` can be a Theme instance or the slug string of that theme
`Themes::getActive()`	Theme	Returns the active theme
`Themes::setDefault($theme)`	self	Set the default theme, `$theme` can be a Theme instance or the slug string of that theme
`Themes::getDefault()`	Theme	Returns the default theme
`Themes::resolveTheme($slug)`	Theme	Resolve a theme using it's slug. It will check all theme paths for the required theme.
`Themes::all()`	string[]	Returns all resolved theme slugs
`Themes::get($slug)`	Theme	Returns the theme instance if the theme is found
`Themes::has($slug)`	bool	Check if a theme exists
`Themes::count()`	int	Get the number of themes
`Themes::addNamespace($name, $dirName)`	self	Add a namespace to the theme
`Themes::getPath($type)`	string	Get a path for the type (assets, views, namespaces, packages)

Theme (instance of a theme)

Function call	Return type	Description
`Theme::getConfig()`	array	The array from `theme.php`
`Theme::getParentTheme()`	Theme	..
`Theme::getParentSlug()`	string	..
`Theme::hasParent()`	bool	..
`Theme::getSlug()`	string	..
`Theme::getSlugKey()`	string	..
`Theme::getSlugProvider()`	string	..
`Theme::getName()`	string	..
`Theme::isActive()`	bool	..
`Theme::isDefault()`	bool	..
`Theme::isBooted()`	bool	..
`Theme::boot()`	void	..
`Theme::getVersion()`	SemVer	..
`Theme::getPath()`	string	..
`Theme::getCascadedPath()`	string	..

Assets

The Asset Facade links to AssetFactory. It should not be confused with the Asset class that Asset::make returns, which actually holds asset data.

Note $path is the same as with Views (namespaces, packages, etc)

Function call	Return type	Description
`Asset::make($path);`	`Asset<FileAsset>`	Returns the asset instance
`Asset::url($path);`	string	Returns the asset URL
`Asset::uri($path);`	string	Returns the asset uri
`Asset::script($path, array $attr = [ ], $secure = false));`	string	Renders the asset in a `<script src="">` tag
`Asset::style($path, array $attr = [ ], $secure = false));`	string	Renders the asset in a `<link ..>` tag
`Asset::group($name);`	`AssetGroup`	Returns an AssetGroup, more details below
`Asset::addGlobalFilter($extension, $callback);`	void	Add global `Assetic` filter, to be applied on all assets with matching extension
`Asset::setCachePath($path);`	string	Returns the filesystem path to the asset file
`Asset::getCachePath();`	string	Returns the filesystem path to the asset file
`Asset::deleteAllCached();`	string	Returns the filesystem path to the asset file
`Asset::setAssetClass("Full\Class\Name");`	string	Returns the filesystem path to the asset file
`Asset::setAssetGroupClass("Full\Class\Name");`	string	Returns the filesystem path to the asset file

AssetGroup

Is used to group assets. Has several features you could use:

Depencency management
Minifaction & concenation
Caching

// I would advice to do this in theme.php its boot closure!
Asset::group('base')
    ->add('jquery', 'plugins/jquery/dist/jquery.min.js')
    ->add('bootstrap', 'plugins/bootstrap/dist/js/bootstrap.min.js', [ 'jquery' ])
    ->add('bootstrap', 'plugins/bootstrap/dist/css/bootstrap.min.css')
    ->add('bootbox', 'something::bootbox/bootbox.js', [ 'jquery', 'bootstrap' ])
    ->add('slimscroll', 'plugins/jquery-slimscroll/jquery.slimscroll.js', [ 'jquery' ])
    ->add('modernizr', 'plugins/modernizr/modernizr.js')
    ->add('moment', 'plugins/moment/moment.js')
    ->add('highlightjs', 'plugins/highlightjs/highlight.pack.js')
    ->add('highlightjs', 'plugins/highlightjs/styles/zenburn.css')
    ->add('sassStyle', 'sassStyle.scss');

Asset::group('ie9')
    ->add('respond', 'plugins/respond/dest/respond.min.js')
    ->add('html5shiv', 'plugins/html5shiv/dist/html5shiv.js');
    
// And continue somewhere else 
Asset::group('base')
    ->add('name', 'path');
    
    
// Other functions
$group = Asset::group('base');

$group->addFilter('scss', 'Assetic\Filters\ScssphpFilter')
$group->render($type, $combine = true); // type can be either: 'scripts' or 'styles'
$group->getFilters($fileExtension);
$group->get($type, $handle); // $handle is the name of the asset, which u entered as first parameter with add()
$group->getSorted($type); // get all assets of $type sorted by dependency
$group->getAssets($type); // get all assets of $type
$group->getName(); // get the name of group ('base')

// then in the view files you could do
<html>
<head>
    <link href='//fonts.googleapis.com/css?family=Lato:100' rel='stylesheet' type='text/css'>
    {!! Asset::group('base')->add('style', 'style.css')->render('styles') !!}

</head>
<body>
		<div class="container">
			<div class="content">
                <div class="info">
                    Using theme: {{ Themes::getActive()->getName() }}.
                    @if(Themes::getActive()->hasParent())
                        Using parent theme: {{ Themes::getActive()->getParentTheme()->getName() }}
                    @endif
                </div>
				<div class="title">
                    @section('content')
                        The layout
                    @show
                </div>
			</div>
		</div>

    <!--[if lt IE 9]>
    {!! Asset::group('ie9')->render('scripts') !!}
    <![endif]-->
    {!! Asset::group('base')->render('scripts') !!}
    {!! Asset::script('something::bootbox/bootbox.js') !!}
    
    <!-- Get the URL -->
    {!! Asset::url('something::bootbox/bootbox.js') !!}

    <!-- Get the URI -->
    {!! Asset::uri('something::bootbox/bootbox.js') !!}

    <!-- Dump the content -->
    Asset::make('bootbox', 'something::bootbox/bootbox.js')->dump()

    <!-- Dump some scss converted to css -->
    {!! Asset::make('sassStyle', 'sassStyle.scss')->dump() !!}
</body>
</html>

The theme file

Beside the obvious fields, the boot field is rather important. Use the boot field closure to register namespaces for your theme, define assets and asset groups, and other global stuff.

use Illuminate\Contracts\Foundation\Application;
use Laradic\Themes\Theme;

return [
    'parent'   => null,
    'name'     => 'Example theme',
    'slug'     => 'example/theme',
    'version'  => '0.0.1',
    'register' => function (Application $app, Theme $theme)
    {
    },
    'boot'     => function (Application $app, Theme $theme)
    {
        Themes::addNamespace('something', 'something');
        
        Asset::group('base')
            ->add('jquery', 'plugins/jquery/dist/jquery.min.js')
            ->add('bootstrap', 'plugins/bootstrap/dist/js/bootstrap.min.js', [ 'jquery' ])
            ->add('bootstrap', 'plugins/bootstrap/dist/css/bootstrap.min.css')
            ->add('bootbox', 'something::bootbox/bootbox.js', [ 'jquery', 'bootstrap' ])
            ->add('slimscroll', 'plugins/jquery-slimscroll/jquery.slimscroll.js', [ 'jquery' ])
            ->add('modernizr', 'plugins/modernizr/modernizr.js')
            ->add('moment', 'plugins/moment/moment.js')
            ->add('highlightjs', 'plugins/highlightjs/highlight.pack.js')
            ->add('highlightjs', 'plugins/highlightjs/styles/zenburn.css');

        Asset::group('ie9')
            ->add('respond', 'plugins/respond/dest/respond.min.js')
            ->add('html5shiv', 'plugins/html5shiv/dist/html5shiv.js');
    }
];

Navigation/Breadcrumbs

Console Commands

List publishers

php artisan themes:publishers

Publish a theme

php artisan themes:publish <publisher>

Creating a theme

php artisan themes:create <theme/slug> [path]

Creating the initial theme structure (ment as example)

php artisan themes:init

Name		Name	Last commit message	Last commit date
Latest commit History 52 Commits
resources		resources
src		src
tests		tests
.gitignore		.gitignore
.gitmodules		.gitmodules
.travis.yml		.travis.yml
LICENSE.md		LICENSE.md
README.md		README.md
composer.dev.json		composer.dev.json
composer.json		composer.json
phpunit.xml		phpunit.xml

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

Laradic Themes for Laravel 5

Click here to go to the new repo/v3 branch

Version 0.3

Overview

Todo for 1.0

Installation

Composer

Laravel

Configuration

First time usage guide and explenation

Inheritance system basics

Cascade system basics

To create a namespace

To create package

Views/Themes

Common methods overview

Themes (Facade => ThemeFactory)

Theme (instance of a theme)

Assets

AssetGroup

The theme file

Navigation/Breadcrumbs

Console Commands

List publishers

Publish a theme

Creating a theme

Creating the initial theme structure (ment as example)

Copyright/License

About

Releases

Packages

Languages

License

laradic-old/themes

Folders and files

Latest commit

History

Repository files navigation

Laradic Themes for Laravel 5

Click here to go to the new repo/v3 branch

Version 0.3

Overview

Todo for 1.0

Installation

Composer

Laravel

Configuration

First time usage guide and explenation

Inheritance system basics

Cascade system basics

To create a namespace

To create package

Views/Themes

Common methods overview

Themes (Facade => ThemeFactory)

Theme (instance of a theme)

Assets

AssetGroup

The theme file

Navigation/Breadcrumbs

Console Commands

List publishers

Publish a theme

Creating a theme

Creating the initial theme structure (ment as example)

Copyright/License

About

Resources

License

Stars

Watchers

Forks

Releases

Packages 0

Languages

Packages