qwebyr3243/jgg6uy

Purpose and Runtime

This is a Next.js TypeScript application combining a public business/product site, registration flow, document/contract interactions, and an administrator area. It uses the App Router: page components serve UI and route.ts handlers expose server APIs. Styling is global CSS/PostCSS; persistence is modeled through Drizzle.

Key entry points:

• src/app/layout.tsx — application shell and shared providers/layout.

• src/app/page.tsx — public landing page.

• src/app/admin/page.tsx — administrative UI.

• src/db/index.ts and src/db/schema.ts — database access and schema boundary.

Public Experience Composition

The landing experience is assembled from focused presentation components for marketing, company information, discovery, security, and contact/partner workflows.

• src/app/page.tsx

• src/components/Hero.tsx

• src/components/Features.tsx

• src/components/Contact.tsx

Supporting domain content is centralized separately from rendering:

• src/data/brands.tsx

• src/data/countries.ts

• src/data/modules.ts

Registration, Resume, and Contract Flows

Dedicated routes support candidate or user enrollment, resume handling, and contract signing. Contract data is also exposed through a server endpoint, making the API boundary distinct from the client interaction layer.

• src/app/register/page.tsx

• src/app/resume/page.tsx

• src/components/ContractSigner.tsx

• src/app/api/contracts/route.ts

• src/app/api/registrations/route.ts

API and Business Data Boundary

Route handlers provide the primary server-side integration surface for leads, messages, orders, registrations, contracts, and externally managed/open APIs. These handlers are the expected boundary for validation, persistence, and integration logic rather than client components accessing storage directly.

• src/app/api/leads/route.ts

• src/app/api/messages/route.ts

• src/app/api/orders/route.ts

• src/app/api/open-apis/route.ts

Administration and Access Control

Admin functionality is split between an admin page and protected server operations for login and administrative data retrieval. Authentication logic is isolated in a shared library, which should be the control point for credential/session policy used by admin APIs.

• src/app/admin/page.tsx

• src/app/api/admin/login/route.ts

• src/app/api/admin/data/route.ts

• src/lib/auth.ts

Data, Observability, and External Interfaces

Drizzle configuration and the database module define persistence infrastructure. A health endpoint supports deployment/runtime monitoring. The documentation page and API-manager component indicate a first-class external API/documentation surface; dashboard and search components suggest integrations or embedded analytics/search capabilities.

• drizzle.config.json

• src/db/index.ts

• src/app/api/health/route.ts

• src/app/docs/page.tsx

• src/components/OpenApiManager.tsx

• src/components/SupersetDashboard.tsx

Localization and Shared UI Infrastructure

Internationalization is provider-based, with supported languages and translations kept outside feature components. Shared navigation, footer, and global styles establish common UI behavior across public and workflow pages.

• src/i18n/I18nProvider.tsx

• src/i18n/languages.ts

• src/i18n/translations.ts

• src/components/Header.tsx

• src/app/globals.css