nhovratov/mask-to-content-blocks

1. This repository is a TYPO3 extension whose only job is to migrate existing Mask content elements to TYPO3 Content Blocks. It is not a site feature extension; it is a one-shot migration utility that runs inside a TYPO3 installation.

2. The main entry point is a TYPO3 CLI command, mask-to-content-blocks:migrate, implemented in Classes/Command/MaskToContentBlocksCommand.php. The command is the orchestration layer: it reads the currently loaded Mask definitions and generates Content Block definitions.

3. The migration writes the generated Content Blocks back into the same extension context where the Mask elements already live. That makes the tool a transformation bridge between two TYPO3 content-type systems rather than a standalone generator.

4. A dedicated service, Classes/Service/SvgIconService.php, handles SVG icon-related processing during generation. This suggests the migration preserves or converts icon assets as part of the Content Block output, which is a separate concern from the core element conversion logic.

5. Dependency wiring is handled through TYPO3’s service container in Configuration/Services.yaml. That file registers the command and service classes for injection, so the architecture is based on framework-managed services rather than direct instantiation.

6. The system boundary is very clear: it depends on an existing TYPO3 v13 runtime with Mask already installed and populated. The extension does not store or manage content itself; it transforms configuration/code that already exists in the TYPO3 instance.

7. The output side targets TYPO3 Content Blocks, the official TYPO3 mechanism for defining content types. So the migration path is: Mask element metadata in TYPO3 → command execution → generated Content Block definitions → manual verification and cleanup.

8. The repository also contains a .github/workflows/publish.yml, indicating automated release/publishing for the extension package. This affects distribution, not runtime behavior.

9. .ddev/config.yaml shows the project is set up for local TYPO3 development in DDEV, which matters mainly for spinning up the required TYPO3 environment and testing the migration command.

10. Operationally, the README describes a manual post-migration boundary: after generation, Mask and this extension can be removed, but TypoScript overrides and frontend/backend previews may need adjustment. That means the tool handles structure conversion, while presentation-layer validation remains outside its scope.

11. In architectural terms, this repo is a small, command-driven migration adapter with one primary workflow and one supporting service, sitting between two TYPO3 content-modeling systems.