Global Data (< PagesJS 1.0.0) | Yext Hitchhikers Platform
Overview
Often there is shared data that you want to use across pages on your site. You could hardcode this information, but sometimes you want this content to be configurable by a separate content team. In this scenario, you can use Content to power global data via a site entity.
Content
First, you will want to create a site entity type and create one entity of that type. While the entity type and the schema can be anything you want, we recommend the following conventions:
- Create a new
Siteentity type. - Add any relevant fields to this entity type.
- Create a single instance of your new
Siteentity type. - Populate the fields on the entity with content you want to make accessible across your site.
Stream Definition
Next, you need to define a site stream. To do so, create a site-stream.json file within your sites-config directory.
sites-config/site-stream.json.
Below is an example definition. Note that unlike in a streams-powered template, this stream will filter by entityIds and not entityTypes.
{
"$id": "site-entity",
"filter": {
"entityIds": ["SITE_ENTITY_ID_GOES_HERE"] // Site Entity ID
},
"fields": ["name"], // Fields to pull from the entity type
"localization": {
"locales": ["en"],
"primary": false
}
}Access Site Data
Once the site stream has been set up, you can then access the site data in any template, and there will be a new field on the document named _site. This property will contain any of the fields specified in the definition above.
Here is an example of a template that uses global data.
const Static: Template<TemplateRenderProps> = ({ document }) => {
const { _site } = document;
return (
<Layout footer={<div>©️ {_site.name}</div>}>
<div>Hello World</div>
</Layout>
);
};