Configuring Recipe Extensions

Recipe extensions can expose configuration parameters that are set in the Cook's configuration file, cook-config.yml. Most of the default extensions supplied by CCI Europe (the ones downloaded from npm.escenic.com) have very few configuration parameters, and where necessary, the setup tool ensures that they are supplied with sensible values. You may, however, need to modify some of the defaults set by the setup tool or add some additional settings of your own.

If you do need to configure a recipe extension, you can do so by creating a cook-config.yaml override file in your publication repository, as described in Overriding Setup Defaults, and adding the necessary parameter settings to it.

For information about all the configuration parameters exposed by the default extensions, check the readme files on http://npm.escenic.com/. You will, for example, find information about the cue-front-extension-binary extension at http://npm.escenic.com/#/detail/@escenic/cue-front-extension-binary.

Reasons for needing to configure a recipe extension include:

• Support for image content types that are not called picture (see Configuring Image Content Types)

• Support for custom story element types (see Configuring Story Element Types)

• Changing the default URL-GraphQL query mappings (See Configuring URL-GraphQL query mappings)