Introduction

Vard is a schema-driven content layer for developers who build sites for clients. You define your content structure in TypeScript. Vard provisions a dashboard where your clients can edit content — no backend work, no redeploys.

How it fits into your stack

Vard sits between your codebase and your client. You install the SDK, define a schema, and deploy. From that point on, your client can edit any field you’ve exposed — text, images, collections — directly from their Vard dashboard.

Your codebase (TypeScript schema)
        ↓
    vard deploy
        ↓
  Client dashboard ← client edits here
        ↓
  Content API ← your app reads from here

Who it’s for

Vard is built for developers who:

• Build sites for clients and spend time fielding “can you change this text” requests
• Want to hand off content editing without giving clients access to the codebase
• Need type-safe content with runtime defaults, not a headless CMS with a GUI schema builder

What Vard is not

• Not a page builder or visual editor
• Not a database — content values are stored and served by Vard, not your own DB
• Not a CMS that requires you to model content in a web UI

Next steps

• Quick Start — get to working in under 5 minutes
• How It Works — understand the mental model before writing code