TLD and default content dimensions

[benjamink (Benjamin Klix)]

Possible duplicate of:

RFC: Domain based content dimensions

Motivation Yet another customer project. But fear not, it's already implemented and works quite nicely. Well, there are a still a few problems with the Neos backend interface, but those should not be too hard to resolve I guess. And I had to write an aspect to feed additional preset data to the ContentDimensionPresetRepository-thingy. Might be more fun without it. Status quo Using domains instead of / in addition to configured path segments is currently not possible out of the box. Why I conside…

Have you seen the other discussion already, @kapale ?

I think this one could be closed then.