I am beginning to migrate a large v7 site to v8, so I have a chance to revisit some decisions made during the v7 implementation.
We have a media section with about 1200 media nodes, and I could see this number going up to 5000 or so within a few years. We're facing a couple problems with media:
Media nodes do not support v8's language variants. We want to associate translated data with media nodes, like alt text.
Media nodes do not support 'send to publish' approvals like content nodes, which makes the content team's workflows more difficult.
What would be the downsides to switching all of our media nodes to be content nodes, with 'upload' and 'image cropper' properties on them? I assume there is a performance disadvantage, but how significant would it be, for 1200-5000 nodes?
Downsides of adding media as content nodes?
I am beginning to migrate a large v7 site to v8, so I have a chance to revisit some decisions made during the v7 implementation.
We have a media section with about 1200 media nodes, and I could see this number going up to 5000 or so within a few years. We're facing a couple problems with media:
Media nodes do not support v8's language variants. We want to associate translated data with media nodes, like alt text.
Media nodes do not support 'send to publish' approvals like content nodes, which makes the content team's workflows more difficult.
What would be the downsides to switching all of our media nodes to be content nodes, with 'upload' and 'image cropper' properties on them? I assume there is a performance disadvantage, but how significant would it be, for 1200-5000 nodes?
Thanks,
David
is working on a reply...