title: Composer package where to put client config?
body: <p>I have a composer package designed for use in other projects that has configurations, or rather default settings I'd like the end user to be able to adjust based on their intended use. The package itself can be configured to build things differently depending on the configurations passed to the package's builder class. I'd like there to be default settings, possibly in a settings.yml file (the medium is not a concern, *.conf, *.json, *.php), may be this should go within the package? But then I imagine if that were the case it would be hard for the end user to maintain as it would be overwritten during composer updates? Anyone know what the norm for storing composer vendor packages configs is? </p>
  
  <pre><code>$parameters = [
      'handlers' =&gt; [
          // various depending on client use
          '//widget' =&gt; 'LivingMarkup\Component\Widgets\{name}',
          '//img' =&gt; 'LivingMarkup\Component\Img',
          '//a' =&gt; 'LivingMarkup\Component\A',
          '//var' =&gt; 'LivingMarkup\Component\Variable',
          '//condition' =&gt; 'LivingMarkup\Component\Condition',
          '//redact' =&gt; 'LivingMarkup\Component\Redact'
      ],
      'hooks' =&gt; [
          'beforeLoad' =&gt; 'Executed before onLoad',
          'onLoad' =&gt; 'Loads object data',
          'afterLoad' =&gt; 'Executed after onLoad',
          'beforeRender' =&gt; 'Executed before onLoad',
          'onRender' =&gt; 'RETURN_CALL',
          'afterRender' =&gt; 'Executed after onRender',
      ]
  ];
  </code></pre>
  
  <p>Thank you.</p>