While the ‘rich text’ field type is useful, it’s not sufficient for some of our needs. We’d really like to have the same editing capabilities that are available in a blog post – insertion of images and galleries, for example, including options for image placement and sizing.
As a workaround, we currently build dynamic page designs with optional elements for images and galleries and pull quotes, and then we use Velo code to expand and collapse those elements, based on whether or not the matching collection fields have content. But that doesn’t handle text flow around images, and all those optional fields make the collection messy and hard to use. Also, inevitably we run into situations where we don’t have enough of the optional fields.