Download the PHP package jasminecms/jasmine without Composer

Jasmine CMS

A Laravel based CMS inspired by Voyager.

Screenshots

Login

Bread index

Bread Edit

Requirements

• PHP >= 8.4
• Laravel >= 13

Note

Jasmine uses alexusmai/laravel-file-manager
If you are using it already or planning to,
you might need to tweak some configurations to prevent conflicts.

Installation

Require JasmineCMS in your new or existing laravel app
composer require jasminecms/jasmine

Publish the config file (optional, to customize routes and other options)
php artisan vendor:publish --tag=jasmine-config

Link jasmine public assets to your public folder
php artisan jasmine:link-public-assets

Migrate the database (be sure to make any changes to the default laravel migration prior)
php artisan migrate

Create a user (1st user is super admin)
php artisan jasmine:create-user

You can now log in to Jasmine,
Navigate to /jasmine
And login

Routes

Unlike previous versions, Jasmine now registers its web and api routes automatically.
No need to add anything to your route files.

You can control registration, prefixes and middleware via the config file:

Set register to false if you prefer to register the routes yourself using Jasmine::routes() and Jasmine::apiRoutes().

API documentation

When api routes are registered, Jasmine generates an OpenAPI specification for all jasmine.api.* routes using Scramble:

• Interactive docs UI: /{api-prefix}/docs
• OpenAPI JSON spec: /{api-prefix}/api.json

The docs are only visible to authenticated Jasmine users.

Registering assets

You can register Jasmine assets in your AppServiceProvider.

Locales (content)

Jasmine supports multilingual content, define your content languages like so

Interface locale

Jasmine's interface language files are simple JSON files.
To add or override an interface locale, place a {locale}.json file in:

Jasmine will automatically pick up any locale files in that directory, alongside its built-in locales. To get started quickly, publish the built-in locale files and edit or copy them:

Breadables

Breadables can be any model

In your model implement
Jasmine\Jasmine\Bread\BreadableInterface
use trait Jasmine\Jasmine\Bread\Breadable
if the model has multilingual columns, also use trait
Jasmine\Jasmine\Bread\Translatable;
implement missing methods

then register your model in AppServiceProvider

Registering a breadable automatically registers its permissions (browse, read, edit, add, delete) and, unless disabled, a sidebar menu item that is hidden from users lacking the browse permission.

Pages

Pages are very similar to models, but function as a single entity instead of a table

Register your pages in AppServiceProvider

Registering a page automatically registers its permissions (read, edit, add) and, unless disabled, a submenu item under the "pages" sidebar menu that is hidden from users lacking the read permission.

Custom assets

If for some reason you wish to load custom javascript or css you can do it like so

Paths should be absolute URLs (prefer https).

Permissions

Permissions are simple dot-notated string keys:

Registered permissions are automatically rendered in the role edit screen as grouped switches — each dot segment becomes a group.

Breadables and pages register their own permissions automatically (models.{key}.{browse|read|edit|add|delete} and pages.{slug}.{read|edit|add}).

You can check permissions on a user with $user->jCan('models.post.edit').

SideBarMenuItems

You can add items to the sidebar menu like so

Items accept: title, href, target, icon, class, hidden, is-route.
The third argument is the item's priority (lower = higher in the menu, default 50).
Items with hidden => true (or no href) are not rendered — handy for permission checks:

Submenu items

You can nest items under a parent menu item:

Registration order doesn't matter — submenu items are merged into their parent lazily, so you can register children before the parent (or from different service providers).
A parent with no visible children is not rendered.

Jasmine ships with a few built-in parent items you can attach submenu items to: pages (priority 30), jasmine (55) and tools (60).

Dashboard cards

Dashboard cards let you add widgets to the Jasmine dashboard.
A card is either a blade card (server rendered HTML) or a vue card (a Vue SFC rendered client side).

Card options

• ->width(int) — grid width in columns, 1–12 (cards are always full width on mobile). Default 4.
• ->priority(int) — display order, lower comes first. Default 50.

Card actions

Cards can expose server side actions, callable from the card's frontend:

• ->get($name, $handler) — read-only action (cacheable, no CSRF token)
• ->post($name, $handler) — mutating action
• ->action($name, $handler, $method) — any of GET, POST, PUT, DELETE

Route groups

You can register your own route groups inside Jasmine's route scope — useful both for packages extending Jasmine and for app specific admin routes.
Groups are registered in one of three scopes:

Groups can optionally be named, which allows replacing or removing them (registering the same id twice throws a LogicException):

unregisterApiRouteGroup(), unregisterGuestRouteGroup() and resetRouteGroups() are also available.

Oauth2 SSO

You can register oauth2 providers to enable sso login to jasmine

Facebook example