Hi again,
have to prevent editors from fancy powerpoint-fired layout and confusing possibilities. Would like to restrict selection to two main types on the top:
Hey aertmann,
thanks.
No problem. I guess new backend-solution «Without-Aloha» will change a lot: Maybe also this. Or do you think, I should do a pull request because of change this also for Post-Aloha-Time?
Did someone know best practice or docu to include own CSS for Backend?
So I could do my own rule. Think:
Not sure, hopefully not as the new editor should be more flexible/configurable. However you’re also the first one I’ve seen request this, so it’s unlikely something that will be tested for.
And yeah that css trick will certainly work, depending on how you include your css either wrap in with the neos:rendering.inBackend view helper or a fusion condition like @if.isInBackend = ${documentNode.context.inBackend}
I’m looking forward to the new and don’t pull a request.
For now and for so little instruction I decided to insert CSS-statement in «front-end» SCSS->CSS. Rocks!