Content node collections should optionally include node bodies

[aralshawa]

If I may revive the topic introduced in #881.

As of the v1.0.0 release, I do not see a mechanism to return the complete body associated with a content node. This is only done when an id is explicitly specified and a single node is returned as opposed to a content collection list. I've been sleuthing through the source of the core API and cannot see a native way to return the content body of a document. The approaches I'm personally exploring at the moment are: taking a custom plugin approach to "transform" what is returned to include the body and an inelegant solution involving extrapolating the content IDs and querying for each individually.

I'm curious to see if I may have missed some functionality that may have been integrated. The prime use case for such a need in my experience is when there is a one-to-many relationship between statically generated page and content nodes.

[MoOx]

@aralshawa Hi. Currently there is not "super" easy way unless you do a plugin indeed. I am currently thinking about another way of fetching content but that will take time to produce as I am thinking about a entire new fetching system.