From 4eb1c37d624620145e715f8219a134ee6d9efc4f Mon Sep 17 00:00:00 2001 From: "Jake Bayliss [SSW]" <32888060+jakebayliss@users.noreply.github.com> Date: Mon, 30 Mar 2026 14:42:06 +1100 Subject: [PATCH 1/2] TinaCMS content update Co-authored-by: Jake Bayliss [SSW] --- .../rule.mdx | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/public/uploads/rules/link-emails-to-the-rule-or-template-they-follow/rule.mdx b/public/uploads/rules/link-emails-to-the-rule-or-template-they-follow/rule.mdx index e3a60e99fdf..ea32b24b774 100644 --- a/public/uploads/rules/link-emails-to-the-rule-or-template-they-follow/rule.mdx +++ b/public/uploads/rules/link-emails-to-the-rule-or-template-they-follow/rule.mdx @@ -20,7 +20,7 @@ seoDescription: Do you link emails to the rule or template they follow? created: 2012-03-20T15:13:20.000Z createdBy: Griffen Edge createdByEmail: GriffenEdge@ssw.com.au -lastUpdated: 2026-03-29T22:58:21.314Z +lastUpdated: 2026-03-30T03:39:50.436Z lastUpdatedBy: 'Jake Bayliss [SSW]' lastUpdatedByEmail: jakebayliss@ssw.com.au archivedreason: null @@ -41,7 +41,7 @@ It also saves time if another employee needs to send one of these out later, as figure="" /> -In order for other people to recognize emails following **rules** and **standards**, it's a good idea to include something like "**\**" at the end of your email. +In order for other people to recognize emails following **rules** and **standards**, it's a good idea to include something like "**\**" at the end of your email. Even when the rule or standard doesn't include an actual email template, but you want to empathize you are following it, it is still valid to include that link at the bottom, so the other person can get easily get more information. @@ -59,7 +59,9 @@ Even when the rule or standard doesn't include an actual email template, but you Need an answer on this ASAP, please - <This email was sent as per [Do you know how to follow up an unanswered email?](/do-you-know-how-to-follow-up-an-unanswered-email)> + \ + + \ ... } From 790e7f7b5c52e58d14dc966b10c4e570e35451bd Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Mon, 30 Mar 2026 03:43:07 +0000 Subject: [PATCH 2/2] chore: auto-fix MDX issues --- .../rule.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/public/uploads/rules/link-emails-to-the-rule-or-template-they-follow/rule.mdx b/public/uploads/rules/link-emails-to-the-rule-or-template-they-follow/rule.mdx index ea32b24b774..02f287548bf 100644 --- a/public/uploads/rules/link-emails-to-the-rule-or-template-they-follow/rule.mdx +++ b/public/uploads/rules/link-emails-to-the-rule-or-template-they-follow/rule.mdx @@ -41,7 +41,7 @@ It also saves time if another employee needs to send one of these out later, as figure="" /> -In order for other people to recognize emails following **rules** and **standards**, it's a good idea to include something like "**\**" at the end of your email. +In order for other people to recognize emails following **rules** and **standards**, it's a good idea to include something like "**\**" at the end of your email. Even when the rule or standard doesn't include an actual email template, but you want to empathize you are following it, it is still valid to include that link at the bottom, so the other person can get easily get more information. @@ -59,9 +59,9 @@ Even when the rule or standard doesn't include an actual email template, but you Need an answer on this ASAP, please - \ + <This email was sent as per [Do you know how to follow up an unanswered email?](/do-you-know-how-to-follow-up-an-unanswered-email)> - \ + <This email was sent as per {{ LINK }}> ... }