Skip to content

Getting started

This page explains how LionPOS documentation is organized—user guides for Admin and Vendor apps versus technical references for engineers—and where each audience should start.


GoalsNon-goals
Pick the right entry (Admin vs Vendor vs Technical) quicklyReplace Swagger or the backend as the API contract source
Understand route naming and doc conventions at a glanceList every REST field or screen variant here

  • User guide — procedures for Admin and Vendor web apps (dashboards, POS, catalog, finance).
  • Technical — monorepo, API, auth, tenancy, and integrations (Technical overview).
  • API details remain in Swagger (API conventions).

  1. Open the documentation home.
  2. Use the table below to jump to Admin, Vendor, or Technical overview.
  3. Follow linked guides for the task (orders, catalog, POS, finance, etc.).

  • Guides focus on supported UI flows; JWT lifecycle and HTTPS expectations are covered under Authentication.
  • Account creation and password flows may be policy-driven; some self-serve screens are not fully API-backed—see Sign-in (Admin) and Sign-in (Vendor).

IDScenarioExpected
G1New reader opens Getting startedCan identify Admin vs Vendor vs Technical path
G2Follow link to Admin overviewSystem Panel overview loads
G3Follow link to Vendor overviewMerchant Panel overview loads

For full-stack happy/unhappy catalogues and E2E suitability per module, use System test cases (index).


Use this site in two ways:

  • User guide — procedures for people using the Admin or Vendor web apps (dashboards, POS, catalog, finance).
  • Technical — how the monorepo and API fit together (for engineers and integrators).
RoleStart here
Head office / zone adminSystem Panel overview
Store / vendor operationsMerchant Panel overview — includes POS
Cashier at the laneCashier help center — Vendor Desktop /point-of-sale/* (VI)
Developers / DevOpsTechnical overview

Owner sign-in page — /vendor-login

  • Admin web routes live under /dashboard/* (after login). See System Panel overview for the full route map.
  • Vendor web includes /pos and /dashboard/*. See Merchant Panel overview.
  • API contracts are defined in the backend Swagger UI (see API conventions); this site does not duplicate every field.
  • Authoring progress: repository file apps/docs/DOCUMENTATION-CHECKLIST.md.
  • System test cases (index) — module-linked scenario sheets and coverage checklist.