diff --git a/humbug/urls.py b/humbug/urls.py
index ff389461b3..29abea31c5 100644
--- a/humbug/urls.py
+++ b/humbug/urls.py
@@ -36,6 +36,9 @@ urlpatterns = patterns('',
     url(r'^terms$',   'django.views.generic.simple.direct_to_template', {'template': 'zephyr/terms.html'}),
     url(r'^privacy$', 'django.views.generic.simple.direct_to_template', {'template': 'zephyr/privacy.html'}),
 
+    # New user "tutorial"
+    url(r'^new-user$', 'django.views.generic.simple.direct_to_template', {'template': 'zephyr/new-user.html'}),
+
     # These are json format views used by the web client.  They require a logged in browser.
     url(r'^json/update_pointer$',           'zephyr.views.json_update_pointer'),
     url(r'^json/get_updates$',              'zephyr.views.json_get_updates'),
diff --git a/templates/zephyr/new-user.html b/templates/zephyr/new-user.html
new file mode 100644
index 0000000000..f906d5f942
--- /dev/null
+++ b/templates/zephyr/new-user.html
@@ -0,0 +1,49 @@
+{% extends "zephyr/portico.html" %}
+
+{# New user tutorial standin. #}
+
+{% block portico_content %}
+<div class="row-fluid">
+  <div class="span8" style="font-size: 110%">
+    <h2>Hello, and welcome!</h2>
+
+    <p>Humbug is a little different than some systems you may have already
+      used.<br />
+      Here's what you need to know:</p>
+
+    <ul>
+      <li>Every message has a <b>stream</b> and a <b>subject</b></li>
+      <li>A stream is kind of like a mailing list -- it represents a group of people -- and anyone can <i>subscribe</i> to a stream and start getting traffic there</li>
+      <li>A subject, on the other hand, is what the message is <i>actually about</i></li>
+      <li>(You can, of course, send private messages.)</li>
+      <li>All of these are displayed simultaneously, in an interleaved way, chronologically</li>
+      <li>Time flows down, and the page does not automatically scroll</li>
+    </ul>
+
+    <p>This means we can have a conversation about git, jQuery,
+      fundraising, where to go to lunch, and a message from your commit bot
+      all simultaneously--without it getting unmanageable.</p>
+
+    <p>Let's take a look:
+    <img src="/static/public/images/streams-example.png">
+    </p>
+
+    <p>Here, we have three conversations occurring simultaneously:</p>
+    <ul>
+      <li>One on stream "humbug" with subject "Lunch", about where to go to lunch</li>
+      <li>One on stream "humbug" with subject "Humbug testers", about early beta testers</li>
+      <li>One automated notification on stream "commits", about a commit made to the repository</li>
+    </ul>
+
+    <h3>Some things to know</h3>
+    <ul>
+      <li>"Enter" will start a reply to the message with the blue line by it (in the example above, the one with subject "Humbug testers")</li>
+      <li>When you send the reply, it will appear at the very bottom of the stream (not directly below the message you reply to)</li>
+      <li>After you're done typing a reply, you can send it with Tab followed by Enter (just pressing Enter will add a new line to the message)</li>
+    </ul>
+
+    <h3>That's it!</h3>
+    <a class="btn btn-primary btn-large" href="{% url zephyr.views.accounts_home %}">Create your account now</a>
+    <br /><br /><br /><br />
+  </div>
+{% endblock %}
diff --git a/zephyr/static-access-control/public/images/streams-example.png b/zephyr/static-access-control/public/images/streams-example.png
new file mode 100644
index 0000000000..c0a5394b3d
Binary files /dev/null and b/zephyr/static-access-control/public/images/streams-example.png differ