the ContentCollection has a ContentElementWrapping that adds some meta tags around it in the backend that will later be removed via JS.
But for the Augmenter it looks like multiple tags and then it has to add a surrounding div.
Those two objects don’t like each other so much sadly.
You can either fix this by directly using the ContentCollectionRendererer and take care of the caching config etc. yourself.
Or you define the node itself as the content collection without the node in-between and therefore have already the ContentElementWrapping from the ContentComponent and you can turn off the one from the collection.
Im using atomic fusion and the next step should be adding css modules.
So i need a solution with a reusable component for manipulating the content collection without loosing the default contentElementWrapping.
Now my solution is a helper component with the Augmenter. It is theoretically reusable in my other components with similar collections. I think a separate component with the augmenter to add own attributes is useful for separation of concerns.
Im Using The Columns Node as ContentCollection and the fusion is the normal atomic fusion stuff. To putt the wrapper component with the augmenter between the content-collection and contentElementWrapping, i use @process and @position. And now it’s working like expected. It’s a clean html markup in frontend and backend.
Regarding the naming… that’s why I personally neither do or recommend the naming part of atomic design. IMO it wastes brain power.
I have f.e. a components folder and there for each usable component a subfolder with separated integration and presentation parts.