Laravel Astro Landing
A Laravel development package that scaffolds an Astro landing page in the same repository, runs it alongside the application, and generates independent deployment workflows.
Laravel PHP Astro TypeScript Composer GitHub Actions
Laravel Astro Landing keeps a product’s marketing site close to its application without coupling their production environments. The Astro landing lives in the Laravel repository, so both can share pull requests and changes, while the static site deploys independently from the PHP application.
I built the package to make that setup repeatable: scaffold the landing, run it beside the application, and generate its deployment workflow from Artisan.
One repository, independent builds
The package installs as a development dependency. The landing has its own package manifest, lockfile, and build output; the Laravel application keeps its existing runtime and deployment. Nothing in the package needs to run on the production application server.
composer require lauroguedes/laravel-astro-landing --dev
php artisan landing:installThe interactive installer can start from Astro’s minimal template, an official example, a template repository, or a free theme from the Astro catalog. It asks about the directory, package manager, deployment target, and public URL. Existing files are protected unless an overwrite is explicitly requested.
A shared local workflow
On Laravel 13.16 and later, the landing can join composer run dev as another development process. Standalone landing:dev and landing:build commands also support earlier Laravel applications. Missing landing dependencies are installed before these commands run.
The installer adds landing build artifacts to the application’s ignore rules and excludes its files from Tailwind v4’s application scan, keeping the two stylesheets separate.
Deployment that follows the landing
landing:workflow generates GitHub Actions workflows for Cloudflare Pages, Netlify, Vercel, GitHub Pages, or an SSH server. Path filters keep application-only changes from redeploying the marketing site.
php artisan landing:workflow cloudflare-pagesThe workflow uses the configured public landing URL during the Astro build, aligning canonical URLs, social metadata, and sitemap entries with the deployment. Placeholder production URLs are rejected before publishing.
Clear routes and agent guidance
The recommended setup serves the landing on the main domain and the application on a subdomain. An optional root redirect uses plain Laravel configuration, so it continues working when development dependencies are absent in production. The documentation also covers serving the landing under a path.
The package includes Laravel Boost guidelines and a development skill to help AI agents understand the directory boundaries, commands, and deployment model before making changes.