Email templating improvement suggestions

[diabWH3]

Emailed back and forth with Opee about this, but figured it'd be easier to track in the GitHub system. Some suggestions for email templates to help the End User stay organized by having a more consistent appearance and clearer kennel/run # designations.

Some basic concepts:

• All reports to have a consistent subject prefix to help with auto email filtering/organizing.
• Run count numbers, when appropriate, to be included to eliminate auto-grouping of reports from different events by email clients
• Simplify email subjects to reduce length for readability
• Items in { } are application variables...some of these may be optional (i.e. Event Names...not every trail/kennel puts names on their events and only advertises trail numbers)
• Prefix [Harrier Central] is meant to include the brackets

Suggested Subject Templates:

• Run Count Report, Kennel-Specific: [Harrier Central] Run Count Report - {kennel_name}
• Run Count Report, All-Time: [Harrier Central] Run Count Report - All Kennels
• Run Stats Report: [Harrier Central] Run Stats Report - {kennel_name}
• Run Info: [Harrier Central] Run Info - {kennel_name} #{run_number} ({event_name})
• Payment Report: [Harrier Central] Payment Report - {kennel_name} #{run_number} ({event_name})

[James-A-White]

Thanks for putting it in GitHub... my email is a disaster because of all of the non-Harrier Central work I do. GitHub is the best way to make sure I don't miss something!