A simple command line, markdown based blog add-on package for Laravel including support for tags and series of related posts.

Include the package via composer:

composer require "saywebsolutions/letsblog" 

Add the service provider to config/app.php:

'providers' => [ ...	SayWebSolutions\LetsBlog\Providers\LetsBlogServiceProvider::class,	... ] 

The best way to get a sense of the config options is to publish the config and take a look at the file:

php artisan vendor:publish --provider="SayWebSolutions\LetsBlog\Providers\LetsBlogServiceProvider" --tag=config 

Find the config file in config/letsblog.php.

php artisan migrate --path=/vendor/saywebsolutions/lets-blog/database/migrations 

Your main blade layout must be named app.blade.php for the default theme to work out of the box; if not, there is a config key theme_extends that will allow you to define the blade layout to extend.

Navigate to /blog and see the default blog page.

Write posts using the markdown format, and by default posts should go in the ./blog/posts directory.

After adding/editing a post run the letsblog:build command to add the new post(s) and/or apply your edits:

php artisan letsblog:build 

The main key used for checking existing posts will be the identifier field which by default uses the filename.

The post format should look like the following:

--- title: LetsBlog Package Released slug: letsblog-package-released-laravel meta: LetsBlog package released for Laravel. keywords: letsblog, package, laravel, release published_at: 2018-03-17 tags: LetsBlog, Laravel --- ## Post Title Post contents... 

You can set any fields in the top section (front matter) of the file. The available parsers recieve the data defined in the front matter for each field, and can manipulate that data prior to being saved to the posts table.

Current parsers are:

• Title
• Meta (description)
• Body
• PublishedAt
• Slug (if not defined will fallback to filename)
• Tags
• Series (optional name of the series to which to post belongs)

The migration can be run directly from the packages migrations folder:

php artisan migrate --path=/vendor/saywebsolutions/lets-blog/database/migrations php artisan migrate:rollback 

If the migrations need to be published to the parent app, use the vendor:publish command:

php artisan vendor:publish --provider="SayWebSolutions\LetsBlog\Providers\LetsBlogServiceProvider" --tag=migrations 

To set a theme set the 'letsblog.theme' property in the config. To simplify things ALL views should simply use letsblog::theme.master as the main view. Then a view is set as part of the data sent to the view.

return view('letsblog::themes.master', [ 'view' => lb_view('post.show'), ]); 

The lb_view is a shortcut helper to use to avoid having to set the full path with the theme each time. This allows easy swapping of themes by only having to change the config parameter.

So far the currently supported themes are:

• default
• extension

The default theme is currently untested, and may or may not be working.

The extension theme is useful if you have an existing blade layout you'd like to embed the blog in. Right now the extension theme expects Bootstrap 3 to be available in the parent application.

Make sure to have a yield directive for javascript in your parent layout, ex.):

@yield ('javascript') 

In many cases you will want to add some customization to the layout to include some analytics tracking or ads for instance. To allow this the themes include many section blocks that can replace or modify existing layout.

To start, create an overrides file in the views directory:

/resources/views/vendor/lets-blog/themes/overrides.blade.php 

From there the following section blocks can be used which hopefully are self explanatory.

• meta.opensearch
• meta.title
• meta.keywords
• meta.description
• meta.og
• head.files
• head.styles
• sidebar.series
• sidebar.popular
• component.search
• component.related
• footer-nav.left
• footer-nav.right
• post.list
• post.head
• post.series
• post.body
• post.related
• page.head
• page.body
• layout.view
• layout.end

For customization the LetsBlog facade may be used.

'aliases' => [ 'Blog' => SayWebSolutions\LetsBlog\Facades\LetsBlogFacade::class, ... ] 

The facade provides access to the following shortcut functions:

• published() - Paginated list of posts.
• search($q) - Paginated list of posts by search.
• all() - All posts.
• last() - Last post (by published_at date).
• post($slug) - Post or page by slug.
• count() - Post count.
• top($amount) - Top posts (default 10).
• tags() - All tags.
• publishedWhereTag($tag) - Paginated list of posts by tag.

Publish all files from the package:

php artisan vendor:publish --provider="SayWebSolutions\LetsBlog\Providers\LetsBlogServiceProvider" 

Or publish separately:

php artisan vendor:publish --provider="SayWebSolutions\LetsBlog\Providers\LetsBlogServiceProvider" --tag=migrations php artisan vendor:publish --provider="SayWebSolutions\LetsBlog\Providers\LetsBlogServiceProvider" --tag=views php artisan vendor:publish --provider="SayWebSolutions\LetsBlog\Providers\LetsBlogServiceProvider" --tag=config php artisan vendor:publish --provider="SayWebSolutions\LetsBlog\Providers\LetsBlogServiceProvider" --tag=assets 

Each theme should also support a header and footer section (and perhaps more standard sections to follow). The idea is that a list of views can be provided and they will be included in that order.

This allows the inclusion of any ads or analytics tracking codes.

To add a parser, create a class with the name of the key being parsed. So title would look for SayWebSolutions\LetsBlog\Parser\Field\Title. This way additional fields may be added or existing ones overridden.

Some things that still need to be done.

• Admin section (with WYSIWYG MD editor)
• Additional themes
• Comments