3. Mayd Configuration
The configuration of the mayd bundles itself has also changed, this migration guide tells you which keys were added, which were changed and how to migrate your config from Mayd 1 to Mayd 2.
For all added keys, please take a look at the corresponding bundle documentation.
Core
- removed
project
: replaced with the hosting bundle config -
changed
assets.css
: renamed toassets.header
css
renamed toheader
. You can now also mix different asset types here.js
renamed tofooter
. You can now also mix different asset types here.
features
: unchanged- removed
locales
: removed without replacement
Files
- removed
file_browser_items_per_page
: removed without replacement - added
upload_storage
- added
image_sizes
Forms
No configuration available, so nothing has changed.
Mailer
The configuration has not changed from Mayd 1 to 2.
Pages
- removed
menus
: replaced with your theme’sFrontendTheme::getMenuLocations()
- removed
slots
: replaced with separateSlot
classes / entities - removed
page_type_routes
: the path is now hardcoded toconfig/page_type_routes
default_website_selector
: unchanged- added
workflow
Redirections
No configuration available, so nothing has changed.
Rich Text
No configuration available, so nothing has changed.
mayd.yaml
While this feature might get deprecated in the future, it is currently possible to use a mayd.yaml
file in your
project (and for some features it’s the only way to integrate some things).
That’s why we list the changes to this file here as well.
- changed
routes
: every sub entry can now either be a string or a{path: "...", priority: 1}
map -
changed
assets
:npm_packages
renamed topackages
-
changed
entries
:-
Now there is a new level between
entries
andjs
/scss
:entries.backend.(js/scss)
andentries.frontend.(js/scss)
- The
js
/scss
entries are no array anymore, but just a single (scalar) entry.
-
page_type_routes
: unchangedform_theme
: unchanged