You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Notify gives specific instructions for users to size their logos when they upload them, but when they follow them, the logo ends up larger than expected.
Note: If we fix this, we need to think about how to handle existing logos. We could either go back and fix them all, or perhaps only re-size images properly going forward.
If we can’t change how logos are displayed, we could instead change our instructions.
Instructions:
Your logo must be compatible with GC Notify. Check logo is:
In PNG image format
Exactly 108 pixels tall
Maximum 600 pixels wide
Result:
However, it should look like this: SEV-4 Low
To Reproduce
Steps to reproduce the behavior:
Upload a custom logo and follow the sizing instructions
Logo is larger than expected
Expected behavior
Logo should be the same size as image uploaded
Impact
Impact on Notify users:
This could confuse users, reduce their trust in the product
Impact on Recipients:
If not corrected, the emails can look unprofessional, which could reduce/erode trust
Impact on Notify team:
Causes extra work to handle support cases, fix logos, etc.
The text was updated successfully, but these errors were encountered:
Describe the bug
Notify gives specific instructions for users to size their logos when they upload them, but when they follow them, the logo ends up larger than expected.
Note: If we fix this, we need to think about how to handle existing logos. We could either go back and fix them all, or perhaps only re-size images properly going forward.
If we can’t change how logos are displayed, we could instead change our instructions.
Instructions:
Result:
However, it should look like this:
SEV-4 Low
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Impact
Impact on Notify users:
Impact on Recipients:
Impact on Notify team:
The text was updated successfully, but these errors were encountered: