README

PUAN.TECH is a Composer plugin for Laravel projects that installs a ready-to-use frontend admin template and converts the selected template into a structured Blade layout using @extends, @include, sections, and reusable view partials.

The project is intentionally frontend-only. It does not create or modify models, controllers, migrations, seeders, or database tables.

Status: pre-release / active development.

Planned installation experience

After the first stable release is published to Packagist:

composer require puan/tech

PUAN.TECH will display its terminal identity, ask the user to choose an admin template, and install the selected frontend into the Laravel project.

Available templates planned for v1:

Acara — Ticketing Admin Dashboard
Qubis — Multipurpose Bootstrap Admin Template
Slim Clean — Clean & Modern Bootstrap Admin Dashboard

What PUAN.TECH installs

Depending on the selected template, PUAN.TECH will install:

frontend assets under public/puan/<template>/
Blade master layout
reusable Blade partials such as head, header, sidebar, footer, and scripts
a dashboard page
a simple frontend route in routes/web.php

Example Blade structure:

resources/views/puan/
├── template/
│   └── index.blade.php
├── layout/
│   ├── head.blade.php
│   ├── header.blade.php
│   ├── sidebar.blade.php
│   ├── footer.blade.php
│   └── script.blade.php
└── pages/
    └── dashboard/
        └── index.blade.php

Example master layout:

<!DOCTYPE html>
<html lang="en">
<head>
    @include('puan.layout.head')
</head>
<body>
    @include('puan.layout.sidebar')
    @include('puan.layout.header')

    <main>
        @yield('content')
    </main>

    @include('puan.layout.footer')
    @include('puan.layout.script')
</body>
</html>

Example dashboard page:

@extends('puan.template.index')

@section('title', 'Dashboard')

@section('content')
    <h1>Dashboard</h1>
@endsection

PUAN.TECH does not touch

PUAN.TECH does not create or modify:

app/Models
app/Http/Controllers
database/migrations
database/seeders
application database tables
application business logic

Development installation

During local plugin development, add PUAN.TECH as a Composer path repository from a separate Laravel test project.

Example folder layout:

C:/PUAN/
├── puan-tech/
└── puan-test/

Inside the Laravel test project:

composer config repositories.puan path ../puan-tech
composer require puan/tech:@dev

Composer may ask whether the plugin is trusted and should be enabled through allow-plugins. This is expected for Composer plugins.

Development workflow

Recommended order for v1:

Composer plugin foundation
PUAN.TECH binary terminal logo
interactive template selector
installer engine
Acara Blade conversion
Qubis Blade conversion
Slim Clean Blade conversion
public asset installer
route installer
reinstall / overwrite protection
fresh Laravel installation tests
GitHub public repository
Packagist publication
v1.0.0 release

Package structure

puan-tech/
├── composer.json
├── LICENSE
├── README.md
├── THIRD_PARTY_NOTICES.md
├── src/
│   ├── Composer/
│   ├── Console/
│   └── Installer/
└── templates/
    ├── acara/
    ├── qubis/
    └── slim/

Website

Official project website:

https://puan.tech

The website can later host documentation, screenshots, template previews, changelogs, and installation guides. Composer package distribution itself will use GitHub and Packagist.

Third-party templates

PUAN.TECH may redistribute template files and assets only under the applicable licenses and permissions obtained for those templates. These third-party files are not automatically relicensed under the MIT License of the PUAN.TECH source code.

See THIRD_PARTY_NOTICES.md and the corresponding license files for details.

License

Original PUAN.TECH source code is licensed under the MIT License.

Third-party templates and assets remain subject to their own licenses and/or redistribution permissions.

puan / tech

Maintainers

Package info

Statistics

Security