You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When previewing content, is it possible to make the site.data object populated? Content that will be available via Jekyll will parse the _data folder and add any .yml (amongst other) files into site.data for use (e.g. categories).
Without the site.data object, previews that rely on the data can look distorted and I feel this would benefit many users. I have read the documentation regarding the use of JSONP files to make data available but it doesn't really meet the needs.
This field accepts a list of absolute .JSONP paths to content that is loaded during Jekyll live previews. This is particularly useful for building out tags or categories that should be present during preview.
Has anyone else come accross this issue or think they would find it beneficial?
The text was updated successfully, but these errors were encountered:
When previewing content, is it possible to make the
site.data
object populated? Content that will be available via Jekyll will parse the_data
folder and add any.yml
(amongst other) files intosite.data
for use (e.g. categories).Without the site.data object, previews that rely on the data can look distorted and I feel this would benefit many users. I have read the documentation regarding the use of JSONP files to make data available but it doesn't really meet the needs.
Has anyone else come accross this issue or think they would find it beneficial?
The text was updated successfully, but these errors were encountered: