impleri / laravel-base Goto Github PK

Life would be a lot easier if some things could be configured in one spot. Whenever possible, disagreeable things should be stuck into a config file so people can disagree without needing to hack the regular files.

No blog is complete without having some kind of taxonomy. Tags are all the rage these days, but some folks like those good old-fashioned categories, so make them both possible.

The base taxonomy resource would have a name (obviously), URL slug (for listing posts on a page), description, and a the ability to create them in a hierarchy (nested sets look nice and easy).

That AJAX stuff from #2 is great, but it'd be even better if it meant we can do straight inline WYSIWYG in the UI (provided the user has the right permissions) that syncs via Backbone. This won't work for every single thing, but since we've moved all CRUD handling to API routes which can do the forms (oh so 2002!) or AJAXy JSON magic, let's focus users to the shiny things.

Whether blog posts, news updates, or something else, a lot of websites like to have a dynamic collection that looks and feels different from a regular page. A good base post resource would have a title (obviously), URL slug, lead image, status (active/etc), author reference, created and modified dates, taxonomy/tags, body (also obviously), and a summary (either auto-generated or manually set). Also, these should be revisionable and auto-savable so that users can revert bad edits.

With all of the really awesome features available in JavaScript packages such as Backbone, we should never need to wait for the backend server to perform.

Ideally, we will have Backbone structured to interact with the Laravel API backend so as many CRUD actions as possible occur behind the scenes, on the fly, and whatever hip terms can be used for the Web X.Y slang.

Most data entities should be accessible via a simple, generic resource handling that covers the basics of creating and controlling RESTful routes, performing CRUD actions on the model, and view template shells.

The goal is that a developer can add a new resource, such as 'blog post' without needing to build out or copypasta the repetitive portions.

What website doesn't have a basic page? A good base page resource would have a title (obviously), URL slug, lead image, status (active/etc), author reference, created and modified dates, body (also obviously), and a summary (either auto-generated or manually set). They should also have a revision history.

So, like, everyone in the world has a device with a different screen. The template skeleton and CSS should be responsive out of the box.