Quote from: donshakespeare at Nov 24, 2016, 02:10 AMRE: mtalvenheimo
RE: Mark Hamstra
On a good day I'd even argue that images don't belong in a RTE, because you'll often want to resize the source image, and perhaps use something like the picture element instead of an img tag for responsive images. That's a specialised type of content that RTEs aren't typically equipped to deal with in a flexible way.
Wat!!?!!
No day is good enough to engage in such an argument. What is richtext without the wealth of images? What is 1000 words if not one picture? What is a RTE without awesome image capabilities? ...
... Enter TinyMCE (I mean the official tinymce.com version)
???? That's a specialised type of content that RTEs aren't typically equipped to deal with in a flexible way ...????
Begging to defer; though I can't speak for any other RTE on the market but TinyMCE.
I had a feeling you'd disagree!
I'm not arguing against using images, just that I don't think RTEs are
always the best possible means for dealing with rich media like images, videos, widgets or what have you. If you're just throwing an image in the content and that's all you're going to do with it, then sure, use the RTE.
But the name of the thing is still "rich
text editor". Build fancy plugins all you want, but its core goal is to enhance text. If that includes a nice image on the side, fine. But if it includes a nice image that has several breakpoints of automatically generated (or manually selected) crops, the markup of which you might need to change across all resources on your site because you've switched polyfills or forgot the IE8/9 conditional comment markup to make it work cross-browser, that's when I'd argue for separating the markup (an
or
tag) from the content (the image/image url), and to use specialised blocks for specialised types of content.
It's called
Modular Content and is a way of thinking about/building pages beyond just an image in the content and a dozen templates to choose from.
That's where something like ContentBlocks comes in, which allows you to use a RTE for blocks of basic content (including images if you want), as well as special widgets with their own processing and templates for content that needs a bit more markup/content separation.
Again, maybe you don't need anything like that. Insert an image here, make it accept a div there. For many people that's all they need, and they've got plenty of choice to do that!
But when you start approaching things with modular content in mind, you're going to need something other than a RTE at the core in my opinion. It will most likely still
use a RTE, and you may not use it on every single page because your blog is just a bunch of text and images compared to your landing pages, but it's a different set of ideas that deserves something different.
If you disagree with that and still think I'm blasphemous by saying images or other rich types of content don't
always belong in a RTE, I'd love to hear why you decided to work on Structures, as the idea of that extra is rather similar despite the different implementation
☆ A M B ☆
), but there is no denying that Redactor attempts to clean up the markup. I'd say Redactor is definitely more opinionated in what it does and doesn't do, so it's probably true. 
