Sharp is not a CMS: it's a content management framework, a toolset which provides help building a CMS section in a website, with some rules in mind:
- the public website should not have any knowledge of the CMS — the CMS is a part of the system, not the center of it. In fact, removing the CMS should not have any effect on the project.
- The CMS should not have any expectations from the persistence layer: MySQL is cool — but it's not the perfect tool for every problem. And more important, the DB structure has nothing to do with the CMS.
- Content administrators should work with their data and terminology, not CMS terms. I mean, if the project is about spaceships, space travels and pilots, why would the CMS talk about articles, categories and tags?
- website developers should not have to work on the front-end development for the CMS. Yeah. Because life is complicated enough, Sharp takes care of all the responsive / CSS / JS stuff.
Sharp intends to provide a clean solution to the following needs:
- create, update or delete any structured data of the project, handling validation and errors;
- display, search, sort or filter data;
- execute custom commands on one instance, a selection or all instances;
- handle authorizations and validation;
- all without write a line of front code, and using a clean API in the PHP app.
Sharp 4 needs Laravel 5.4+ and PHP 7.0+.
Here's a series of blog posts which present Sharp following a simple example:
In Sharp, we handle entities; and entity is simply a data structure which has a meaning in the applicative context. For instance, a Person, a Post or an Order. In the Eloquent world, for which Sharp is optimized, it's typically a Model — but it's not necessarily a 1-1 relationship, a Sharp entity can represent a portion of a Model, or several Models.
Each instance of an entity is called... an instance.
Each entity in Sharp can be displayed:
- in an
Entity List, which is the list of all theinstancesfor thisentity: with some configuration and code, the user can sort the data, add filters, and perform a search. From there we also gain access to applicativecommandsapplied to aninstanceor the whole list, and to a simplestatechanger (the publish state of an Article, for instance). All of that is described below. - And in a
Form, either to update or create a newinstance.
- Add the package with composer:
composer require code16/sharp, - [Laravel 5.4 only] Register the service provider
Code16\Sharp\SharpServiceProviderin the provider array ofconfig/app.php, - Publish assets:
php artisan vendor:publish --tag=assets.
Sharp needs a config/sharp.php config file, mainly to declare entities. Here's a simple example:
return [
"entities" => [
"spaceship" => [
"list" => \App\Sharp\SpaceshipSharpList::class,
"form" => \App\Sharp\SpaceshipSharpForm::class,
"validator" => \App\Sharp\SpaceshipSharpValidator::class,
"policy" => \App\Sharp\Policies\SpaceshipPolicy::class
]
]
];As we can see, each entity (like spaceship, here), can define:
- a
listclass, responsible for theEntity List, - a
formclass, responsible for... theForm - and optionally:
- a
validatorclass, to handle form validation - and a
policyclass, for authorization.
- a
We'll get into all those classes in this document. The important thing to notice is that Sharp provides base classes to handle all the wiring (and more), but as we'll see, the applicative code is totally up to you.
- Building the menu
- How to transform data
- Sharp built-in solution for uploads
- Handling form data localization
- Testing with Sharp
- Style & Visual Theme
- Redefine Sharp theme (coming soon)