WIP: Implement Arbitrary Collection Support #2028

wants to merge 25 commits into


None yet
3 participants

parkr commented Feb 11, 2014

Fixes #1941.

  • Configuration handling for collections key
  • Configuration handling for render key
  • Read in all Collections
  • Render collections in render config array
  • Figure out how pages should work with relationship to Collection
  • Clean up Site with any pages/posts handling
  • Write a million tests
  • Security review (/cc @jekyll/gh-pages)
  • Validate collection names (maybe not data, for example? Or should data become a collection and we add in the backwards-compatibility of the current implementation as necessary?

parkr added this to the 2.0 milestone Feb 11, 2014

parkr added the Feature label Feb 11, 2014

parkr self-assigned this Feb 11, 2014


benbalter commented Feb 11, 2014

Believe from initial discussions posts and pages would become a collection, and maybe this is an optimization saved for 2.1, but thinking through it, I believe data can become a collection as well (reading YAML, rather than MD).


parkr commented Feb 12, 2014

Believe from initial discussions posts and pages would become a collection

Yep, that's still happening. The question above refers to "what is a page?" given that pages aren't Collections in the same sense that they are files in _pages like all the other collections. They behave somewhat differently in terms of their source locations.

parkr closed this Mar 17, 2014

parkr reopened this Mar 17, 2014

parkr closed this Apr 3, 2014

parkr deleted the collections branch Apr 3, 2014


benbalter commented Apr 3, 2014

Closed in favor of #2199.

jekyllbot locked and limited conversation to collaborators Feb 27, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.