commit 600d2e5f99b2708bad5a7ee18f1e7ddfa44d29e7
parent 1d02f7d3f3d4af68713c552758eee10ce7222a0e
Author: Jonathan Lassoff <jof@thejof.com>
Date: Sun, 28 Apr 2013 13:26:03 -0700
Update content
Diffstat:
2 files changed, 58 insertions(+), 0 deletions(-)
diff --git a/history/index.md b/history/index.md
@@ -0,0 +1,12 @@
+---
+layout: default
+---
+
+## # History
+Originally, sup was a project maintained by William Morgan at [http://sup.rubyforge.org/](http://sup.rubyforge.org/).
+
+[git was in Gitorious](http://gitorious.org/sup)
+
+There was also a nice wiki on Rubyforge, but it has since fallen prey to mischievous robots.
+
+<img src="/images/wiki_bot_death.png" />
diff --git a/index.md b/index.md
@@ -0,0 +1,46 @@
+---
+layout: default
+---
+## # [sup](https://github.com/sup-heliotrope/sup/)
+[Sup](https://github.com/sup-heliotrope/sup/) is a console-based email client for people with a lot of email.
+
+It presents an interface of a list of threads, which are each hierarchical collections email messages.
+Threads can have multiple tags applied to them.
+It supports a very fast full-text search, automatic contact-list management, custom code insertion via a Ruby hook system, and more.
+If you're the type of person who treats email as an extension of your long-term memory, Sup is for you.
+
+## # Features
+ * Handle massive amounts of email.
+ * Fast, local full-text index of messages.
+ * Mix email from different sources: mbox files and maildirs.
+ * Instantaneously search over your entire email collection. Search over body text, or use a query language to combine search predicates in any way.
+ * Handle multiple accounts. Replying to email sent to a particular account will use the correct SMTP server, signature, and from address.
+ * Add custom code to handle certain types of messages or to handle certain types of text within messages.
+ * Organize email with user-defined labels, automatically track recent contacts, and much more!
+
+## # Sub-projects
+### sup
+sup is the original curses email client, full-text index, and hook system.
+
+### [Heliotrope](https://github.com/sup-heliotrope/heliotrope)
+[Heliotrope](https://github.com/sup-heliotrope/heliotrope) is an architectural
+shift from sup that maintains many of the same concepts, but separates out a
+server and client.
+Contrast to what is done in sup, where one large client installation has all
+the mail documents and indexes locally, Heliotrope provides a server-side
+service that indexes mail.
+
+In this way, remote clients can connect up and interact with their mail stores
+in a sup-like way, while keeping the mobile install slim.
+This is a lifesaver when switching from machine to machine.
+
+### [Turnsole](https://github.com/sup-heliotrope/turnsole)
+[Turnsole](https://github.com/sup-heliotrope/turnsole) is an example client
+that would connect to Heliotrope and interact with mail.
+
+### Resources
+ * [wiki](https://github.com/sup-heliotrope/sup/wiki)
+ * [Issues](https://github.com/sup-heliotrope/sup/issues)
+
+### Authors and Contributors
+Sup is brought to you by [a cast of hackers.](https://github.com/sup-heliotrope/sup/blob/master/CONTRIBUTORS)