noodlewitt / bootlegcms Goto Github PK

A Laravel 5 CMS package.

License: MIT License

PHP 0.94% HTML 13.91% JavaScript 78.35% CSS 6.65% Makefile 0.06% Python 0.05% Shell 0.01% Batchfile 0.03% Ruby 0.01% PowerShell 0.01%

bootlegcms's Introduction

####Setup Instructions:

install & setup laravel laravel:

composer create-project laravel/laravel=5.0.22 mixtapes --prefer-dist

..then do database, migrations, etc

add in cms to composer:

composer require 'bootleg/cms:dev-master'

Remove contents of default laravel routes file:
```
app/Http/routes.php
```

Add in service providers: config/app.php:

//service providers
'Bootleg\Cms\CmsServiceProvider', 
'Collective\Html\HtmlServiceProvider'

//aliasses
'Form' => 'Collective\Html\FormFacade', 
'Html' => 'Collective\Html\HtmlFacade',

'permissions' => 'Bootleg\Cms\Middleware\Permissions',

Publish assets for cms:
```
php artisan vendor:publish
```
composer dump-autoload to make sure you've got all the migrations and config files included.
```
composer dump-autoload
```

===

You then should set up the database:

Run migration:
```
php artisan migrate
```

Run seeding:

php artisan db:seed --class="Bootleg\Cms\BootlegSeeder"

===

####You then need to make a theme or plugin.

######via Laravel 4.2's workbench: You can still use laravel 4's workbench to set up a theme.

composer.json:

composer require "illuminate/workbench:dev-master"

Add in service provider:

"Illuminate\Workbench\WorkbenchServiceProvider",

Create workbench config file config/workbench.php

<?php
return [
    'name' => 'Simon Davies',
    'email' => '[email protected]',
];

..and composer dump-autoload

Add run workbench command to create a workbench item:
```
php artisan workbench vendor/package --resources
```

Add this into composer.json

"autoload": {
    "classmap": [
        "workbench/vendor/package/src"
        ..
    ]
}

Optionally add this into the plugins table OR You can include it into config/app.php

######via Manual: You can of course create a plugin manually with whatever structure makes sense to you.. A base template for a theme can be found here: Sample theme.

bootlegcms's People

Contributors

Stargazers

Watchers

Forkers

chaddles23 niallkatana

bootlegcms's Issues

add application level redirect behaviour

..for easier redirection of urls etc.

Application settingfs update function

Nothing here yet. needs to be implemented.

user select2 for tags interface instead of current bootstraptags

it'll cut down on the amount of jquery plugins we are using. Also handles existing tags better.

currently using select2 for dropdowns anyways.

content_settings -> cast/mutate parameters as array automatically

See array casting:
http://laravel.com/docs/5.1/eloquent-mutators#attribute-casting

uploads if blank - seems to be adding in invalid file?

Review Tree Structure

Not sure Baum is the right tool for the job anymore - nested sets are painfully bad for updating - especially with regards to larger data sets and multi site functionality.

https://github.com/franzose/ClosureTable

add ability to add multiple themes/settings per application

probs another table that will allow for wp style plugins. woop.

review upload code.

Probably needs validation, allowed file types, file sizes etc. JSON object for this?

add grid view for multi-page-editing

needs extra col in content_settings table to track view index number

add in method to ignore csrf on given urls

Disable middleware for given urls maybe or something?

re-work new content item creation.

We don't want to create all the content items imediatly.. just use the ones that we've been given and add the rest from content_default_fields

Separate dashboard/logout functions from UsersController CRUD

May be more suitable to keep dashboard/logout functions in a base CMS controller, and keep User CRUD separate. Will make it easier to provide custom per-project User CRUD when necessary.

Add sections for fields.

Need some way of splitting the fields up into tabs and probably sections too.

add title column to settings field

so if they change the name field we don't have to update every field.

File handling abstraction

-is this worth doing with the s3 upload with L5?

add seeds for template table and new plugins table

Add in hooks for some actions

stuff like updating content, removing content, adding content

add image resizing

dunno yet if this needs to be client side or not.

Loading indicator when modifying content tree

Currently, when creating/moving/updating items in the content tree, a user can still interact with the tree while it is updating in the database. Any changes during this short period are not saved, and can cause a glitchy interface until the user refreshes.