<p> tag missing in WYSIWYG editor

[StrangeTech]

The answer is different depending on whether you are using Tailwind or not.

Please see this thread for details about how to do this without Tailwind using Global Classes and Relative Styles:

Making Posts editor client friendly

Hi @smontreuil , As I happily found out myself, through doing exactly what @Louis described, yes, any styles you apply to the post content block are indeed reflected perfectly in the admin interface. This allows you to customise each post types editing experience individually to reflect the front-end display. Cwicly global styles are also automatically applied to the editor, so you don’t need to do anything special or extra to make that work. One trick that I recommend that really worked wel…

Making Posts editor client friendly

No problem, once you get your head around it, it becomes a lot easier to follow. When you set up the Relative Style you need to add the rule that targets the p tag. First click on the Rules button for the Relative style: [Relative Styles Inspector Panel] Then you can configure the rule to target the p tag: [Relative Style Rules]

Please see this tip to do this with Tailwind using Shells and Arbitrary Variants:

Styling post content blocks and third party blocks with Tailwind

As many people are now utilising the Tailwind capabilities of Cwicly, one requirement that we all have is to be able to style blocks that we can’t directly control from our templates (such as blocks within Post Content and third-party blocks). Fortunately, Cwicly + Tailwind has you covered. In Tailwind, we are provided with a key way of constructing dynamic classes that can be applied to Cwicly blocks and used to target child selectors, similarly to how relative styles work in Cwicly - these a…