You know Laravel. Now learn to work with it.

How a Laravel project is put together from the inside.

You learn the architecture of the project rather than writing code wherever it happens to fit, and follow a request the whole way: browser, route, controller, model, database, and back.

You build a complete module inside Laravel, not a set of disconnected examples.

Working with a database properly.

We work on a real database and learn to design one a project can grow into, handling data through Eloquent rather than writing SQL for every operation.

You can design a database structure for a real project and relate the models to each other.

From a plain form to a real feature.

Handling user input properly and safely, and moving validation out of the controller into form request classes so the project stays organised.

A complete CRUD module: create, read, update, delete, search, pagination, validation and file upload.

Not every user should see everything.

Building a user and permission system close to what real projects use, and understanding the difference between who you are and what you are allowed to do.

A real authentication and authorization system, not a simple login.

First thing: requirement analysis.

Nobody says "build an e-commerce site" — we start from requirements, the way any client project starts, and then design the database.

The e-commerce foundation is ready for the customer features.

Building the customer experience.

The part the customer sees: from browsing products through to a completed order — cart, address, order, payment, confirmation.

A complete customer side you can actually use.

Building a real admin panel.

The side that runs the shop: orders and stock through to coupons, permissions and reports.

Admin dashboard plus customer site — the core of a working shop.

Connecting the project to the outside world.

We move past the idea of a plain Laravel website and build APIs, so a frontend or a mobile app can consume the project.

An e-commerce project with a website, an admin dashboard, REST APIs, notifications and email.

A second project with a different kind of business logic.

We build a CMS from nothing — and before any code, work out who the users are, who administers it, and who may publish, edit and delete.

A working CMS foundation with basic content management.

Turning the CMS into a complete system.

A real users and roles system, a content editor, and management for SEO, forms, the newsletter and the site settings.

A complete CMS with an admin dashboard, roles, SEO and content management.

The project has to be deliverable.

We stop adding features and look at quality — is the code organised, is anything duplicated, are the names clear, are there security problems?

The project becomes production-ready on the fundamentals, not just a demo.

From development to production.

The last week mirrors handing a project to a client: from the git workflow through deploying to a real server and presenting the work.

Two deployed projects, a ready portfolio, and a presentation you can give in an interview.