FEATURE: Preview for non site packages
The packages
configuration can now be used to configure non-site packages for previewing in the styleguide.
When a prototype of a non-site package is rendered Monocle will only load the Root.fusion of this specific package and the Monocle Root.fusion. Every other fusion including the default fusion has to be included explicitly. This mimics the behavior of the classic FusionView that is used for FusionRendering of Flow Controller Actions.
Sitegeist:
Monocle:
packages:
#add a key to the package list without package specific configuration
'Vendor.Example': {}
In addition a smarter and configurable way to determine the defaultPackageKey was added.
If a domain can be identified from the current request monocle will use this to determine the initial sitePackage.
If that does not work a newly added setting defaultPackageKey
is used. If this setting is not set the key of
the first site package or the first key in the packages
configuration is used.
Please note that Monocle still has a dependency to Neos. We are planning to change this at some point in future.