# DocQube Landing Page

DocQube is an all-in-one document management and AI platform that unites four core products:
- **Drive**: Document management + AI
- **PDF Editor**: True-reflow editing
- **Workflows**: Route, approve, sign
- **Sign**: Verified e-signatures

This repository contains the Next.js marketing landing page built to showcase DocQube's solutions for various audiences including Enterprise, Legal, Real Estate, and Operations.

---

This is a [Next.js](https://nextjs.org) project bootstrapped with [`create-next-app`](https://nextjs.org/docs/app/api-reference/cli/create-next-app).

## Getting Started

First, run the development server:

```bash
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
```

Open [http://localhost:3000](http://localhost:3000) with your browser to see the result.

You can start editing the page by modifying `app/page.tsx`. The page auto-updates as you edit the file.

This project uses [`next/font`](https://nextjs.org/docs/app/building-your-application/optimizing/fonts) to automatically optimize and load [Geist](https://vercel.com/font), a new font family for Vercel.

## Learn More

To learn more about Next.js, take a look at the following resources:

- [Next.js Documentation](https://nextjs.org/docs) - learn about Next.js features and API.
- [Learn Next.js](https://nextjs.org/learn) - an interactive Next.js tutorial.

You can check out [the Next.js GitHub repository](https://github.com/vercel/next.js) - your feedback and contributions are welcome!

## Deploy on Vercel

The easiest way to deploy your Next.js app is to use the [Vercel Platform](https://vercel.com/new?utm_medium=default-template&filter=next.js&utm_source=create-next-app&utm_campaign=create-next-app-readme) from the creators of Next.js.

Check out our [Next.js deployment documentation](https://nextjs.org/docs/app/building-your-application/deploying) for more details.

## Environment & Build Scripts

This project is configured with multiple environments for seamless deployments and testing.

### Environment Variables
- `.env`: Used by `npm run local` and points to `http://localhost:5173/login`.
- `.env.test`: Used by `npm run test` and `npm run build:test`; points to `https://docqubeapp-test.maskantech.in/login`.
- `.env.production`: Used by `npm run build:production` and `npm run prod`; points to `https://app.docqube.com/login`.

**Note:** Environment files (`.env*`) are ignored in Git to keep variables secure. Make sure you create them locally if you clone this repository.

### Build Scripts
- `npm run local`: Starts the local development server using `.env`.
- `npm run test`: Starts the development server using `.env.test`.
- `npm run build:local`: Builds the application using `.env`.
- `npm run build:test`: Builds the application using `.env.test`.
- `npm run build:production`: Builds the application using `.env.production`.
- `npm run prod`: Starts the production server using `.env.production`.

### Production Deployment Artifact

The Next.js configuration uses standalone output. Build the production artifact with:

```bash
npm ci
npm run build:production
```

The deployment must include:


Prepare the standalone artifact after building:

```bash
cp -r public .next/standalone/
cp -r .next/static .next/standalone/.next/
```

On Windows PowerShell, use this equivalent sequence because `cp` does not merge existing directories:

```powershell
Remove-Item -Recurse -Force .next\standalone\public -ErrorAction SilentlyContinue
Remove-Item -Recurse -Force .next\standalone\.next\static -ErrorAction SilentlyContinue
Copy-Item public .next\standalone\public -Recurse
Copy-Item .next\static .next\standalone\.next\static -Recurse
```

Start the standalone server with:

```bash
node .next/standalone/server.js
```

On Windows PowerShell:

```powershell
$env:PORT = "3000"
$env:HOSTNAME = "127.0.0.1"
node .next\standalone\server.js
```

For Nginx deployment, run the server on an internal port and reverse proxy to it:

```bash
PORT=3000 HOSTNAME=127.0.0.1 node .next/standalone/server.js
```