Add laravelcollective/html dependency, update documentation

Author: mikebronner

CHANGELOG.md

@@ -1,6 +1,11 @@
 # Change Log
 [Package Checklist](http://phppackagechecklist.com)
 
+## [0.1.8] - 29 Sep 2015
+### Added
+- "laravelcollective/html" as a package dependency.
+- moved documentation to https://governor.forlaravel.com.
+
 ## [0.1.0] - 1 Sep 2015
 ### Added
 - Commit initial code, derived from the Bones-Keeper package.

README.md

@@ -3,91 +3,13 @@
 
 ![governor for laravel](https://cloud.githubusercontent.com/assets/1791050/9620997/05b36650-50d6-11e5-864b-f15bd9622d08.jpg)
 
-## Overview
-### Goal
+## Goal
 Provide a simple method of managing ACL in a Laravel application built on the Laravel Authorization functionality.
 By leveraging Laravel's native Authorization functionality there is no additional learning or implementation curve. All
 you need to know is Laravel, and you will know how to use Governor for Laravel.
 
-### Reasoning
-I was looking for a straight-forward approach to ACL management that didn't require extensive customization,
-configuration, or even project rewrites. The following criteria shaped the development of this package:
-- Provide drop-in capability, so you can equally add it to existing or new Laravel projects without issues.
-- Allow granular access management, yet keep it simple to use.
-- Provide an administrative front-end out-of-the box.
-
-### Considerations
-#### User Requirements
-- You must have at least 1 (one) user in your users table. The user with the lowest ID will become your admin by default.
-  This can be changed after the installation, of course.
-
-#### Tables
-You must add a `created_by` column to each of your tables. I purposefully chose not to write a 'magical' migration that
-would do all this for you, as that could lead to problems. However, I have added such a migration at the end to give you
-a solid starting point.
-
-#### User Model
-Your user model (most often `User.php`) should implement the Governable and Authorizable traits:
-```php
-<?php namespace App;
-
-use GeneaLabs\LaravelGovernor\Governable;
-use Illuminate\Auth\Authenticatable;
-use Illuminate\Auth\Passwords\CanResetPassword;
-use Illuminate\Contracts\Auth\Access\Authorizable as AuthorizableContract;
-use Illuminate\Contracts\Auth\Authenticatable as AuthenticatableContract;
-use Illuminate\Contracts\Auth\CanResetPassword as CanResetPasswordContract;
-use Illuminate\Database\Eloquent\Model;
-use Illuminate\Foundation\Auth\Access\Authorizable;
-
-class User extends Model implements AuthenticatableContract, AuthorizableContract, CanResetPasswordContract
-{
-    use Authenticatable;
-    use Authorizable;
-    use CanResetPassword;
-    use Governable;
-
-    // [...]
-}
-```
-
-#### Models
-The `create` methods in your models will automatically add the created_by user ID. To prevent this, add the following to
-your models that do not have a `created_by` column in their table:
-```php
-    protected $isGoverned = false;
-```
-
-#### Routes
-This package adds multiple routes under `genealabs/laravel-governor`. Please verify that these don't collide with any of
-your existing routes.
-
-#### Policies
-Your policy classes must extend `GeneaLabs\LaravelGovernor\Policies\LaravelGovernorPolicy`, and call the
-`validatePermissions` method. Please see the example policy class below. As you can see, all your policies are very
-straightforward, clean, and easy to understand. Governor and Laravel take care of all the dirty work for you.
-
-## Features
-Governor for Laravel takes full advantage of the Authorization functionality added to Laravel 5.1.12 and provides full
-User/Roles management. It lets you specify the policies using the native Authorization mechanisms, and lets you
-granularly manage user access to the various parts of your system.
-
-### Entities
-![screen shot 2015-09-01 at 18 46 40](https://cloud.githubusercontent.com/assets/1791050/9621341/25faf32a-50da-11e5-9c4c-cb1b8ac0c0e0.png)
-You define a list of entities, named after your Policy classes. This is not a requirement, but helps keep things organized.
-
-### Roles
-![screen shot 2015-09-01 at 18 47 09](https://cloud.githubusercontent.com/assets/1791050/9621338/21878380-50da-11e5-86bc-e2c0cd11635a.png)
-Roles are basically your user-groups. Two roles are created out of the box (these cannot be removed):
-- Superadmin: is set up with the user with the lowest ID by default. You can add more users as necessary.
-- Members: all users are by default members. You cannot remove users from the Members group.
-
-![screen shot 2015-09-02 at 10 28 52](https://cloud.githubusercontent.com/assets/1791050/9638813/77f0d928-515d-11e5-95c8-ab00289a5fad.png)
-Editing each role will let you specify granular access to each policy.
-
-### Assignments
-![screen shot 2015-09-01 at 18 48 18](https://cloud.githubusercontent.com/assets/1791050/9621369/73eed088-50da-11e5-8bd1-72c61edd3548.jpg)
-Assignments tie users to roles; this is where you add and remove users to and from roles.
+## Documentation
+Please see https://governor.forlaravel.com for complete documentation.
 
 ## Installation
 ```sh

composer.json

@@ -11,7 +11,8 @@
   "require": {
     "php": ">=5.5.9",
     "genealabs/bones-macros": "^0.2.33",
-    "illuminate/support": "^5.1"
+    "illuminate/support": "^5.1",
+    "laravelcollective/html": "^5.1"
   },
   "require-dev": {
     "orchestra/testbench": "~3.1",