PHPackages nickdekruijk/leap-template - 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. [Templating & Views](/categories/templating) 4. / 5. nickdekruijk/leap-template ActiveLibrary[Templating & Views](/categories/templating) nickdekruijk/leap-template ========================== Frontend website template scaffolding for nickdekruijk/leap: the leap:template and leap:content commands. Install with composer require --dev. 2.4.0(2w ago)193↓71.1%MITPHPPHP ^8.3CI passing Since Jul 15Pushed 2w ago1 watchersCompare [ Source](https://github.com/nickdekruijk/leap-template)[ Packagist](https://packagist.org/packages/nickdekruijk/leap-template)[ RSS](/packages/nickdekruijk-leap-template/feed)WikiDiscussions master Synced 1w ago READMEChangelog (10)Dependencies (10)Versions (36)Used By (0) Leap Template ============= [](#leap-template) Frontend website template scaffolding for [`nickdekruijk/leap`](https://github.com/nickdekruijk/leap): the `leap:template` and `leap:content` commands, plus the stubs they copy into your project. It is **dev-only tooling** — install it with `--dev` so it (and its commands) are absent from production entirely. Installation ------------ [](#installation) Leap itself is a **runtime** dependency (the admin panel runs in production); only the scaffolding is dev-only. So install **two** packages, like Laravel's own framework + Pint: ``` composer require nickdekruijk/leap # admin panel — production (non-dev) composer require --dev nickdekruijk/leap-template # scaffolding — dev only ``` > **Why `nickdekruijk/leap` must be a normal (non-dev) require:** this package depends on leap, but if you only `require --dev leap-template`, leap comes in as a *dev-transitive*dependency and `composer install --no-dev` on production removes it — taking the admin panel with it. leap has to be a direct non-dev requirement of your app. On production (`composer install --no-dev`) `leap-template` is not installed, so `leap:template`/`leap:content` don't exist there — zero footprint. Live demo --------- [](#live-demo) [leap.nickdekruijk.nl](https://leap.nickdekruijk.nl) is a stock `leap:template` install — that site is what these stubs produce. Log in on [/admin](https://leap.nickdekruijk.nl/admin) with `info@example.com` / `leapdemo` and change anything; the site resets to its seeded state 15 minutes after the last change. Commands -------- [](#commands) ``` php artisan leap:template # scaffold the frontend website (interactive) php artisan leap:template --fresh # complete, unattended install (implies --force) php artisan leap:content News # generate a listed content type ``` Both refuse to run on `APP_ENV=production` without `--force` (like Laravel's `migrate`). Documentation ------------- [](#documentation) The template and content types are documented in the leap repo: - [Frontend template](https://github.com/nickdekruijk/leap/blob/master/docs/template.md) - [Content types (news/events/…)](https://github.com/nickdekruijk/leap/blob/master/docs/content-types.md) Versioning ---------- [](#versioning) Tracks leap's major line — this package requires `nickdekruijk/leap: ^1.0`, so only a breaking leap release (2.0) is paired with a new `leap-template` major. The two packages are released in lockstep at the same version number, but within the major you can update either on its own. Pushing a tag publishes a GitHub release automatically, with that version's [CHANGELOG.md](CHANGELOG.md) section as its notes — so the changelog stays the only place a release is written. A tag whose version has no changelog section fails the workflow rather than publishing an empty release. License ------- [](#license) MIT. ### Health Score 48 — FairBetter than 94% of packages Maintenance97 Actively maintained with recent releases Popularity15 Limited adoption so far Community7 Small or concentrated contributor base Maturity60 Established project with proven stability Bus Factor1 Top contributor holds 100% of commits — single point of failure 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. ### Release Activity Cadence Every ~1 days Total 35 Last Release 16d ago Major Versions 0.10.18 → 1.0.02026-07-23 1.1.1 → 2.0.02026-08-10 ### Community Maintainers ![](https://www.gravatar.com/avatar/0b01fc7c2c39bbe8f87b4afa70ffe1cf2bb787310e1d22fcfed6ae527d4573bb?d=identicon)[nickdekruijk](/maintainers/nickdekruijk) --- Top Contributors [![nickdekruijk](https://avatars.githubusercontent.com/u/607302?v=4)](https://github.com/nickdekruijk "nickdekruijk (97 commits)") --- Tags laraveldevscaffoldingtemplateleap ### Code Quality TestsPHPUnit Code StyleLaravel Pint ### Embed Badge ![Health badge](/badges/nickdekruijk-leap-template/health.svg) ``` [![Health](https://phpackages.com/badges/nickdekruijk-leap-template/health.svg)](https://phpackages.com/packages/nickdekruijk-leap-template) ``` ### Alternatives [laravel/octane Supercharge your Laravel application's performance. 4.0k30.7M279](/packages/laravel-octane)[statamic/cms The Statamic CMS Core Package 4.9k3.9M1.2k](/packages/statamic-cms)[ecotone/laravel Ecotone for Laravel — CQRS, Event Sourcing, Sagas, Durable Workflows, and Outbox on top of Laravel Queue, via PHP attributes. 21336.4k4](/packages/ecotone-laravel)[api-platform/laravel API Platform support for Laravel 58190.1k22](/packages/api-platform-laravel) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)