Repository navigation
v0.3.0
The template is now built on tey/kit, and a fresh clone reaches a designed sign-in with one command.
Changed
- The template is built on tey/kit 0.1 with every feature added.
app/Starter,routes/starterandresources/js/startergive way to the kit library and to the migrations and pages thatkit:addwrites. CI checks these againstkit:addon a clean Laravel app.tey/starter-blueprintandstarter:maintainare removed in favour ofkit:addandkit:update. Databases migrated by 0.2 keep their schema and data (#30, #15) composer setuptakes a fresh clone to a working local sign-in.starter:first-ownercreates the first local owner, locally only and with no default password (#30)- The sign-in page and app shell are designed. They are built from Laravel's MIT Vue starter kit, use Tailwind CSS 4 and Instrument fonts, and the nav lists your workspaces (#30, #36)
- New apps start conformant:
- The suites also run on PostgreSQL in CI, and a Pest browser test signs in on a fresh clone over HTTPS (#30)
Security
- Trusted hosts are pinned to
APP_URL, so a forged forwarded host can't reach reset or invite links (#35)
Known gaps
- The template runs Mod 0.9 until tey/kit moves to Mod 0.10.
- Password reset and owner set-password links need mail (#24).
What's Changed
- Untangle shared seams into per-feature registrations by @jaspertey in #27
- Move starter code into feature namespaces by @jaspertey in #28
- Build the roadmap on tey/kit by @jaspertey in #29
- Build the template on tey/kit by @jaspertey in #33
- Fix the post-merge audit findings for the template by @jaspertey in #37
- Validate the MCP capability declaration against the vendored schema by @jaspertey in #39
- Fix the remaining MCP capability declaration findings by @jaspertey in #41
- Inventory the kit controllers the MCP declaration references by @jaspertey in #43
- Set the starter's fonts by @jaspertey in #44
Full Changelog: v0.2.1...v0.3.0