Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable replacing feature and other config objects from the site scope to other objects #22

Open
briandominick opened this issue May 22, 2021 · 0 comments
Labels
enhancement New feature or request Jekyll Involves working heavily with or extending Jekyll SSG Liquid Incorporates Liquid templating

Comments

@briandominick
Copy link
Contributor

Right now, most features and other theme settings draw from the site scope defined by Jekyll configuration files.

It would be nice to provide (at the point of expression in layout/include templates) an alternate source for any object. The object would need the same required properties, but this would enable proviing configuration in data files.

WORKAROUND: For now, the optimal means of achieving this is to source the different site-scoped objects in separate files and list all files in your Jekyll command using bundle exec jekyll build --config file1.yml,file2.yml. To break up the giant site.features scope into multiple files, you''ll need to compile multiple child objects into one, which is not handled by AsciiDocsy alone.

@briandominick briandominick added enhancement New feature or request Jekyll Involves working heavily with or extending Jekyll SSG Liquid Incorporates Liquid templating labels May 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Jekyll Involves working heavily with or extending Jekyll SSG Liquid Incorporates Liquid templating
Projects
None yet
Development

No branches or pull requests

1 participant