Download the PHP package chriskelemba/laravel-ui-kit without Composer

On this page you can find all versions of the php package chriskelemba/laravel-ui-kit. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of chriskelemba/laravel-ui-kit

Informations about the package laravel-ui-kit

Laravel UI Kit

Blade-first UI components for Laravel. Includes a full set of atoms, molecules, organisms, and templates with Tailwind + Alpine.

Install

No publishing required. Components, Alpine, and the bundled UI Kit stylesheet are auto-registered.

Usage

Hyphenated tags (recommended)

Namespaced tags

Component Inventory

Atoms

Molecules

Organisms

Templates

Config (optional)

You can publish config and views if you want to customize:

Theming

UI Kit supports per-project brand theming through config, so different consumers can use different color schemes without editing package views.

Publish the config:

Then set your project colors in config/ui-kit.php:

If you use the package layout, theme styles load automatically.

If you use your own app layout, add this once inside <head>:

Then package components like primary buttons, active steps, charts, progress bars, sidebars, and focus states will use your project colors automatically.

Icon Aliases

Navigation-style components can resolve simple icon names to Font Awesome automatically.

If icon is omitted, UI Kit will also try to map the icon from the item label. Raw SVG or HTML icons still work and take precedence.

Dual Sidebar Layouts

The app shell supports optional left and right navigation regions.

For a right-side mirrored setup, render the rail and sidebar using the right slots and pass side="right":

If the right side should behave like a contextual helper section instead of another nav list, switch the sidebar organism into panel mode:

Shell Templates

UI Kit also includes a higher-level shell template for multi-pane layouts where you want a primary rail, contextual navigation, a top bar, and an optional helper panel without wiring each region by hand:

You can pass your own navigation arrays, branding, labels, badges, helper rail items, and helper panel blocks to shape the shell for any module in your app.

Custom Profile Menu Actions

Consumers can customize the profile dropdown menu in ui-kit::templates.module-workspace instead of being limited to the built-in profile and logout links.

Each menu item supports:

If profileMenuItems is not provided, the package keeps the current fallback behavior and builds the menu from profileEditHref and profileLogoutHref.

Module Workspace

x-ui-kit::templates.module-workspace is the first-class Blade entry point for app-style modules like dashboards, inventory screens, and operations workspaces.

The recommended pattern is to shape one page contract in your controller and let the Blade layout render it, instead of querying models or inferring route state inside the view.

Then render the shell from your layout:

This keeps the frontend contract explicit, makes pages easier to hand off between backend and frontend teammates, and makes it easier to reuse the same backend data in Vue or another client later.

Workspace Profile Menu

The workspace shell profile menu resolves the current authenticated user automatically when auth is available. If the host app has no logged-in user, it falls back to Default User and uses the first letter of the resolved name as the avatar.

Consumers can support different user shapes by publishing and editing config/ui-kit.php:

You can also override the profile per render:

For apps without named routes, pass direct URLs instead:

workspace-shell also supports two named slots for dynamic page controls:

Use actions for header controls and floating for pinned corner UI such as quick-create buttons.

For a consumer-controlled details panel, workspace-shell also accepts a custom right sidebar body:

Use rightSidebarContent when the consumer wants to fully own the sidebar body instead of relying on the package block renderer.

For consumers who do not want to build full primaryRailItems and sidebarSections arrays, UI Kit also includes a simpler workspace wrapper:

Use module-workspace when the consumer wants a simpler entrypoint built around one navigation array instead of assembling the lower-level shell structure manually.

Auth Pages

UI Kit includes an auth template that gives consumers a flexible shell for login, register, forgot-password, and other auth views without forcing one fixed design.

It supports:

Set shared branding once in config/ui-kit.php:

Then render an auth page:

Placement and size are now package-level options, so a consumer can shift the auth content without rebuilding the template:

If a consumer wants a different auth logo than the main app brand, they can override it per page:

If they want total visual control, they can replace the background or logo regions with slots:

Requirements

All versions of laravel-ui-kit with dependencies

PHP Build Version
Package Version
Requires php Version ^8.2
illuminate/support Version ^11.0|^12.0|^13.0
illuminate/view Version ^11.0|^12.0|^13.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package chriskelemba/laravel-ui-kit contains the following files

Loading the files please wait ...