Table of Contents | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
...
Code Block | ||
---|---|---|
| ||
{ "id": "unique-manifest-id", "type": "StrapiContent", "contentType": "contentAPI-typeID-from-strapi", "contentValue": 3, // optional "displayFieldName": "DisplayField", "display": "Strapi Content Test" } |
...
id: A unique string (no spaces) to identify this setting against others for this exhibit
type: Always string
StrapiContent
when pulling content values from StrapicontentType: The dynamic content type type’s API-ID from Strapi, made to be plural (include an “s” at the end - see below screenshots): by convention it should be singular, or whatever the original value was entered as when creating the collection type.
contentValue: The ID value of the content item that should be the value of this setting or null
displayFieldName: The string name of the field that should be used for selection within the Gumband UI
display: The setting label for within the Gumband UI
To find the contentType for the manifest, select the content type under “Collection Types” in the left navbar and then select a single content itemn entry. Use the value next to “API ID” under the item header, and add an “s” to make that string plural. In this example, you would use contentType “oscar-test-types” in the manifest.
...
Anchor | ||||
---|---|---|---|---|
|
...
When connecting these content types to Gumband, by default the Strapi API only returns nested entries one level deep. Additional business logic can be added to your Gumband-Strapi instance to be able to query more complex data structures. Talk to your Gumband representative for more details.
Content Entry Customization
Each strapi field can be configured with a unique label and description. See the video walkthrough below:
...