Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/templates/zerver/emails/followup/day2.html

44 lines
1.8 KiB
HTML
Raw Normal View History

Queue the day 1 and day 2 Zulip followup emails Handled by the queue processor for signups. Added a management command that accomplishes the same task, in case it's needed for manually added users, or in case we goof and need to remove queued emails for a given user. This addresses Trac #1807 (imported from commit 6727b82a07fa6a3ea3d827860c9e60fd0602297a)
2013-10-07 17:36:38 +02:00
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Zulip</title>
</head>
<body>
<table width="80%" style="align:center; max-width:800px" align="center">
<tr><td>
i18n: Title attribute should be translatable.
2016-12-15 10:11:05 +01:00
<a href="{{ realm_uri }}/"><img style="max-height:75px; height:75px;" height="75px" alt="Zulip" title="{{ _('Zulip') }}" src="{{ realm_uri }}/static/images/landing-page/zulip-header.png" /></a>
Queue the day 1 and day 2 Zulip followup emails Handled by the queue processor for signups. Added a management command that accomplishes the same task, in case it's needed for manually added users, or in case we goof and need to remove queued emails for a given user. This addresses Trac #1807 (imported from commit 6727b82a07fa6a3ea3d827860c9e60fd0602297a)
2013-10-07 17:36:38 +02:00
day2 email: Try to make clear that this is the last one. (imported from commit 953d491a7c5b6717178c85aed4a96e08a8e61e61)
2013-11-07 19:20:34 +01:00
<h3 style="font-family:Arial; font-size:30px; margin: 5px 0px; color:#555">one last thing</h3>
Queue the day 1 and day 2 Zulip followup emails Handled by the queue processor for signups. Added a management command that accomplishes the same task, in case it's needed for manually added users, or in case we goof and need to remove queued emails for a given user. This addresses Trac #1807 (imported from commit 6727b82a07fa6a3ea3d827860c9e60fd0602297a)
2013-10-07 17:36:38 +02:00
</td></tr>
<tr><td style="font-size:16px; font-family:Helvetica;">
Remove full names from our day1 and day2 emails. The weird formality of using your complete name I think feels even spammier than saying nothing. (imported from commit b2326de91866fa3c13c2023723f64d1beadf435e)
2013-11-07 16:12:40 +01:00
<p>Hey,</p>
Queue the day 1 and day 2 Zulip followup emails Handled by the queue processor for signups. Added a management command that accomplishes the same task, in case it's needed for manually added users, or in case we goof and need to remove queued emails for a given user. This addresses Trac #1807 (imported from commit 6727b82a07fa6a3ea3d827860c9e60fd0602297a)
2013-10-07 17:36:38 +02:00
Revise day1/day2 emails. (imported from commit dc5e78cccb22b024be46b3066d44f09ea1b53345)
2013-11-27 06:18:54 +01:00
<p>I wanted to share one last thing with you: a few tips about topics, since mastering topics is a key part of being a Zulip power user.</p>
<p>Topics are like email subject lines. The big difference, though, is that they're really short and lightweight. One or two words will do it. Don't overthink 'em&mdash;you can always edit the message later!</p>
Queue the day 1 and day 2 Zulip followup emails Handled by the queue processor for signups. Added a management command that accomplishes the same task, in case it's needed for manually added users, or in case we goof and need to remove queued emails for a given user. This addresses Trac #1807 (imported from commit 6727b82a07fa6a3ea3d827860c9e60fd0602297a)
2013-10-07 17:36:38 +02:00
<ul>
Revise day1/day2 emails. (imported from commit dc5e78cccb22b024be46b3066d44f09ea1b53345)
2013-11-27 06:18:54 +01:00
<li>Good topics: screenshot, Bug 345, lunch</li>
day2 email: Soften advice against using long topics. In response to feedback that joining (and sending a first message to) a new chat platform/org is already intimidating enough, and "Not Recommended" gets the point across in a gentler way.
2017-01-10 21:53:59 +01:00
<li>Not recommended: "What do people think of this new screenshot?", "I'm looking at Bug 345", "Where should we go to lunch?"</li>
Queue the day 1 and day 2 Zulip followup emails Handled by the queue processor for signups. Added a management command that accomplishes the same task, in case it's needed for manually added users, or in case we goof and need to remove queued emails for a given user. This addresses Trac #1807 (imported from commit 6727b82a07fa6a3ea3d827860c9e60fd0602297a)
2013-10-07 17:36:38 +02:00
</ul>
Typo fix in day2 email. (imported from commit bf36702c84ba545a64bf5c6531ce30fc23ef6ac7)
2014-01-30 07:44:17 +01:00
<p>Why bother with topics? Well, two reasons: it makes conversations clearer (imagine if email didn't have them!), and it lets you more efficiently catch up on what's happened while you're away&mdash;read the topics that are relevant to you, and ignore the ones that aren't!</p>
Revise day1/day2 emails. (imported from commit dc5e78cccb22b024be46b3066d44f09ea1b53345)
2013-11-27 06:18:54 +01:00
templates: Use realm_uri and server_uri settings for server URL. The policy here is essentially: * Pages on the central server (documentation, etc.) are server_uri. * Pages associated with a user's realm server (anything logged-in, plus things like their login page) are realm_uri.
2016-08-13 00:39:22 +02:00
<p><a href="{{ realm_uri }}">Take it for a spin now.</a></p>
Queue the day 1 and day 2 Zulip followup emails Handled by the queue processor for signups. Added a management command that accomplishes the same task, in case it's needed for manually added users, or in case we goof and need to remove queued emails for a given user. This addresses Trac #1807 (imported from commit 6727b82a07fa6a3ea3d827860c9e60fd0602297a)
2013-10-07 17:36:38 +02:00
Revise day1/day2 emails. (imported from commit dc5e78cccb22b024be46b3066d44f09ea1b53345)
2013-11-27 06:18:54 +01:00
<p>Thanks,<br />Zulip</p>
Queue the day 1 and day 2 Zulip followup emails Handled by the queue processor for signups. Added a management command that accomplishes the same task, in case it's needed for manually added users, or in case we goof and need to remove queued emails for a given user. This addresses Trac #1807 (imported from commit 6727b82a07fa6a3ea3d827860c9e60fd0602297a)
2013-10-07 17:36:38 +02:00
</td></tr>
</table>
Add one-click unsubscribe links to day 1 and day 2 emails. (imported from commit 9396f96365430baf894c708f9eaea642fc648435)
2013-11-26 00:08:17 +01:00
<p>
templates: Use realm_uri and server_uri settings for server URL. The policy here is essentially: * Pages on the central server (documentation, etc.) are server_uri. * Pages associated with a user's realm server (anything logged-in, plus things like their login page) are realm_uri.
2016-08-13 00:39:22 +02:00
<a href="{{ realm_uri }}/#settings">Manage email preferences</a> |
Add one-click unsubscribe links to day 1 and day 2 emails. (imported from commit 9396f96365430baf894c708f9eaea642fc648435)
2013-11-26 00:08:17 +01:00
<a href="{{ unsubscribe_link }}">Unsubscribe from welcome emails</a>
</p>
Queue the day 1 and day 2 Zulip followup emails Handled by the queue processor for signups. Added a management command that accomplishes the same task, in case it's needed for manually added users, or in case we goof and need to remove queued emails for a given user. This addresses Trac #1807 (imported from commit 6727b82a07fa6a3ea3d827860c9e60fd0602297a)
2013-10-07 17:36:38 +02:00
</body>
</html>