Front

Installation

composer require webisters/front

Sass partials

The sass/ directory contains the design tokens (colors, spacing, typography) plus reusable component partials: buttons, forms, cards, navigation, tables, alerts. Pull them into your project's main stylesheet:

// app.scss
@use 'webisters/front/sass/tokens';
@use 'webisters/front/sass/buttons';
@use 'webisters/front/sass/forms';
@use 'webisters/front/sass/cards';

Override any token by re-declaring it before the @use import.

Compiling styles

Front includes a small PHP-driven Sass compiler at sass-compiler.php so you don't need a Node toolchain just for CSS. Invoke it directly from Composer:

php vendor/webisters/front/sass-compiler.php \
    --input=resources/app.scss \
    --output=public/css/app.css

Or wire it into your composer.json scripts:

{
    "scripts": {
        "build:css": "php vendor/webisters/front/sass-compiler.php --input=resources/app.scss --output=public/css/app.css"
    }
}

Shared views

The views/ directory ships partials for things every project re-creates: layouts, flash messages, pagination, form fields. The views-builder.php helper copies them into your project's view directory so you can edit freely:

php vendor/webisters/front/views-builder.php --to=resources/views

Conclusion

Front is opinionated, lightweight, and easy to override. Use it as a starting point, not a constraint — bring in only the partials you want and replace anything that doesn't fit your design.