ichhabrecht / mask-export
Export your mask elements as extension
Installs: 176 531
Dependents: 0
Suggesters: 0
Security: 0
Stars: 46
Watchers: 12
Forks: 26
Open Issues: 23
Type:typo3-cms-extension
Requires
- php: ^7.2 || ^8.0
- mask/mask: ^4.0 || ^5.0 || ^6.0 || ^7.1
- typo3/cms-core: ^9.5 || ^10.4.16 || ^11.5
- typo3/cms-extbase: ^9.5 || ^10.4.16 || ^11.5
- typo3/cms-extensionmanager: ^9.5 || ^10.4.16 || ^11.5
- typo3/cms-fluid: ^9.5 || ^10.4.16 || ^11.5
Requires (Dev)
- nimut/testing-framework: 6.x-dev
- phpunit/phpunit: ^8.5
- typo3/cms-fluid-styled-content: ^9.5 || ^10.4.16 || ^11.5
Replaces
- typo3-ter/mask-export: 4.0.2
- dev-main / 4.x-dev
- 4.0.2
- 4.0.1
- 4.0.0
- 3.x-dev
- 3.0.4
- 3.0.3
- 3.0.2
- 3.0.1
- 3.0.0
- 2.4.1
- 2.4.0
- 2.3.0
- 2.2.0
- 2.1.1
- 2.1.0
- 2.0.1
- 2.0.0
- 1.x-dev
- 1.0.0
- 0.9.1
- 0.9.0
- 0.8.0
- 0.7.0
- 0.6.3
- 0.6.2
- 0.6.1
- 0.6.0
- 0.5.0
- 0.4.2
- 0.4.1
- 0.4.0
- 0.3.2
- 0.3.1
- 0.3.0
- 0.2.1
- 0.2.0
- dev-compatibility-mask-8
- dev-pre-merge
- dev-use-references-for-icons
- dev-feature-add-page-template
This package is auto-updated.
Last update: 2024-04-03 22:16:25 UTC
README
Want to create new content elements the easy way?
Use mask and its drag & drop wizard to create content elements the easy way.
Use mask_export to export the content elements into an own extension.
Why
A content element needs some TCA information, TypoScript and database configuration and template files. Actually there is no need to depend on any third party extension when dealing with content elements.
But you don't want to deal with different information in different files and folders. You want to be able to concentrate on what is necessary for the user, not how it has to be implemented in your TYPO3 CMS.
By using mask and mask_export you can do exactly this! Simply create your own content elements by using a drag & drop wizard. Add fields, repeating items, nested content elements within minutes.
Why not
Mask offers an easy way to create content elements but has some disadvantage when you need to take care about performance. Especially the frontend rendering can take at lot of time for uncached pages. Instead of relying on TYPO3 CMS core rendering, all elements are rendered by an own Extbase Controller. As this was needed to support former version of TYPO3 CMS, it was deprecated with the introduction of fluid_styled_content and the concepts of DataProcessors in TYPO 7 LTS.
This is what mask_export is developed for. It takes the content element information from the mask configuration and generates the needed code to get those elements to work with pure TYPO3 CMS core functionality out of the box. It bundles all necessary information into an own extension that can be installed and used in every other TYPO3 CMS system.
Installation
Simply install mask and mask_export with Composer or the Extension Manager.
composer require ichhabrecht/mask-export
Usage
- use the mask wizard to configure own content elements
- change to tab "Code Export"
- if you like change the extension key, the default one is my_mask_export
- either install or download your extension
Best practise
It is recommended to not touch the generated export extension. Instead you should add necessary changes and your own templates into a site package.
This ensures you can edit your content elements within the mask wizard (add further content elements, change settings) and still be able to use the new extension version in your existing system.
You can find some common configuration in the my_maskexport_sitepackage example site package.
Furthermore you can refer to the slides CCE (Custom Content Elements) - Best Practice for additional information.
Community
- Thanks to Marcus Schwemer who wrote about mask_export in his blog TYPO3worx
- Thanks to Thomas Löffler for his ongoing support as Patron