pattern partial needs to be able to generate dark-light versions automagically

Since one cannot alter the SVGs colors easily with tailwind¹

We need to bolt the functionality of autogenerating dark/light image variants into the pattern partial.

my thought process on how it should work at the moment:

• When explicitly invoked, you may specify tailwind-style color-hue values, OR hexvals

• if specified, those take precedence to any automated hue divination.

• If only one value is provided, the provided is used alongside the default theme mode to determine a nice alternate

• Dark/light mode pattern hues in config by content type. This should be used in the cases where:

  • Have a default value for each content type, and for the site as a whole.
    • If a pattern is included as a background for $contentType, (ie in params, or frontmatter)
    • and a color/hue set (dark/light) is not provided

• Dark/light mode declared in config for contributor background

  • if both values are defined in config. This overrides "defaults"

• Dark/light mode values provided on invocation

  • when instantiating the partial to generate the svg, if you feed it a set of twcolors, or hexvals,

• only one value declared in

• partial consumes site config and assesses the 'default theme variant' (dark/light)

  • This will tell the partial what the given color value should be assigned to in the event that only one color value was providedc.
  • have a default offset dark/light

1. (yes, I know I know... you SUPPOSEDLY can... but really, it's a lot more involved than ya think... an it's kinda fucky) ↩