Example Concept: Feature Flags Pipeline

Use this as a blueprint for explaining architecture, data flow, or abstract concepts.

Overview

Feature flags let you ship changes to a subset of users, toggle experiments, or disable unstable features without redeploying.

When to use

• Launching a beta version of a page.
• Gradually enabling integrations (Vipps, Appwrite collections) while monitoring metrics.
• Providing per-tenant customization.

How it works

1. Admin toggle – Editors set flag values in the admin app (/admin/experiments).
2. Appwrite storage – Flags are stored in the feature_flags collection with context (environment, locale, rollout %).
3. Runtime lookup – Web and admin apps read flags via @repo/api in Server Components or server actions.
4. Rendering – Components branch on the flag value (SSR-safe).

Folder layout

Related documentation

• @repo/api Package – retrieving Appwrite documents.
• Admin App Overview – where editors manage flags.
• Web App Components – conditional rendering patterns.