Documentation article
Quick start
Start with the playground for exploration and published toolkit packages for integration.
Schema Transformation Web is the product surface. The toolkit packages provide the transformation engine that the web app demonstrates and will eventually expose more deeply.
The easiest place to start is the web playground, but it helps to keep the package model in mind so the docs feel connected rather than split across two worlds.
Keeping those three layers distinct makes the docs easier to navigate and the product easier to evolve.
If you only want to validate a conversion path, start with the playground. It removes install friction and lets you see the supported flow immediately.
If you want to integrate transformations into another system, follow the toolkit repository and published package artifacts instead of relying on local workspace links.
The exact package mix depends on which source and target formats you need, but the docs should keep pointing back to published release artifacts as the default path.
Typical package entry point
npm install @aio/sdk @aio/parser-typescript @aio/generator-json-schema