Thanks @AmberV! I really appreciate that you even put together a small demo project!
Let me just rephrase to see if I understood correctly. The Prefix/suffix fields should actually work as “raw text” and the <p> enclosure produced by the compiler is a bug.
The Paragraph prefix/suffix fields are also “raw text”, but enclose each paragraph, while the Prefix/suffix fields enclose a contiguous sequence of equally styled paragraphs. (The manual is not really clear about that, so that is what I guessed.)
The method with defining the “<div class=…> … </div>” enclosure in the compiler settings is exactly what I was striving for, as it keeps the HTML and CSS code separate from the source - just as you point out.
Btw. : Is there a reason why the CSS pane does only appear for epub3 compiles and not for epub2? Seems to be an oversight to me.
Thanks for your help. Really appreciate it. Do you have any comments to my other post (Workflow Recommendations ?