---
title: "Developers"
description: "CLI, SDK, packages, schemas, deployment, integrations, and contribution guides."
---

## Choose the smallest surface

<div className="hf-route-grid">
  <a href="/developers/cli"><strong>CLI</strong><span>Create, check, render, publish, and automate.</span></a>
  <a href="/sdk/quickstart"><strong>SDK</strong><span>Open, query, edit, and persist compositions.</span></a>
  <a href="/packages/player"><strong>Player</strong><span>Embed and control a seekable composition.</span></a>
  <a href="/packages/core"><strong>Packages</strong><span>Use one focused HyperFrames capability.</span></a>
  <a href="/deploy/cloud"><strong>Deployment</strong><span>Render on managed or self-hosted infrastructure.</span></a>
  <a href="/reference/html-schema"><strong>HTML schema</strong><span>Composition elements, timing, tracks, and variables.</span></a>
</div>

## A good first technical result

Choose one result rather than installing the whole repository:

- render one known project from a script or CI job;
- open one composition with the SDK and change one value;
- embed one project with the Player and seek to a timestamp;
- deploy one minimal render path;
- validate one generated composition against the schema.

Continue to package or reference pages only when that working path requires more control. Most integrations should not depend on every HyperFrames package.

## Working on HyperFrames itself?

Use [Contributing](/contributing) for repository setup, tests, Catalog contributions, and releases. Product integrations should begin with one of the surfaces above instead.