Welcome to BISO Sites Documentation

This is the control center for everything related to the BISO Sites monorepo—repositories, apps, shared packages, and operational playbooks. Whether you are the incoming IT manager or an active contributor, you can navigate the entire system from here.

Choose Your Path

Section Map

Repository

• Project Structure – how the monorepo is organized.
• Installation – prerequisites, tooling, and dev setup.
• Troubleshooting – common issues and fixes.

Applications

• Overview – when to use the web vs admin app.
• Web App – routing, components, API routes, and features.
• Admin App – authentication, permissions, and editor workflows.

Packages

• @repo/api – Appwrite client usage patterns.
• @repo/payment – Vipps integration steps.
• @repo/ui & @repo/editor – reusable components and the Puck builder.

Development

• Guides – auth, database, forms, i18n, styling, and tests.
• Command references for linting, type-checking, and builds live in Reference.

Architecture

• Overview – big-picture system design.
• Applications & Packages – how each piece collaborates.
• Data Flow & Dependency Injection – learn how requests move through the stack.

Operations

• Operations Overview – deployment models and infrastructure.
• Environment Variables – canonical env var definitions.
• Appwrite Setup & Docker Guide – external services.

Reference

• Commands Reference – everything you can run with Bun/Turbo.

Quick Actions

• ✅ Set up local dev: bun run dev (all apps) or bun run dev --filter=web.
• 🔁 Run quality gates: bun run lint, bun run check-types, bun run build.
• 🚀 Deploy: follow Operations Overview and the per-app checklists.
• 🧭 Need support? Open a GitHub issue and link the relevant doc page.

Technology Stack

• Frontend: Next.js 15, React 19, TypeScript
• Styling: Tailwind CSS
• Backend: Appwrite (Database, Auth, Storage)
• Payment: Vipps MobilePay
• i18n: next-intl (Norwegian & English)
• Monorepo: Turborepo with Bun

Project Structure

Getting Help

• Browse this documentation and follow the cross-links.
• Check Troubleshooting.
• Consult the Commands Reference when you forget a script.
• Update docs whenever you discover a new process so the next maintainer has a smoother handover.