[Neos] RFC: Simplify templates and reduce auto-generated HTML

Bastian Waidelich bastian at typo3.org
Wed Nov 20 15:32:25 CET 2013

Bastian Waidelich wrote:

To add some more details:

> I have spent some time trying to improve the situation in a backwards
> compatible way [...]

The ContentElementViewHelper won't be required and will be marked 
obsolete, but If you use it like:
<neos:contentElement node="{node}" class="{className}" tag="span">
it will just render:
<span class="typo3-neos-nodetypes-<nodeType> {className}">...</span>
making it backwards compatible.

But I'm afraid, the actual question got a bit lost in all the gibberish:

> The problem is that *TYPO3.Neos:Template* is too generic.. We use it for
> menues, stylesheets, page title and what not. And we don't want to add
> the content-element attributes to those obviously.
> [...] Any suggestions?

I just wrote a little script that generates a diagram of all the current 
NodeTypes. For the demo site the result looks like:
http://yuml.me/diagram/scruffy/class/f723362d.png (yellow boxes = 
abstract node types)

If I see it correctly, we might be able to add the meta data only for TS 
objects that are bound to a node of type *TYPO3.Neos:Content* and 
explicitly disable it for *TYPO3.Neos.NodeTypes:Menu* (or remove 
superTypes: ['TYPO3.Neos:Content'] from it's declaration).

Bastian Waidelich

More information about the Neos mailing list