Fusion preview-rendering & propSets
Render the preview for the prototypes via fusion. The used fusion-path can be controlled via Setting preview.fusionRootPath
wich defaults to /<Sitegeist.Monocle:Preview.Page>
This release contains many breaking-changes so please read the change-log below carefully
Changes:
- !!! Fusion Preview: The used fusion-path can be controlled via Setting
preview.fusionRootPath' wich defaults to
/Sitegeist.Monocle:Preview.Page. The fusion preview gets the context
sitePackageKey,
prototypeName,
propSetand
props. By altering the
Sitegeist.Monocle:Preview.Page` prototype or implementing an alternate one you can control the html-the prototype preview is rendered in. - Add prototype
Sitegeist.Monocle:Preview.Page
- Renders the preview Frame for a prototype, makes use of the prototypes below to do so. This prototype mimics the interface ofNeos.Neos:Page
so you can adjust it in the same way - Add prototype
Sitegeist.Monocle:Preview.Prototype
- Render the preview for a single prototype and pass propSets and props - The
@styleguide
annotations now severalpropSets
in addition to props that define different sets of previewDate for each prototype. The propSets can be select via props-tab. - Support to modify boolean props in the props-tab.
- !!! The monocle routes are added automatically via settings and the routes are prefixed with
monocle
- !!! The Settings
viewportPresets
andstructure
are moved into theui
configuration-section - All Settings can be overwritten for each package via
packages.__package_key__
- !!! Settings
additionalResources
andmetaViewport
are removed from the configuration. You can control the included resources by alteringSitegeist.Monocle:Preview.Page
the same way you adjustNeos.Neos:Page
- !!! During rendering the styleguide-props are only applied to the main rendered prototype. If you want to render another prototype with applied styleguide props you can use
Sitegeist.Monocle:Preview.Prototype
. This allows the check in the styleguide wether all needed props are passed down.