Fix bad config YAML in collections example

[happycollision]

If you add the previous version to your config file, you'd get an error on build/serve.

[pathawks]

collections needs to be an array, not a hash.

[happycollision]

That's what I thought, but putting this into the config file:

collections:
  - my_collection:
      output: true

results in this error in the terminal:

Configuration file: /Users/Don/Git Projects/some-site/_config.yml
            Source: /Users/Don/Git Projects/some-site
       Destination: /Users/Don/Git Projects/some-site/_site
 Incremental build: disabled. Enable with --incremental
      Generating... 
jekyll 3.0.2 | Error:  undefined method `gsub' for {"my_collection"=>{"output"=>true}}:Hash

Conversely, this

collections:
  my_collection:
    output: true

produces no errors and behaves as expected (the collection outputs and I can access it at site.my_collection).

This also seems to be exactly in line with the current documentation for collections. (Or that same collection documentation from the latest commit on master)

Just above that link on those pages is the "Step 1" section, which seems to suggest that if you want to specify metadata for a collection, you must not use an array. From the documentation:

Add the following to your site's _config.yml file, replacing my_collection
with the name of your collection:

collections:
- my_collection

You can optionally specify metadata for your collection in the configuration:

collections:
  my_collection:
    foo: bar

Am I missing something?

I guess you're right 👍

[ashmaroli]

👍

[parkr]

Thank you!

@jekyllbot: merge +site