/my/file/path.json
. The file can be viewed at hash-dev.preview.zesty.io/my/file/path.json
or my-custom-domain.com/my/file/path.json
as long as the file and its content has been published. File types that can be used: css, html, json, js, xml, css, csv, tsv, xml, yaml, md, svg, txt, rss, ics, vcf, xhtml./my/file/path.json
or //my-custom-domain.com/my/file/path.json
. We recommend using relative links as the endpoint will render relative to the domain that you're on.
This is important because preview URLs are not cached, they do not collect analytics, Google does not recognize it as their own domain, and it can expose unpublished content.
However, production URLs are cached and thus perform faster, is recognized by Google and collects analytics, and will not expose unpublished content./this/is/my/custom/file.json
/store/12345/my-product/
is capture by a file named /store/*/*/index.parsley
*
as a path part between two forward slashes, and the name index.parsley
at the end of the file path. Please reference the file (resource) resolution loading order./store/12345/my-product/
(represented as a custom file type named /store/*/*/index.parsley
) the identifier is the product id 12345
which is accessed with {{request.pathPart(2)}}
and can be used to query another system like Oracle for product data. This is useful when thousands of products are store externally and do not need to be synchronized into a content instance. /referral/3e5h1/
(represented as a custom file type named /referral/*/index.parsley
where 3e5h1
is a unique identifier which can be accessed with {{request.pathPart(2)}}
and can be used to present a printable coupon on page, or to make a request to an external system via javascript.