> For the complete documentation index, see [llms.txt](https://docs.giize.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.giize.com/product-docs/readme.md).

# Ticket Dashboard Docs

This folder is the GitBook-ready documentation layer for `ticket-dashboard`.

It is curated from the raw source documents in `document/`. The purpose of `docs/` is:

* provide a clean reading experience for operators and developers
* separate onboarding guides from low-level API reference
* keep GitBook import and navigation predictable

## Audience

* operators who need to run the app day to day
* engineers who need to debug or extend integrations
* reviewers who need a compact map of the system before reading code

## Recommended Reading Order

1. `Getting Started / Quick Start`
2. `Getting Started / Architecture Overview`
3. `Feature Guides / Order Report` or `Feature Guides / OpenVPN Pipeline`
4. `API Reference / SDP API` and `API Reference / IT Portal API`
5. `API Reference / Staging API` when planning new integrations

## Source Of Truth

The original working notes remain in `document/`.

This `docs/` tree is the publish-friendly layer. When content conflicts:

* treat `document/` as the authoring source
* update `docs/` after the source notes are reviewed

## Current Scope

This version prepares the repo for GitBook import with:

* landing page
* sidebar structure via `SUMMARY.md`
* split reference pages for staging API
* grouped feature and operations guides