Doo Scramble

Overview Most Laravel starters focus on full-stack experiences, bundling Blade or Vite. However, modern backends often serve as headless engines for mobile apps or SPAs. The Laravel API Starter Kit by Jean Mark fills this void. It provides a lean, opinionated foundation that strips away the frontend fluff, focusing entirely on robust API architecture, versioning, and automated documentation. Prerequisites To effectively use this kit, you should be comfortable with: * **PHP 8.2+** and Laravel fundamentals. * **RESTful Principles**: Understanding HTTP methods and status codes. * **Composer**: Managing PHP dependencies. * **Docker or Local Servers**: Familiarity with Laravel Herd or Sail for environment hosting. Key Libraries & Tools * Laravel 12: The underlying framework providing the core engine. * Doo Scramble: An automated Open API 3.1 documentation generator. * Laravel API Route: A package for managing multi-strategy versioning (URL, Header, etc.). * Spatie Query Builder: Simplifies filtering, sorting, and including relations via URL parameters. * Laravel Sanctum: Handles lightweight API token authentication. Code Walkthrough 1. Installation and Setup Clone the repository and run the standard Laravel initialization commands. This kit skips the traditional `npm install` because it contains no frontend assets. ```bash git clone https://github.com/Grazulex/laravel-api-kit api cd api composer install php artisan key:generate php artisan migrate ``` 2. Versioning and Routes Routes are not defined in the standard `api.php`. Instead, they reside in version-specific files, managed by the Laravel API Route package. Configuration happens in `config/api-route.php`. ```php // routes/api/v1.php Route::post('/login', [AuthController::class, 'login'])->name('login'); ``` 3. The API Controller Pattern The kit uses an abstract `APIController` that utilizes an `ApiResponse` trait. This ensures consistent JSON structures across your entire application. ```php // app/Http/Controllers/Api/AuthController.php public function register(RegisterRequest $request) { // Logic here... return $this->created($user_resource); } ``` Syntax Notes The kit utilizes **Traits** to inject standardized response methods like `success()`, `created()`, and `unauthorized()` into controllers. This promotes DRY (Don't Repeat Yourself) principles. It also leverages **Eloquent API Resources** to transform model data before it leaves the server, ensuring the internal database schema isn't leaked directly to the client. Practical Examples This starter is ideal for building **Mobile App Backends** where you need quick iteration on endpoints without managing a frontend. It is also perfect for **Microservices** that require standardized documentation through Doo Scramble, allowing other teams to integrate with your service by simply visiting the `/docs` endpoint. Tips & Gotchas * **Abstract vs. Trait**: While the kit uses an abstract base controller, you can apply the `ApiResponse` trait directly to specific classes if you prefer composition over inheritance. * **Unused Packages**: Spatie packages like `laravel-data` are included in `composer.json` but aren't strictly required. They serve as architectural suggestions for handling DTOs.