Download the PHP package mindscreen/neos-prototype-generator without Composer
On this page you can find all versions of the php package mindscreen/neos-prototype-generator. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download mindscreen/neos-prototype-generator
More information about mindscreen/neos-prototype-generator
Files in mindscreen/neos-prototype-generator
Package neos-prototype-generator
Short Description Generate default fusion-prototypes to map to view-components
License GPL-3.0-or-later
Informations about the package neos-prototype-generator
Mindscreen.Neos.PrototypeGenerator
This package provides a default prototype generator for creating fusion component-based prototypes to enable front-end developers to create a new node-type based on a yaml-configuration and a view-component without worrying about basic property-mapping.
Installation
composer require mindscreen/neos-prototype-generator
Usage
- Extend your new node-type from
Mindscreen.Neos:ContentComponent
(or include the'Mindscreen.Neos:PrototypeGeneratorMixin'
). - Inline-editable properties are recognized with
type: string
andui.inlineEditable: true
. Block-editing can be enabled withui.inline.editorOptions.multiLine: true
. - Images (
Neos\Media\Domain\Model\ImageInterface
) provide a<property>Uri
and<property>Asset
. - Child-nodes will render with their specific node as
node
in the context;Neos.Neos:ContentCollection
will render with the respectivenodePath
- Set a specific target-component prototype in
options.componentName
. - Specify the child-node mapping in
options.componentMapping.childNodes.<nodeName>
Configuration
Settings:
Usage in node-types:
Notes
Content-Collections
If a node-type is a Neos.Neos:ContentCollection
(e.g. to generate a simple box-component), a ContentCollection will be rendered as content
. This can be configured with the option options.componentMapping.childNodes.this
.