# ResortFlow > ResortFlow is a comprehensive resort growth platform combining software, marketing services, and team support. Built with Next.js and Strapi CMS, it serves ambitious resorts across Europe with multilingual websites, channel management, guest communication, and done-for-you marketing. ## What We Offer - **Software Platform**: Modern websites with integrated booking - **Team Support**: Dedicated teams, not just tools - **Done-For-You Marketing**: Content creation and campaign management - **Guest Communication**: Automated messaging and support - **Channel Management**: Integration with Airbnb, Booking.com, and major OTAs - **Unified Platform**: Everything connected in one place ## Core Features - Multilingual support (i18n) with locale-aware routing - Section-based page builder with 14+ component types - Live booking integration with channel managers - Guest communication automation - Social media management (Instagram, Facebook, TikTok, LinkedIn) - Lead management with Pipedrive CRM - Email marketing with Mailchimp - JSON-LD structured data with Schema.org vocabulary for SEO and LLM understanding ## Tech Stack - **Frontend**: Next.js 14 (App Router), TypeScript, Tailwind CSS - **Backend**: Strapi CMS with MySQL - **UI Components**: shadcn/ui, Radix UI primitives - **Deployment**: Docker, Kubernetes - **APIs**: Mailchimp, Pipedrive integration ## Architecture Monorepo structure with Next.js frontend and Strapi CMS backend: - **Frontend** (`/nextjs/`): Server-rendered React with App Router - **Backend** (`/strapi/`): Headless CMS with content types and components - **Section-based**: Reusable page sections managed through Strapi - **i18n**: Multilingual content with locale routing ## Documentation - [Development Guide](/docs/development-guide.md): How to add sections, fetch data, handle forms - [Components Reference](/docs/components.md): All available section and UI components - [Setup Guide](/docs/setup.md): Local development and deployment instructions - [JSON-LD Guide](/docs/json-ld.md): Structured data implementation with Schema.org ## Development Principles - **Layout**: Use flexbox with gap (not margins) - **Media**: Images non-localized, alt text localized per language - **TypeScript**: Strict typing, never use `any` - **Components**: Server components for data, client for interactivity - **Styling**: Tailwind CSS, mobile-first, rem units ## Optional - [Strapi Documentation](https://docs.strapi.io/): Headless CMS documentation - [Next.js App Router](https://nextjs.org/docs/app): Server Components and routing - [shadcn/ui](https://ui.shadcn.com/): Accessible component library - [Tailwind CSS](https://tailwindcss.com/docs): Utility-first CSS framework