Review main Abandoned

66064[WIP]]FEATURE] Introduce FLUIDPAGE

Georg Ringer CR 0 V 0 Hard +307 −1 updated 10/19/21, 19:01

Commit message

A new contentObject `FLUIDPAGE` incorporates all the best practices to
setup a new site. The site coniguration got a new field to select a site
package extension.

The only TypoScript it needs is
```
page.20 = FLUIDPAGE
```

The used backend_layout defines the template which is loaded
automatically from
Resources/Private/Page/Templates/<BackendLayoutName>.html. Also the path
to the partials and layouts is automatically setup

The TS to set templateRootPaths, layoutRootPaths, partialRootPaths is
still in place to be able to set fallback setups, especially useful for
multisites.

Todos:
- should the path mapping be configurable?
- Naming of site_package/extension
- Should we keep the FluidTemplateAssets even though we have the asset
VH?

Review

  • Code review CR 0

    Imported before Forger kept the single votes, the next import adds them.

  • Verified V 0

    Imported before Forger kept the single votes, the next import adds them.

Files 4