Provide a 'byline' or 'contributors' property

[phillipadsmith]

Every client is going to have to implement a function to create a string from the author names, as well as having to look up the proper name from the API once for each author in the authors property of the module.

Instead, this should be written once in the API code and provided as a property of the module object, e.g,:

byline: Jane Doe and John Doe

Or
byline: Jane Doe, John Doe, and Janice Doe

Or

byline: Jane Doe

Thoughts?

[adrian-the-git]

Alright. It's clear to me that the content loader needs some kind of early-stage translated strings because it doesn't currently have a good way to load the necessary and/y/و strings. Relying on one of the text docs makes the whole thing kind of brittle.

Anyhow I've put a hacked solution in place, but don't parse this byline key because it could potentially list a missing author or contain a typo which the normal relationship-munging code would catch. Really missing relational dbs! And I hate SQL the same as anyone! :)