Skip to content

🐛 Bug - Email examples render as a single paragraph in TinaCMS rules #2551

@ssw-yakshaver

Description

@ssw-yakshaver

Requested by: @KostaMadorsky via YakShaver.ai 🦬
cc: @jakebayliss, @adamcogan, @KostaMadorsky, @Marxoz, @PothieuG, @Freego1783

Hi Team!

  🟥  Watch the video (4 min 1 sec)

  Url from screen share: https://www.ssw.com.au/rules/reply-done

Pain

Email examples in SSW Rules are rendering incorrectly when viewed on the live site. In the rule “Reply Done – Delete Original Email”, the Good and Bad examples appear as a single paragraph, making it unclear where the original email ends and the reply begins. This is caused by Markdown being rendered as one line unless there is an empty line between sections. Although the content may appear correct in the TinaCMS editor after manual spacing fixes, the deployed rules page can still render incorrectly. The issue may affect multiple rules, not just this one, so a broader audit and fix is required.

Acceptance Criteria

  1. The Good and Bad email examples in the rule "Reply Done – Delete Original Email" render with clear paragraph separation on the live rules page.
  2. Markdown line breaks and empty lines are correctly respected in deployed output, not just in the TinaCMS editor preview.
  3. Extra or unexpected spaces are not introduced in the rendered email examples compared to the editor content.
  4. Other rules are reviewed to identify the same Markdown rendering issue.
  5. All identified affected rules are updated so their email examples render correctly.
  6. Changes are verified in a staging environment before being released to production.

Reproduce Steps

  1. Open the rule "Reply Done – Delete Original Email" on the live SSW Rules site.
  2. Navigate to the Good or Bad email example section.
  3. Observe that the original email and the reply appear on the same line or as one paragraph.
  4. Compare the rendering with the expected formatting (separate paragraphs with clear boundaries).

Screenshot

Screenshot
Figure: Email reply example renders as a single line, obscuring separation between original request and reply

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions