Skip to content
Slingshot

Legacy: Config-Driven Overview

Config-driven is the older name for what the docs now split into two clearer sections:

Those sections are now the canonical docs path.

If you landed here

Section titled “If you landed here”

Use this mapping:

  • definePackage(...), domain(...), route.*(...), capabilities, and entityRef(...) now live under Package-First Authoring
  • defineEntity(...), defineOperations(...), storage wiring, generated routes, overrides, and extra routes now live under Entity System

Canonical path

Section titled “Canonical path”
Quick Start Start with the normal app scaffold.
App Authoring Learn the core API surface: app assembly, config, context, events, WebSockets, SSE, and composition.
Package-First Authoring Learn the canonical package-level authoring model.
Entity System Learn the canonical model for data-shaped domains.

Why this changed

Section titled “Why this changed”

Config-driven was too broad. It mixed:

  • package authoring
  • entity authoring
  • route policy
  • storage wiring
  • escape hatches

That made it harder for users to answer basic questions like:

  • how do I scaffold an app?
  • where is the normal package story?
  • where is the normal entity story?
  • where do the advanced customizations begin?

The new split makes those paths explicit.

Section titled “Legacy deep links”

The old config-driven/* pages still exist for compatibility and deeper reference material, but they are no longer the main learning path.