Theme settings in config or data? about jekyll-help HOT 5 CLOSED

For my plugins I've been favouring option #2, simply because it's
segregated. It's easier to ask users for their _data/config.yml file and
get just the relevant settings. It's also an organisational tool. Just with
jekyll plus a few other settings, my _settings.yml file is getting quite
long as it is.

On 22 April 2014 06:24, Anatol Broder [email protected] wrote:

I write a customizable theme for Jekyll. Call it theme. I see two places
where the user can place her settings:

_config.yml

theme:
option1: value1
option2: value2

Then I access the settings via site.theme.
2.

_data/theme.yml

option1: value1option2: value2

Then I access the settings via site.data.theme.

Which one is better and why?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/21
.

from jekyll-help.

I would say _config.yml, since you're configuring the theme. Use data for real datasets like government organizations that use GitHub.

from jekyll-help.

I'm bit more inclined to the _config.yml; both ways are good and functionally the same, but those options seems to be more like configuration settings.

from jekyll-help.

I use _data/settings.yaml for anything I want to expose to non-technical people, and config for everything else.

from jekyll-help.

Thank you for opinions. I will use _config.yml because:

• the file already exists in every installation
• _data should contain user content only

from jekyll-help.