Migration of plain Flux elements (no columns)

dkmedie / fluxmigrate

Tool to help migrate from the TYPO3 extension Flux to a solution closer to core

GNU General Public License v3.0

1 stars 0 forks source link

Migration of plain Flux elements (no columns) #3

Open stigfaerch opened 2 years ago

stigfaerch commented 2 years ago

How should plain Flux elements be migrated? Any extension you think is necessary to depend on?

jonaseberle commented 2 years ago

I'll gather some possible "targets":

TYPO3 Core (based on fluid_styled_content fields, palettes and lib.contentElement) Output format: TCA/Overrides/*.php, .typoscript, .html (either into an existing extension or as a new composer package)
TYPO3 Core (not based on fluid_styled_content) Output format: same
mask Output format: .json (latest version supports a single .json per content element), .html
Content Blocks Registration API Output format: contentBlock / composer package
Dynamic Content Elements (DCE) Output format: structure in database(?), .html

jonaseberle commented 2 years ago

I would like to build it in a modular way where the target output process is a kind of OutputPlugin: So we could start with one target but we or others can add other options later. As time goes by, we might need new OutputPlugins for new versions to support new features/changes in the targets.

I would favor the first option (TYPO3 Core + fluid_styled_content), but I am open.

wolffc commented 2 years ago

I like the idea of OutputPlugins and also think the Focus should be on TYPO3 Core + fluid_styled_content.

because most people migrating away from flux would like to reduce dependancies on other packages.