content-block-registration-api
content-block-registration-api copied to clipboard
This is a repository of the TYPO3 Structured Content Initiative. It provides the registration API for Content Blocks for TYPO3.
TODO: Discussion if this is really necessary and how exactly this should be done if so.
# As an integrator, I want to use the example content blocks in my installation, to benefit from existing solutions. ## Acceptance criteria - [ ] The example content blocks...
Copied from #45
# As an integrator, I can define display conditions for a field in the EditingInterface.yaml, so that the field is only shown in certain cases. ## Acceptance criteria - [...
# As an integrator, I can define crop variants for an image field, so that specific image sizes can be applied to the image field. ## Acceptance criteria - [...
I came across that when copy-pasting content blocks. Renaming the translations IDs might just not be necessary.
# As a *Integrator*, I can use *language labels* in EditorPreview, to give the editor *more information about the data* in contentBlock ## Acceptance criteria - [ ] In content...
# As an integrator, I can configure my content blocks, so that my editors only see the content block fields. ## Acceptance criteria - [ ] Some content blocks can...
As an integrator, I can configure field of type Color in the Content Blocks Builder, so that I don't have to add it manually to the EditingInterace.yaml ## Acceptance criteria...
As an integrator, I can configure field of type `Datetime` in the Content Blocks Builder, so that I don't have to add it manually to the EditingInterace.yaml ## Acceptance criteria...