anchor.diff:  
   Twixt is available under the terms of the Apache Sofware License 2.0.
   
  -Twixt is downloadable from the https://clojars.org/io.aviso/twixt[Clojars Repository].
  +Twixt is available from the Clojars artifact repository as `io.aviso:twixt`.
  +Follow [these instructions](https://clojars.org/io.aviso/twixt) to configure the dependency in your build tool.
   
   http://howardlewisship.com/io.aviso/twixt/[API Documentation]
   
  -=== Usage
  +== Usage
   
   By default, Twixt serves resources located on the classpath, in the +META-INF/assets/+ folder.
   The contents of this folder is accessible via the URL +/assets/+.
  
positive.code: For example, the asset stored as +META-INF/assets/blueant/cla.html+ can be accessed as +/blueant/cla.html+, and will be sent a redirect
  to +/assets/123abc/blueant/cla.html+.
  
  === Configuring Twixt
  
  Twixt's configuration is used to determine where to locate asset resources on the classpath, 
  and what folder to serve them under. It also maps file name extensions to MIME types, and
  
negative.code: The +:compressable+ key identifies which content types are compressable; note the use of the +/*+ suffix to indicate
  that all text content types are compressable.
  
  == Caching
  
  It is desirable to have Twixt be able to serve-up files quickly, especially in production.
  However, that is counter-balanced by the need to ensure the *correct* content is served.
  
  === Development Mode
  
  Twixt will cache the results of compilations to the file system; the cache persists between executions.
  This means that on restart, the application will normally start right up, since the compiled files
  will be accessed from the file system cache.
  
  Whenever a source file changes, the corresponding compiled file is rebuilt (and then the file system cache is updated).
  This is great for development, as you will frequently be changing your source files.
  
  Twixt doesn't bother to cache the GZip compressed versions of assets to the file system; it is relatively quick
  to rebuild the compressed byte stream. There's an in-memory cache of the compressed assets, but each request includes
  checks to see if the compiled output itself must be updated.
  
  You may need to manually clear out the file system cache after upgrading to a new version of Twixt, or any other
  configuration change that can affect the compiled output.
  
  === Production Mode
  
  In production mode, Twixt starts from a clean slate; it does not use a file system cache. However, all assets
  are cached in memory; Twixt also caches the compressed versions of assets, to save the cost of repeatedly compressing
  them on the fly.
  
  In production mode, there are no checks to see if the in-memory cache is valid; if a source file is changed, it is assumed
  that the entire application will be re-deployed and re-started.
  
  == Future Plans
  
  The goal is to achieve at least parity with Apache Tapestry, plus some additional features specific to Clojure. This means:
  
  