How does it work?
You start by choosing which data sources you want to use (triggers).
Afterward, you begin designing your schema by mapping which data from your data sources you want to use, e.g., a title. The actual schema design is done in the properties object.
If you want to make your schema routable you define a route. By defining a route, you can fetch it via the Delivery API.
When you finish designing your schema, it’s time to deploy it. Deploying the schema will automatically generate a View for each Source Entity Type.
A View is the actual data that has been transformed. If you have 10 Source Entity Types linked to your schema, this will generate 10 Views.
- Deploy the schema again (this will regenerate all Views).
- A new Source Entity with the same type is available (this will only generate Views for the new Source Entities).
- A Source Entity gets Created, Updated, or Deleted via the Ingest API (This will affect the Views for the specific Source Entity).
Example
Below is a simple example showing how a schema can look for transforming source entities with the type offrontPage.
- Source entity
- Schema design
- Output data
Given the
frontPage source entity have the following content.Source entity example