from my understanding, a Collection is the base class that a Page inherits from(extends or whatever) so Collections have a base class, a PageID has the same CollectionID, and so you can think of a Collection as basically a cID as the key, you have base attributes(cName, cDescription, cDatePublic) as part of the class, other ones you add are CollectionAttributes and are not required to be present.

A Collection appears to be boiled down to the really basic details of a base page mapped to Areas(the things blocks belong to), and your versioning of pages is tied to collection versions, which are associated to the initial base collection you created.

For all intents and purposes you usually always interact with the Page object so Collections are just really organization things? That make any kind of sense?

what I mean is if you look at an area:



that $c is the currentPage/Collection object

meh, right?

Now how about doing:


On some other page? That $a->display( is being passed in a collection that isn't the current page, but it still renders since it pulls in THAT collections area(not the current one that is being rendered) which makes me think of them as holders of the areas as their main purpose.

This is getting long-winded, sorry. Hope that helped.

tldr; use Pages, not Collections.