PHPackages                             akitikkx/frontend - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. akitikkx/frontend

ActiveLibrary[Utility & Helpers](/categories/utility)

akitikkx/frontend
=================

The frontend interface to be used for all frontend clients for AECMS

028PHP

Since Mar 17Pushed 5y ago1 watchersCompare

[ Source](https://github.com/akitikkx/Laravel-CMS-Livewire-Frontend)[ Packagist](https://packagist.org/packages/akitikkx/frontend)[ RSS](/packages/akitikkx-frontend/feed)WikiDiscussions main Synced 1w ago

READMEChangelogDependenciesVersions (1)Used By (0)

Install Frontend package
------------------------

[](#install-frontend-package)

From the root directory of your project, run the following:

```
composer require akitikkx/frontend

```

then run:

```
php artisan vendor:publish

```

then select the option with:

```
Provider: Akitikkx\Frontend\FrontendServiceProvider

```

This should automatically generate the following view files which will be need to get the component to work:

```
- resources/views/layouts/livewire/frontend.blade.php
- resources/views/layouts/livewire/frontend-section.blade.php
- resources/views/layouts/app.blade.php
- resources/views/layouts/frontend.blade.php

```

as well as the following classes:

```
- app/Http/Livewire/Frontend
- app/Http/Livewire/FrontendSection
- app/Models/Page
- app/Models/PageSection

```

NB: Note that the namespace needs to be changed to match the project's namespace, such as `App\Http\Frontend` and to add `use App\Models\PageSection;`to `App\Http\Livewire\PageSection`

### Run the migrations

[](#run-the-migrations)

```
php artisan migrate

```

the table 'pages' should be createdb after the migration is complete.

Install Livewire
----------------

[](#install-livewire)

```
php artisan jetstream:install livewire

```

the output should be the following:

```
Livewire scaffolding installed successfully.
Please execute 'npm install && npm run dev' to build your assets.

```

Then run:

`npm install && npm run dev`

Output should be similar to the following:

```
✔ Compiled Successfully in 6130ms
┌─────────────────────────────────┬──────────┐
│                            File │ Size     │
├─────────────────────────────────┼──────────┤
│                      /js/app.js │ 673 KiB  │
│                     css/app.css │ 3.88 MiB │
└─────────────────────────────────┴──────────┘
webpack compiled successfully

```

and the following view files should have been created automatically:

- `resources/views/layouts/guest.blade.php`
- `resources/views/policy.blade.php`
- `resources/views/terms.blade.php`

Using FrontendSection component
-------------------------------

[](#using-frontendsection-component)

The idea behind FrontendSection is to be able to add a block of content into a specified area. This component aims to make it possible to have content sections or blocks leveraging Livewire.

To call the component and have it added to a section of the HTML, simply add the following:

```
@livewire('frontend-section', ['urlslug' => 'this-is-the-fancy-title', 'title_class' => 'my-4 text-5xl
            font-bold leading-tight', 'content_class' => 'leading-normal text-2xl mb-8'])

```

where `this-is-the-fancy-title` is the `slug` from the page section you want to display from the `page_sections` table, the css class for the `title` is defined with `title_class` and the css class for the body of the `content` is defined with `content_class`.

###  Health Score

17

—

LowBetter than 6% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity7

Limited adoption so far

Community4

Small or concentrated contributor base

Maturity30

Early-stage or recently created project

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

### Community

Maintainers

![](https://www.gravatar.com/avatar/4a55f289c451fa4987f04a573a7b30b86540e2d3540aff70eb504bcfbc72fe26?d=identicon)[akitikkx](/maintainers/akitikkx)

### Embed Badge

![Health badge](/badges/akitikkx-frontend/health.svg)

```
[![Health](https://phpackages.com/badges/akitikkx-frontend/health.svg)](https://phpackages.com/packages/akitikkx-frontend)
```

###  Alternatives

[aktuba/php-puppeteer

Extend puphpeteer

182.5k](/packages/aktuba-php-puppeteer)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)