Allow to configure a content in order to fetch data from a third party.
E.g. if we want to fetch content from Contentful:
given we already configured the Contentful credentials somewhere
from the admin we can click to create a new content
we can pick the content provider (in this case Contentful)
then we're presented with a form that will ask us to fill in the content ID
we can also choose the default renderer for that content (from a drop down)
Will be up to the provider to store in the data attribute of the content just the content ID (or other means to fetch the content on the go) or to also store the content allowing local access.
A content provider should be able to update the data section of the content whenever it's triggered.
A content provider should setup itself to receive webhooks or run regularly to update the data attribute of the content.
The default and basic content provider should allow raw editing of the data attribute (in json format).
A content provider should also connect with content created with solidus_static_content.
elia
commented
4 years ago
Allow to configure a content in order to fetch data from a third party.
E.g. if we want to fetch content from Contentful:
Will be up to the provider to store in the data attribute of the content just the content ID (or other means to fetch the content on the go) or to also store the content allowing local access. A content provider should be able to update the data section of the content whenever it's triggered. A content provider should setup itself to receive webhooks or run regularly to update the data attribute of the content.
The default and basic content provider should allow raw editing of the data attribute (in json format).
A content provider should also connect with content created with
solidus_static_content.