I am wanting to turn my Vehica-based theme (tangiblewp.com/vehica) WordPress site into a true headless setup, with the public-facing experience driven entirely by a Next.js application (next-wp.com by 98d). To complete the transition I need the two environments tightly integrated so that: • User authentication flows run through WordPress but feel native inside the Next.js app (registration, login, password reset, role-based access). • The same database powers both layers—when a vehicle, blog post, page, or user profile is added or updated in WordPress it must appear instantly (or near-real-time) in the Next.js frontend. • UI and UX remain consistent; colours, fonts, listing cards and search filters from Vehica need to be mirrored in the React components so visitors never notice they have left WordPress. Vehica will continue to manage inventory logic and admin screens, while the Next.js codebase (TypeScript, Next 14, React Server Components welcome) will be the primary interface users see. Acceptance criteria 1. Secure JWT- or cookie-based auth working end-to-end. 2. Vehicle listings, user profiles, blog posts and pages sync automatically via REST or GraphQL without manual refresh. 3. Styled components / Tailwind (your choice) reproduce the Vehica look pixel-close across breakpoints. 4. Clear setup docs so I can reproduce the build on another server. If you have shipped a headless WordPress project before—especially one involving custom post types like Vehica’s cars—let’s talk.