Documentation
Fumadocs is the single maintained documentation source.
Documentation
Fumadocs (apps/docs) is the only maintained documentation source for ByteBite. It is part of the monorepo (ADR-020) and is served at http://docs.bytebite.test in development and docs.staging.getbytebite.co in staging.
Edit Markdown/MDX under apps/docs/content/docs/. Do not keep a second documentation tree.
Content structure
content/docs/
├── index.mdx
├── documentation-status.mdx
├── architecture/
│ ├── stack.mdx
│ ├── monorepo-structure.mdx
│ ├── tenancy.mdx
│ ├── profile.mdx
│ ├── menu.mdx
│ ├── storage.mdx
│ ├── cart.mdx
│ ├── checkout.mdx
│ ├── delivery.mdx
│ ├── acceptance.mdx
│ ├── kitchen.mdx
│ ├── hours.mdx
│ ├── auth.mdx
│ ├── notifications.mdx
│ └── adr/
├── infrastructure/ # Hosting, networking, ops (source of truth)
│ ├── overview.mdx
│ ├── architecture.mdx
│ ├── environments.mdx
│ ├── compute.mdx … known-gaps.mdx
├── domain/
│ └── product-requirements.mdx
├── development/
│ └── getting-started.mdx
├── deployment/
│ ├── overview.mdx
│ ├── local.mdx
│ ├── staging.mdx
│ └── production.mdx
└── operations/
└── overview.mdxInfrastructure documentation is the operational source of truth for hosting, networking, TLS, deployment, and day-two operations. Application architecture and ADRs remain under architecture/.
Schema note
packages/db models restaurants, restaurant_profiles, restaurant_domains, menu_categories, menu_items, carts, cart_items, orders, order_items, order_delivery_addresses, delivery_rules, restaurant_opening_windows, and Better Auth user / session / account / verification. Media files live in object storage; only logo_url / image_url are stored. There are no notification tables. See Tenancy & storefront, Restaurant profile, Menu catalog, Object storage uploads, Guest cart, Checkout & orders, Delivery, Accept, reject & timeout, Kitchen status, Opening hours, Staff authentication, and Transactional notifications.