Support relations (aggregate/composite) in a way that makes sense to humans about gitify HOT 3 OPEN

Would also be good to do this for template variable values. Either store TV values as subdirectory data (less optimal) or within the resource's html file (more optimal, from an editing perspective).

from gitify.

Maybe with one-to-(one/many) relations we could skip adding extra directories and files, instead adding it right in to the main object.. like the example with the package/versions, that could in redactor.yaml contain a versions array with all the versions..

from gitify.

And with plugin events (#14) that would be like..

data:
  packages:
    class: modPlugin
    primary: name
    relations: 
       events:
         class: modPluginEvent
         alias: Events

name: MyPlugin
description: best one ever
events:
  -
    event: OnHandleRequest
    priority: 5
    propertyset: 0
  -
    event: OnDocFormRender
    priority: 2
    propertyset: 0

-----

$hello = 'Hi!';
$world = 'Earth';

$event->output($hello . $world);

from gitify.