### Running the Development Server Source: https://github.com/rhitune2/ticketfast-mail/blob/main/README.md Commands to start the development server for the Next.js project using different package managers. Assumes Node.js is installed. ```bash npm run dev # or yarn dev # or pnpm dev # or bun dev ``` -------------------------------- ### Next.js Page Component Example Source: https://github.com/rhitune2/ticketfast-mail/blob/main/README.md An example of a Next.js page component, likely written in TypeScript, demonstrating the basic structure and auto-updating feature. ```typescript // app/page.tsx // This file can be modified to edit the page content. // The page auto-updates as you edit the file. ``` -------------------------------- ### TicketFast Development Guidelines - Performance Source: https://github.com/rhitune2/ticketfast-mail/blob/main/docs/project-docs.md Outlines performance considerations for TicketFast development, including optimizing SSR/SSG, implementing loading states, error handling, and Web Vitals optimization. ```APIDOC Performance Considerations: - Optimize Server-Side Rendering (SSR) and Static Site Generation (SSG). - Implement loading states with loading.tsx. - Proper error handling with error.tsx. - Optimize Web Vitals (LCP, CLS, FID). ``` -------------------------------- ### TicketFast Development Guidelines - Code Organization Source: https://github.com/rhitune2/ticketfast-mail/blob/main/docs/project-docs.md Provides guidelines for code organization in TicketFast, emphasizing the use of server components for data fetching, client components for interactivity, TypeScript, and Tailwind CSS. ```APIDOC Code Organization Guidelines: - Server components for data fetching and SEO. - Client components only for interactive elements. - TypeScript for all new code with proper interfaces. - Tailwind CSS for styling following utility-first approach. - Proper error handling and input validation. - Responsive design using mobile-first approach. ``` -------------------------------- ### TicketFast Ticket Management Workflow Source: https://github.com/rhitune2/ticketfast-mail/blob/main/docs/project-docs.md Explains the step-by-step process for managing support tickets within TicketFast, from email conversion to response generation and status tracking. ```APIDOC Ticket Management Workflow: 1. Incoming emails are converted to tickets and appear in the inbox. 2. Tickets can be assigned to team members or left unassigned. 3. Tickets have status (ASSIGNED, UNASSIGNED, WAITING, CLOSED). 4. Tickets have priority levels (LOW, NORMAL, MEDIUM, HIGH). 5. Team members can respond to tickets with optional AI assistance. ``` -------------------------------- ### TicketFast Subscription Plans Source: https://github.com/rhitune2/ticketfast-mail/blob/main/docs/project-docs.md Details the different subscription tiers available for TicketFast: Free, Pro, and Enterprise, outlining the limits for tickets, customers, organizations, and team members. ```APIDOC Subscription Plans: | Feature | Free | Pro | Enterprise | |---|---|---|---| | Tickets | 100 | 500 | 2,000 | | Customers | 10 | 50 | 200 | | Organizations | 1 | 3 | 10 | | Team Members | 3 | 10 | 50 | ``` -------------------------------- ### TicketFast API Endpoints Overview Source: https://github.com/rhitune2/ticketfast-mail/blob/main/docs/project-docs.md Provides a high-level overview of the RESTful API endpoints available in TicketFast for managing tickets, users, organizations, and subscriptions. ```APIDOC API Endpoints: The application provides RESTful API endpoints for: - Ticket management - User management - Organization settings - Subscription handling ``` -------------------------------- ### TicketFast Application Structure Source: https://github.com/rhitune2/ticketfast-mail/blob/main/docs/project-docs.md Describes the directory structure of the TicketFast application using Next.js App Router with route groups for authentication, landing pages, and core application functionality. ```Next.js - (auth): Authentication-related routes - (landing): Public landing pages - (main): Core application functionality ``` -------------------------------- ### TicketFast Development Guidelines - Auth Source: https://github.com/rhitune2/ticketfast-mail/blob/main/docs/project-docs.md Specifies guidelines for authentication and authorization in TicketFast, adhering to Better Auth patterns, role-based access control, and middleware for route protection. ```APIDOC Authentication & Authorization Guidelines: - Follow Better Auth patterns for authentication flows. - Implement proper role-based access controls. - Use middleware for route protection and redirects. ``` -------------------------------- ### TicketFast Subscription Management Workflow Source: https://github.com/rhitune2/ticketfast-mail/blob/main/docs/project-docs.md Describes the process for managing subscription plans and payments within TicketFast, including owner selection, limit enforcement, and payment processing via Polar. ```APIDOC Subscription Management Workflow: 1. Workspace owners can select subscription plans. 2. Subscription limits apply to tickets, customers, and team members. 3. Payment processing is handled through Polar. ``` -------------------------------- ### TicketFast User Management Workflow Source: https://github.com/rhitune2/ticketfast-mail/blob/main/docs/project-docs.md Details the user and team management processes in TicketFast, including inviting members, assigning roles, and managing multi-organization access. ```APIDOC User Management Workflow: 1. Organization owners can invite team members. 2. Members can have different roles and permissions. 3. Users can belong to multiple organizations. ``` -------------------------------- ### TicketFast Data Model Entities Source: https://github.com/rhitune2/ticketfast-mail/blob/main/docs/project-docs.md Outlines the key entities in the TicketFast relational database schema, including Users, Organizations, Tickets, Contacts, and more, managed with Drizzle ORM. ```PostgreSQL - Users: Application users with roles and permissions - Organizations: Teams or companies using the platform - Members: Users belonging to organizations with specific roles - Tickets: Support tickets with metadata, priority, and status - Contacts: Customer profiles linked to tickets - Ticket Messages: Communication thread for each ticket - Inboxes: Email inboxes for ticket collection - Subscriptions: Payment plans and usage quotas ``` === COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.