Laravel Blog

This package has been designed for use with installations of Laravel 5.4 and above. It may well function perfectly well in previous versions but as of the time of writing these docs, it has not been tested and is not supported.

• Installation
• Usage
  • Frontend Routes
  • Backend Routes
• Policies
• Configuration
• Events
• Marking Posts per Site

Installation

This package can be used in Laravel 5.4 or higher.

In Laravel 5.5 the service provider and facade will automatically get registered. In older versions of the framework just add the service provider and facade in config/app.php file:

'providers' => [
    // ...
    Lnch\LaravelBlog\LaravelBlogServiceProvider::class,
];

'aliases' => [
    // ...
    Lnch\LaravelBlog\LaravelBlogFacade::class
]

Once the package is installed, the database migrations must be run. You can optionally publish the migrations to your database/migrations directory if desired using the command below

php artisan vendor:publish --tag="laravel-blog/migrations"

To create the relevant DB tables for the blog, run the migrations like so:

php artisan migrate

For the blog to function properly, you must also publish the public assets provided. These will be published to the public/vendor/lnch/laravel-blog directory. Run the following command to publish the assets:

php artisan vendor:publish --tag="laravel-blog/public"

If you are using the provided layouts then you do not need to reference these public files after publishing them. If you are using a custom layout (explained below in the config section), you will have to reference the CSS and JS files like so in your layout:

<link rel="stylesheet" href="{{ asset("vendor/lnch/laravel-blog/css/styles.css") }}" />

<script src="{{ asset("vendor/lnch/laravel-blog/js/blog.js") }}"></script>

The package also makes use of jQuery so you will also need to reference this before the package JS file if you are using your own layouts.

Usage

After installation, a set of routes, controllers and views are provided to allow instant use of the package. All controllers referenced are namespaced to Lnch\LaravelBlog\Controllers The routes provided are as follows:

Frontend Routes

Backend Routes

All backend routes, excluding scheduled posts, are resource routes. Not all HTTP verbs are included with each resource controller. Excluded routes are noted below.

For more in depth instruction in how to use the various features of the package, please read the documentation pages

Policies

A number of Policy classes are included, that by default will allow all actions to all users. If you would like to define your own Policy classes for the included models, a set of interfaces are provided to ensure your policies contain all necessary functionality.

Refer to the table below to see which interfaces you should implement for each model

Configuration

To modify the configuration of the package, you can publish the config file with the following command:

php artisan vendor:publish --tag="laravel-blog/config"

This will create a local copy of the configuration file for you to edit. That you can modify to suit your needs. The config file is commented to assist you in modifying the properties.

Events

A number of events are provided to allow you to hook your own custom functionality into the Blog process. The events, and their properties are listed below

Marking posts per Site

If your project has a concept of multiple sites, and you want to restrict posts, tags, categories and images only to a certain site, the package is set up for that.

To being with, create a new class that implements Lnch\LaravelBlog\Contracts\SiteInterface. This contract only has one public static function, with the following signature;

public static function getSiteId();

Your model should use this function to define the ID of the Site you wish to link blog posts too at the time. The function should return either NULL or an integer to define the active site.

Once you have created your model, you will have to update two configuration properties as so:

    // ...
    
    'site_model' => Lnch\LaravelBlog\Models\Site::class,
    
    'site_primary_key' => 'id',

Update the site_model to the qualified class name of your site class, and if your Site model uses something other than id as it's primary key, change the site_primary_key property to represent this.