PHPackages                             lightgear/theme - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility &amp; Helpers](/categories/utility)
4. /
5. lightgear/theme

ActiveLibrary[Utility &amp; Helpers](/categories/utility)

lightgear/theme
===============

Easy theme Management for Laravel 4

2.0.0(12y ago)9731PHPPHP &gt;=5.3.0

Since Nov 6Pushed 12y ago1 watchersCompare

[ Source](https://github.com/lightgear/theme)[ Packagist](https://packagist.org/packages/lightgear/theme)[ RSS](/packages/lightgear-theme/feed)WikiDiscussions master Synced 4d ago

READMEChangelogDependencies (2)Versions (4)Used By (0)

Drop-in theme support for Laravel 4
===================================

[](#drop-in-theme-support-for-laravel-4)

Overview
--------

[](#overview)

The Lightgear Theme package adds support for themes to a Laravel 4 application.

Features
--------

[](#features)

- Views overrides for both **app** and **packages**
- Theme assets (css, less and js) support via [Lightgear Asset](https://github.com/lightgear/asset) package

Installation
------------

[](#installation)

### Via Laravel 4 Package Installer

[](#via-laravel-4-package-installer)

```
php artisan package:install lightgear/theme
```

### Manual

[](#manual)

Just require

```
"lightgear/theme": "dev-master"
```

in your composer.json and run

```
composer update
```

Then register the service provider

```
'Lightgear\Asset\ThemeServiceProvider'
```

and, optionally, the alias

```
'Theme' => 'Lightgear\Theme\Facades\Theme'
```

in **app/config/app.php**

Important: regardless of the installation method, until I find a better way to handle this, make sure to have the ThemeServiceProvider as **the last registered** or, at least, **after the service providers containing the views you want to override**.
This is needed in order to override the packages' views.

Usage
-----

[](#usage)

First create the directory that will contain your themes. By default this is "themes" located in the application root but this can be changed in the config file. A tipical theme structure would be:

```
themes
  |__mytheme
     |__css/
     |__less/
     |__js/
     |__views/
     |__info.php
```

As you notice each theme must have an **info.php** file with the following contents:

```
return array(
    'name' => 'My theme',
    'description' => 'A good desc',
    'author' => 'Donato Rotunno',
    'version' => 1.0,
    'styles' => array(
        'paths' => array(
            'less',
            'css'
        ),
        'package' => 'mytheme',
        'group' => 'frontend' // optional asset group
    ),
    'scripts' => array(
        'paths' => array(
            'js',
        ),
        'package' => 'mytheme',
        'group' => 'frontend' // optional asset group
    ),
);
```

This is a pretty simple structure. For more information about the theme assets, please refer to [Lightgear Asset](https://github.com/lightgear/asset) documentation.

Views overrides
---------------

[](#views-overrides)

To override any views (be it from app or package) just create the corresponding file in the views directory.
For example, to override the view **package::posts.index** just create the file **views/package/posts/index.php**. The same goes with the views located in the app. The view **posts.index** would be overridden in **views/posts/index.php**.

Configuration
-------------

[](#configuration)

Both the themes directory and the active theme can be set in the config file.

Changelog
---------

[](#changelog)

0.5: initial release

###  Health Score

29

—

LowBetter than 59% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity15

Limited adoption so far

Community8

Small or concentrated contributor base

Maturity60

Established project with proven stability

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~51 days

Total

2

Last Release

4522d ago

Major Versions

0.5 → 2.0.02013-12-28

### Community

Maintainers

![](https://www.gravatar.com/avatar/0dd711f6813d8f62e12e22c2646641f7960e95969e2c823b07d5f4bd063d2cc7?d=identicon)[ralf57](/maintainers/ralf57)

---

Top Contributors

[![ralf57](https://avatars.githubusercontent.com/u/208237?v=4)](https://github.com/ralf57 "ralf57 (17 commits)")

### Embed Badge

![Health badge](/badges/lightgear-theme/health.svg)

```
[![Health](https://phpackages.com/badges/lightgear-theme/health.svg)](https://phpackages.com/packages/lightgear-theme)
```

###  Alternatives

[barryvdh/laravel-ide-helper

Laravel IDE Helper, generates correct PHPDocs for all Facade classes, to improve auto-completion.

14.9k123.0M687](/packages/barryvdh-laravel-ide-helper)[orchestra/canvas

Code Generators for Laravel Applications and Packages

21017.2M158](/packages/orchestra-canvas)[illuminate/pipeline

The Illuminate Pipeline package.

9446.6M213](/packages/illuminate-pipeline)[illuminate/pagination

The Illuminate Pagination package.

10532.5M862](/packages/illuminate-pagination)[spatie/laravel-pjax

A pjax middleware for Laravel 5

513371.8k11](/packages/spatie-laravel-pjax)[spatie/laravel-mix-preload

Add preload and prefetch links based your Mix manifest

169176.0k2](/packages/spatie-laravel-mix-preload)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
