indigo-panel

As a Frontend Developer, I want to implement the Landing page based on the existing JSX design (Landing v2). This page serves as the entry point for Guests who view the platform demo and explore the interactive global map. It should feature dynamic animations with glowing connection lines between countries, hover interactions showing live stats, client highlights on dot click, and a side panel summary. Links to Login and Demo pages. Implement based on the existing Landing v2 design.

As a Frontend Developer, I want to implement the Login page based on the existing JSX design (Login v2). This page allows Admins and Clients to sign in to the platform. It should include form validation, error handling, and navigation to the Dashboard on success. Implement based on the existing Login v2 design.

As a Frontend Developer, I want to implement the Signup page based on the existing JSX design (Signup v2). This page allows Guests to request a trial account by submitting their details. It includes a multi-step or single-step form for collecting business information and links back to the Landing page. Implement based on the existing Signup v2 design.

As a Frontend Developer, I want to implement the Demo page based on the existing JSX design (Demo v2). This page is accessible to Guests and showcases the platform's key features interactively. It is reached from the Landing page and leads to the Signup page. Implement based on the existing Demo v2 design.

As a Backend Developer, I want to implement REST API endpoints for analytics data so that Admins and Clients can retrieve message usage statistics and reports. Endpoints: GET /analytics/overview, GET /analytics/messages, GET /analytics/clients/{id}, with filters for date ranges and aggregation.

As a Frontend Developer, I want to implement the Dashboard Overview page based on the existing JSX design (Dashboard v2). This is the main landing page post-login for both Admins and Clients. Admins see platform-wide stats and navigation to Clients and Analytics. Clients see their own message stats and navigation to Messages, Templates, Analytics, and Settings. Implement based on the existing Dashboard v2 design.

As an AI Engineer, I want to integrate GPT-based AI assistant functionality using Langchain so that users can interact with an intelligent assistant within the dashboard for query resolution, message drafting, and analytics insights. This powers the dashboard/ai-assistant page already present in the scaffold.

As a Frontend Developer, I want to implement the Clients page based on the existing JSX design (Clients v2). This page is accessible to Admins and allows them to view, create, and manage client accounts. It includes a list/table of clients, a create client form/modal, and links to individual client details. Implement based on the existing Clients v2 design.

As a Frontend Developer, I want to implement the Messages page based on the existing JSX design (Messages v2). This page allows Clients to send and receive WhatsApp messages through the panel. It includes a conversation list, message thread view, and a compose/send message interface. Accessible from the Client Dashboard. Implement based on the existing Messages v2 design.

As a Frontend Developer, I want to implement the Templates page based on the existing JSX design (Templates v2). This page allows Clients to create and manage message templates. It includes a list of existing templates, a create/edit template form, and template preview functionality. Accessible from the Client Dashboard. Implement based on the existing Templates v2 design.

As a Frontend Developer, I want to implement the Analytics page based on the existing JSX design (Analytics v2). This page serves both Admins (to monitor all client usage) and Clients (to view their own message reports). It includes charts, KPIs, and filters for date ranges. Accessible from both Admin and Client dashboards. Implement based on the existing Analytics v2 design.

As a Frontend Developer, I want to implement the Settings page based on the existing JSX design (Settings v2). This page serves both Admins (system-wide settings, API integrations) and Clients (manage API keys, account settings). Accessible from the Admin Analytics page and Client Analytics page. Implement based on the existing Settings v2 design.

As a Frontend Developer, I want to connect the Clients management page to the backend Clients API so that Admins can create, view, update, and delete client accounts via the UI with real data. Includes API service layer, loading states, error handling, and form submissions.

As a Frontend Developer, I want to connect the Messages page to the backend Messages API so that Clients can send and receive real WhatsApp messages via the UI. Includes real-time updates via polling or WebSocket, message state management, and error handling.

As a Frontend Developer, I want to connect the Templates page to the backend Templates API so that Clients can create and manage real message templates via the UI. Includes API service layer, template submission, approval status display, and error handling.

As a Frontend Developer, I want to connect the Analytics page to the backend Analytics API so that Admins and Clients can view real usage statistics and reports via charts and KPIs. Includes API service layer, chart data binding, and date filter integration.

As a Frontend Developer, I want to connect the Settings page to the backend Settings API so that Admins and Clients can manage their API keys and system configurations via the UI. Includes API service layer, form handling, and secure key masking.