TypoScript from backend to extension

Old setups often have a lot of TypoScript and backend template definitions stored in the backend. There are several advantages to keeping TypoScript code in a config extension instead of the backend alias database:

• Extensions are managed in a git repository
• Site configuration cannot be changed from the backend
• All configuration in one place
• Searchable with an IDE
• ...

Here is a quick summary of the code to move and what can be removed:

Setup

// Remove, domains are handeld in site configuration now
config.baseURL = hostname

// move to setup.typoscript and replace with @import
<INCLUDE_TYPOSCRIPT: source="FILE:EXT:zwbisdrei_config/Configuration/TypoScript/plugins.txt">

Page TS

Move all backend template definitions from the backend to your config extension in Configuration/TSconfig/BackendLayouts/[Default].tsconfig and import in page.tsconfig with @import 'EXT:zwbisdrei_config/Configuration/TSconfig/BackendLayouts/*.tsconfig.

Also move the PageTS code from the page settings to the extension in Configuration/TSconfig/Page/page.tsconfig and registerPageTSConfigFile in Configuration/TCA/Overrides/page.php.