Skip to content
CCinder
Cinder documentation

Getting Started

Cinder documentation

Start here for installation, quick start, semantic tags, architecture, and the real local-first SDK path.

Websites you control

Cinder is a semantic runtime for websites you control. These docs are organized to get you from first install to first real command flow as quickly as possible.

Start with the shortest useful path

If you are evaluating the SDK, start here first.

Beyond the core SDK

Choose the path that matches your immediate goal.

I want a first working integration

I want to understand how it works

I need to debug or extend it

What the docs assume

The core product promise

These docs assume the V1 promise is: install Cinder, tag a website you control, resolve common navigation/action/field/output flows locally, and use custom bindings or adapters only when the standard DOM path is not enough.

What is true about the current SDK

  • the browser runtime is the product core
  • semantic tags and graph structure are primary, not prompt tricks
  • local-first resolution is the default path
  • fallback is optional, bounded, and secondary
  • ambiguity is handled more honestly than earlier MVP versions
  • extension points now exist for routes, DOM adapters, custom intents, runtime context, and runtime events

Suggested next pages

  1. Installation
  2. Quick Start
  3. Semantic Tags
  4. Scanning the App
  5. Cinder.run

Continue reading