mirror of https://github.com/zulip/zulip.git
portico: Remove mystery hunt landing page.
This was written by Rishi for a very brief purpose a few years ago, and it doesn't serve much purpose now other than to be a place we update in code sweeps.
This commit is contained in:
parent
71078adc50
commit
95be7dcbab
|
@ -1,34 +0,0 @@
|
|||
{% extends "zerver/portico.html" %}
|
||||
{% set entrypoint = "landing-page" %}
|
||||
|
||||
{% block title %}
|
||||
<title>Zephyr reloaded</title>
|
||||
{% endblock %}
|
||||
|
||||
{% block customhead %}
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
{% endblock %}
|
||||
|
||||
{% block portico_content %}
|
||||
|
||||
{% include 'zerver/landing_nav.html' %}
|
||||
|
||||
<div class="portico-landing why-page">
|
||||
<div class="hero bg-pycon mit">
|
||||
<div class="bg-dimmer"></div>
|
||||
<div class="content">
|
||||
<h1 class="center">The best chat for mystery hunt.</h1>
|
||||
<p></p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="main">
|
||||
<div class="padded-content">
|
||||
<div class="inner-content markdown">
|
||||
{{ render_markdown_path('zerver/for/mystery-hunt.md') }}
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
{% endblock %}
|
|
@ -1,60 +0,0 @@
|
|||
Zulip was started in 2012 by four SIPB alums. We think it’s the best team
|
||||
chat tool for mystery hunt teams.
|
||||
|
||||
**How is this different from Slack?**
|
||||
|
||||
In Slack, IRC, and nearly every other team chat application, users subscribe
|
||||
to chat rooms (“channels”), and get all the messages sent to each channel in
|
||||
a chronological dump. The model is largely designed to support real-time
|
||||
conversation, where it’s easy to participate if you’re online, but not easy
|
||||
to come back a few hours later and reply to a conversation that started
|
||||
while you were gone.
|
||||
|
||||
In Zulip, there is an additional layer of organization in each channel:
|
||||
messages have topics (like “puzzle: duck konundrum”), so it is easy to
|
||||
follow conversational threads. It also makes it easy for someone to come
|
||||
back after 8 hours (okay, 4 hours) of sleep, catch up on the state of
|
||||
various puzzles, and answer questions even if a question was asked many
|
||||
hours ago.
|
||||
|
||||
**You have to write a topic for every message you send? Sounds like a bit much…**
|
||||
|
||||
Nope! Just the first person writing a message to a given topic has to write
|
||||
it out. Replies to that message are automatically grouped in the way you’d
|
||||
expect. Sending a message in Zulip feels just as lightweight as sending a
|
||||
message in SMS, Google Hangouts, or Slack.
|
||||
|
||||
**Is it free?**
|
||||
|
||||
Yes! We provide free hosting for all MIT mystery hunt teams, student groups,
|
||||
and research groups.
|
||||
|
||||
Besides being easy on the wallet, Zulip is also free (open source)
|
||||
software. We make it easy to export your data from [Zulip
|
||||
Cloud](https://zulip.com) and import it into a self-hosted
|
||||
installation.
|
||||
|
||||
**Can I integrate Zulip with my current puzzlehunting software?**
|
||||
|
||||
Yup. Zulip has a well thought out [API](/api/), and
|
||||
it’s easy to write bots that send things into or out of Zulip.
|
||||
|
||||
**Where can I test it out?**
|
||||
|
||||
[Click here](https://zulip.com/new) to create an organization; it
|
||||
only takes only about 30 seconds. If you decide to continue using it, just email
|
||||
support@zulip.com to tell us you’re a mystery hunt team.
|
||||
|
||||
**Where do I go for further information?**
|
||||
|
||||
Come find us on the [Zulip community chat](https://chat.zulip.org). Feel
|
||||
free to post in
|
||||
[#mystery hunt](https://chat.zulip.org/#narrow/stream/mystery.20hunt) or
|
||||
anywhere else that seems appropriate.
|
||||
|
||||
**Help! I’m trapped in a mystery hunt puzzle.**
|
||||
|
||||
This is not a puzzle! But feel free take a look at
|
||||
[Zulip for companies](/for/companies),
|
||||
[Zulip for working groups](/for/working-groups-and-communities), or
|
||||
[Zulip for open source projects](/for/open-source).
|
|
@ -77,6 +77,6 @@ class PorticoDocumentationSpider(BaseDocumentationSpider):
|
|||
'http://localhost:9981/for/open-source',
|
||||
'http://localhost:9981/for/companies',
|
||||
'http://localhost:9981/for/working-groups-and-communities',
|
||||
'http://localhost:9981/for/mystery-hunt',
|
||||
'http://localhost:9981/for/research',
|
||||
'http://localhost:9981/security']
|
||||
deny_domains: List[str] = []
|
||||
|
|
|
@ -137,7 +137,6 @@ class DocPageTest(ZulipTestCase):
|
|||
self._test('/for/research/', 'for researchers')
|
||||
self._test('/for/companies/', 'in a company')
|
||||
self._test('/for/working-groups-and-communities/', 'standards bodies')
|
||||
self._test('/for/mystery-hunt/', 'four SIPB alums')
|
||||
self._test('/security/', 'TLS encryption')
|
||||
self._test('/atlassian/', 'HipChat')
|
||||
self._test('/devlogin/', 'Normal users', landing_page=False)
|
||||
|
|
|
@ -570,8 +570,6 @@ i18n_urls = [
|
|||
{'template_name': 'zerver/for-companies.html'}),
|
||||
url(r'^for/working-groups-and-communities/$', zerver.views.portico.landing_view,
|
||||
{'template_name': 'zerver/for-working-groups-and-communities.html'}),
|
||||
url(r'^for/mystery-hunt/$', zerver.views.portico.landing_view,
|
||||
{'template_name': 'zerver/for-mystery-hunt.html'}),
|
||||
url(r'^security/$', zerver.views.portico.landing_view, {'template_name': 'zerver/security.html'}),
|
||||
url(r'^atlassian/$', zerver.views.portico.landing_view, {'template_name': 'zerver/atlassian.html'}),
|
||||
|
||||
|
|
Loading…
Reference in New Issue