Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Codefied-CodePix/KaroCar-platform/llms.txt

Use this file to discover all available pages before exploring further.

The corporate app is the enterprise-grade portal for business accounts and fleet operators on the KaroCar Platform. It provides organisations with the tools to manage multi-user accounts, oversee fleet bookings, access consolidated reporting, and configure company-wide preferences for KaroCar services. The homepage (app/page.tsx) renders a Vendor Dashboard heading — the corporate portal intentionally reuses the vendor-style layout as a structural foundation for its enterprise management views.
The corporate app’s page.tsx currently renders a “Vendor Dashboard” heading. This is intentional — the corporate portal reuses the same vendor-style layout pattern as a starting scaffold for its enterprise management interface. The heading and copy are expected to be updated as corporate-specific features are built out on top of this foundation.

​
Tech Stack

Next.js 16.2.7

App Router with server components for enterprise-scale data rendering and nested route organisation.

React 19.2.4

Latest stable React for interactive, data-rich corporate management dashboards.

Tailwind CSS v4

Utility-first CSS with the v4 PostCSS engine, ensuring consistent styling with the broader platform.

TypeScript 5

Strict typing across fleet models, organisation structures, and API integrations.

​
Directory Structure

apps/corporate/
├── app/
│   ├── layout.tsx    # Root layout with Geist font
│   ├── page.tsx      # Corporate portal homepage (vendor-style layout)
│   └── globals.css   # Global styles
├── public/           # Static assets
├── package.json
├── next.config.ts
└── tsconfig.json
Additional routes for fleet management, billing, user administration, and organisation settings are expected to be added under app/ following Next.js App Router conventions.

​
Package Configuration

The corporate app does not depend on any internal workspace UI packages. Its component set is built locally within the app, keeping it independently deployable. 
{
  "name": "corporate",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start",
    "lint": "eslint"
  },
  "dependencies": {
    "next": "16.2.7",
    "react": "19.2.4",
    "react-dom": "19.2.4"
  },
  "devDependencies": {
    "@tailwindcss/postcss": "^4",
    "@types/node": "^20",
    "@types/react": "^19",
    "@types/react-dom": "^19",
    "eslint": "^9",
    "eslint-config-next": "16.2.7",
    "tailwindcss": "^4",
    "typescript": "^5"
  }
}

​
Development Commands

turbo dev --filter=corporate
Use turbo dev --filter=corporate to run only the corporate portal. Because this app has no upstream workspace package dependencies, it starts up immediately — ideal when building out enterprise features or refining the organisation management UX in isolation.
Next.js starts on port 3000 by default. When multiple apps in the monorepo are running simultaneously, each is assigned the next available port. Check your terminal output for the exact URL.

​
Building & Starting

turbo build --filter=corporate && turbo start --filter=corporate
1

Install dependencies

Run pnpm install from the monorepo root. All workspace packages and local node_modules will be linked automatically.
2

Build the corporate app

Run turbo build --filter=corporate. Turborepo caches the build output so subsequent runs only recompile changed modules.
3

Start the production server

Run turbo start --filter=corporate and open the printed URL to verify the corporate portal renders correctly.

​
Linting

pnpm --filter corporate lint

​
Customising the Layout

The corporate portal currently inherits the vendor-style page scaffold. To differentiate it:
Edit apps/corporate/app/page.tsx and replace the <h1> content:
<h1 className="...">
  Corporate Portal
</h1>
Update the accompanying paragraph to reflect enterprise-specific messaging for fleet operators and business account managers.
Create new route segments under apps/corporate/app/ following App Router conventions:
apps/corporate/app/
├── fleet/
│   └── page.tsx      # Fleet management
├── billing/
│   └── page.tsx      # Corporate billing
└── users/
    └── page.tsx      # Organisation user management

Vendor App

The vendor dashboard whose layout pattern the corporate portal is based on.

Auth App

The centralised authentication service for corporate user sign-in.

Admin App

Internal operator dashboard for platform-wide management.

Local Setup

Step-by-step guide to running the full platform stack locally.

Build docs developers (and LLMs) love

Get started for freeTalk to us