We’ve tested the side by side, creating a test split-text item called “Mass Production on 14th St.”
I can’t seem to get it to appear in the header menu for “Close Readings,” even though it’s set to display all split texts.
I also don’t see an option to set categories for split-text, only tags, so I’m not sure how we will incorporate a split text item into a masonry grid for a chapter that would comprise a series of posts with a split text item or two interspersed.
We think this is a powerful tool, but needs some refining to be more legible to readers. Here are some suggestions:
- Make a clear visual distinction between the primary text block and secondary text block, with different fonts, backgrounds, and more distinct backgrounds. For example, we might want to evoke a printed book for the primary text, while allowing the secondary text/interpretation to appear more digital. The Marianne Moore site, which makes a clear visual distinction between the facsimile on the left and the transcription on the right is a model for this.
- Refine the highlighting function. Whatever analysis is currently being viewed should be on a white background, with the rest of the text greyed out. The corresponding parts of the primary text could appear highlighted or surrounded by a box with the other parts of the text grayed out. Or, as in the Moore site, you could have a highlighted portion of secondary text correspond to a boxed area (border in similar color) of the primary text.
- The text content areas need to display single space lineation for poems. When we single space the lines of the poem, the view mode converts them to paragraphs.
- As discussed we would really like to be able to use jpeg images as a primary text and refer to specific areas of the image.
- The layout ratio and smooth scrolling/auto-scroll options are nice and user-friendly, but we would like them on the inside/dashboard side for the creator to select, rather than giving the user options that could mess with our formatting of the primary and secondary texts, as well as cause unnecessary confusion for users.