# Use and adapt whatsappservicesui

Use the documented interfaces and source layout for **whatsappservicesui**. The sections below retain the README’s examples and configuration details.

## What Was Kept

- Existing dashboard pages, layouts, components, Arabic/English UI structure, and styling.
- Local mock data and mock actions under `src/mock/` so screens can render without a backend.
- Frontend-only auth/session behavior for previewing the UI.

## What Was Removed

- Backend function files and deployment config.
- Backend CLI scripts and backend runtime dependencies.
- Live backend client initialization.

## Structure

- `src/app/` - Next.js routes.
- `src/components/` - Shared UI components.
- `src/contexts/` - Frontend state providers.
- `src/mock/` - Local data/actions used by the copied UI.
- `src/hooks/` and `src/lib/` - UI helpers preserved from the copied app.

## Commands in the root manifest

The captured [package.json](https://github.com/Up-to-code/whatsappservicesui/blob/HEAD/package.json) declares the following scripts. Run them from the directory containing that manifest.

| Command | Script |
| --- | --- |
| `npm run dev` | `next dev` |
| `npm run build` | `next build` |
| `npm run start` | `next start` |
| `npm run lint` | `eslint` |
| `npm run typecheck` | `tsc --noEmit` |
| `npm run test` | `vitest` |

## Troubleshoot a local change

1. Reproduce the smallest example from the [quick-start guide](/docs/up-to-code-whatsappservicesui/quick-start-guide).
2. Compare required configuration and dependency versions with the README.
3. Check the linked issue tracker for the same error. Include the command, runtime version, and relevant error when reporting a problem; omit credentials.

## Source and help

- [GitHub repository](https://github.com/Up-to-code/whatsappservicesui)
- [Original README](https://github.com/Up-to-code/whatsappservicesui/blob/main/README.md)
- [Issues and existing reports](https://github.com/Up-to-code/whatsappservicesui/issues)