Front-End Developer (Contract) — Tailwind CSS Migration for a Luxury Villa Rental Platform

We run a high-traffic, performance-sensitive Laravel + Blade marketing and booking site for luxury villa rentals. Its CSS has grown into three layers — Bootstrap, ~40 bespoke CSS files, and a large hand-written utility stylesheet that imitates Tailwind — with no real Tailwind build in place. We want to consolidate this into a genuine, compiled Tailwind v4 setup, without redesigning the site. What you'll do Stand up a real Tailwind v4 build inside our existing Laravel toolchain, preserving our current critical-CSS / above-fold / deferred CSS loading strategy. Convert Bootstrap grid + utility classes and our hand-rolled utility CSS to compiled Tailwind across the Blade templates. Migrate bespoke component CSS to Tailwind, keeping the rendered result visually equivalent. Work in phases, starting with a single proof-of-concept page, and verify each phase with before/after screenshots at our breakpoints plus our existing Cypress suite. Out of scope JavaScript refactoring (jQuery / Bootstrap JS / AlpineJS) is a separate engagement. You will leave JS-coupled component styling (modals, off-canvas, sliders) untouched for now. Required Strong Tailwind CSS (ideally v4) and modern CSS expertise. Comfortable in Laravel Blade templates — you'll edit markup classes, not PHP logic. Experience migrating Bootstrap → Tailwind and reasoning about CSS specificity / !important. Performance-aware: understands critical CSS, render-blocking vs. deferred styles, and how a Tailwind build affects bundle size. Disciplined, incremental, fidelity-focused; able to prove "looks the same" with screenshots and a passing e2e suite. Nice to have Laravel Mix and/or Vite build-config experience. Cypress. jQuery / AlpineJS familiarity (for later phases). Engagement Phased contract. Phase 0 is a paid pilot (build setup + one page end-to-end) acting as a go/no-go before the full rollout. To apply: share Bootstrap→Tailwind work you've done, and briefly describe how you'd wire a real Tailwind build into an existing Laravel Mix pipeline without losing a critical-CSS loading strategy.