2014-02-09: More info in the readme.

More info in the readme.

diff --git a/README.txt b/README.txt
--- a/README.txt
+++ b/README.txt
@@ -2,17 +2,35 @@ hg site: Create and/or upload a static c
 
 You can get it via `hg clone http://draketo.de/proj/hgsite/`
 
+With hg site you can say goodbye to vendor lock-in.
+
 The goal of hg site is sharing code over commodity servers which only
 offer FTP access and statically served files, while providing the same
 information as hg serve and full solutions like bitbucket and
-gitorious (naturally without the interactivity).
+gitorious (naturally without the interactivity, but you can always
+clone the repo to interact).
 
 Thanks to the static http support of Mercurial, the clone and browse
 URLs are the same, so you can look at the site with your webbrowser or
 clone the repository with Mercurial using the same URL.
 
-On upload, only changed files are uploaded, based on the time they
-were last modified, so uploads can be reasonably fast.
+The fork detection allows tieing multiple platforms together: It
+tracks repositories from any source for which Mercurial can calculate
+incoming and outgoing changes. And since the bugtracking happens via
+the b-extension, your bugtracking follows your code wherever you go.
+
+Features:
+
+- shows the history, branches, tags and bookmarks
+- shows bugs tracked via the [b-extension][]
+- shows the readme
+- shows forks defined as paths in `.hg/hgrc` - from any source hg supports
+- uploads only  changed files (based on the time they
+were last modified), so uploads can be reasonably fast.
+- Supports FTP and FTPs. Use the latter if you can (just use URLs starting with `ftps://`)
+- static site (no vulnerabilities, little dependencies, high performance)
+
+[b-extension]: http://mercurial.selenic.com/wiki/bExtension "Distributed Bug Tracking: Get bugs resolved, not organized"
 
 Install: