View component is Orchestra Platform approach to deliver themeable application that support extensions. The functionality evolves by modifying how Illuminate\View\ViewFileFinder would resolve which file, which would first look into the current active theme folder, before resolving it cascading-ly.

This would allow extension (or even packages) to have it's own set of view styling while developer can maintain a standardise overall design through out the project using a theme.

1. Version Compatibility
2. Installation
3. Configuration
4. Usage
5. Change Log

Version Compatibility

Laravel	View
4.0.x	2.0.x
4.1.x	2.1.x
4.2.x	2.2.x
5.0.x	3.0.x
5.1.x	3.1.x
5.2.x	[email protected]

Installation

To install through composer, simply put the following in your composer.json file:

{
    "require": {
        "orchestra/view": "~3.0"
    }
}

And then run composer install from the terminal.

Quick Installation

Above installation can also be simplify by using the following command:

composer require "orchestra/view=~3.0"

Configuration

Next add the service provider in config/app.php.

'providers' => [

    // ...

    Orchestra\View\DecoratorServiceProvider::class,
    Orchestra\View\ViewServiceProvider::class,
    Orchestra\Memory\MemoryServiceProvider::class,
],

Usage

1. Basic of a Theme
2. Anatomy of a Theme
3. Asset Routing

Basic of a Theme

Default Theme

By default, the selected theme is default, and located at public/themes/default.

You might need to create the following folder when Theme is used outside of Orchestra Platform.

Manifest File

Each theme can have a manifest file, which provide Orchestra Platform the required information to properly use the theme.

{
  "name": "Default",
  "description": "Default Theme for Orchestra Platform",
  "author": "Orchestra Platform",
  "autoload": [
  ]
}

Autoloading Theme Configuration

There would be time where you would need to be able to customize Theme by adding additional helper or configuration. We can easily start files using the "autoload" options:

{
  "autoload": [
    "start.php",
    "helpers.php"
  ]
}

Based on above example, two files would be loaded on each request:

• public/themes/default/start.php
• public/themes/default/helpers.php

Anatomy of a Theme

The application views is accessible from the root path of your theme, while extensions/packages can be accessible from packages/{package-name} subfolder. So for example if your selected theme is default, and you plan to replace home.index and acme/foo::home.index view. Only the following file would be needed:

• public/themes/default/home/index.blade.php
• public/themes/default/packages/acme/foo/home/index.blade.php
• public/themes/default/theme.json
• public/themes/default/screenshot.png

As you can see, the file structure of the view follow closely cascading filesystem replacement structure used in many other framework.

Asset Routing

You are free to maintain where assets is located inside the theme folder as it is under public folder. To access the asset file, you can use the following snippet.

<script src="{{ Theme::to('assets/js/script.js') }}">
<!-- this would point to `http:://yourdomain.com/themes/default/assets/js/script.js` -->

Alternatively you can also use Theme::asset():

<script src="{{ Theme::asset('assets/js/script.js') }}">
<!-- this would point to `/themes/default/assets/js/script.js` -->