document Extbase Content Element
Current behavior
extbase extensions all rely on data that are stored in special tables.
The case that the data are coming from the content record itself is not covered in the documentation.
An element like this would be a content element instead of plugin, but can be rendered with controller and view, the repository is in this scenario not used, as the data are delivered already.
Expected behavior/output
How to setup an individual content element with extbase in TypoScript.
A description how to map incoming data in a renderAction() and display it without need for further queries.
Links
https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ExtensionArchitecture/Extbase/Examples/Index.html
TYPO3 versions
[e.g. 11, 12] 11, 12, 13, main
an example extension can be found here: https://github.com/DavidBruchmann/extbase-ce. It's WIP, but can show the general concept already.
Hybrid extbase extensions are thinkable / possible too, where content to be shown above list view or single view are entered in the content-record but also the plugin beside options.
The important issue with DataMapper is solved, the rest is a diligent but routine piece of work. https://github.com/DavidBruchmann/extbase-ce/commit/c2d0cf26c769537cf472955494266c7e92dc2a19
Such scenarios would today probably be solved by content blocks or Mask, no extbase neeeded