Get started4 min read

Ship in your first week

This guide sums up how we build at Lantorian: a tested Laravel 13 API and a bilingual Next.js 16 front end. Read a page, apply it in your project, move on.

Next.js renders pages on the server, picks the language (proxy.ts), validates forms with Zod and calls the API.↔ Laravel API in JSON, Sanctum auth

Click a zone to see its role. The dotted lines trace a request.

Your first week

One goal per day. By Friday you open your first pull request on your own.

1
Monday: machine, Git and conventions
Install the tools, clone the projects, run composer test and npm run dev. Learn our branch and commit naming.
2
Tuesday: Laravel architecture
Follow a request end to end: route, FormRequest, thin controller, Action, Resource.
3
Wednesday: Pest tests
Write a Feature test and a Unit test for an existing Action. Run coverage.
4
Thursday: Next.js front end
Structure, FR/EN JSON translations, skeletons, forms validated with Zod.
5
Friday: first PR
Pick a ticket labelled good-first-issue, run through the checklist, request a review.

Non-negotiable rules

Remember these and your code reviews will pass the first time.

No hard-coded UI text: everything goes through messages/fr and messages/en.
Every input is validated twice: Zod in Next.js, FormRequest in Laravel.
Controllers hold no business logic: they delegate to an Action.
No feature without a Pest test, no bug fix without a test that reproduces it.
Every loading state has a skeleton shaped like the final content.
Strict TypeScript, no any, no @ts-ignore without a comment.
No secrets in code or in a NEXT_PUBLIC_ variable.
Small PRs (under 400 lines), green CI before asking for review.

Reference versions

New projects start from the target column. Last updated: September 2026.

Tool	Target	Minimum supported
PHP	`8.4`	8.3
Laravel	`13.x`	13.0
Pest	`4.x`	4.0
Node.js	`24 LTS`	20.9
Next.js	`16.3`	16.0
React	`19.2+`	19.2
TypeScript	`5.9`	5.1
Tailwind CSS	`4.x`	4.0
next-intl	`4.x`	4.0
Zod	`4.x`	4.0

How to read this guide

Every page follows the same order: a diagram to understand, the rule, then code to copy. The Avoid / Do blocks show the mistakes we see most often in review.