diff --git a/CHANGELOG.md b/CHANGELOG.md
index b90590a58a3d67aa6a7ad000e9bffb54be80f206..fde49f7424eb159d4551457a5df199434131285f 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,3 +1,7 @@
+# 0.2.2
+
+* add Known as an application
+
 # 0.2.1
 
 * draft instructions for how to add an application (whether server-wide or per-user)
diff --git a/doc/deploying-a-server.md b/doc/deploying-a-server.md
index fa9bedcbaf0e3b5476af9b68b8fcc68d7bb7583e..0361108114abca9b9b1de8995b60674357f9512d 100644
--- a/doc/deploying-a-server.md
+++ b/doc/deploying-a-server.md
@@ -38,7 +38,7 @@ Make sure you read [getting started](getting-started-as-a-hoster.md) first.
   * Rewrite the haproxy configuration
   * (Re)start haproxy
 
-* If the domain runs wordpress, then:
+* If the domain runs wordpress (and similarly if it runs Known), then:
   * the git clone from backup will fail because of [issue 46](https://github.com/indiehosters/indiehosters/issues/46), so make sure to follow the workaround steps from there.
   * initial wordpress setup will be impossible with the redirect because of [Dockerfiles issue 39](https://github.com/indiehosters/dockerfiles/issues/39), so make sure to follow the workaround steps from there.
   * Indiewebifying the WordPress instance is still a manual process, so make sure you know the user's preferred username (you can use this for the SiteName as well), and preferred language.
@@ -60,7 +60,7 @@ Make sure you read [getting started](getting-started-as-a-hoster.md) first.
         in real time, immediately when you click 'verify' in the StartSSL UI. If they forward the email the next day, then the token
         will already have expired.
     * If no, register it (at Namecheap or elsewhere).
-  * Decide which image to run as the user's main website software (in version 0.2, 'static', 'static-git', and 'wordpress' are supported)
+  * Decide which image to run as the user's main website software (in version 0.2.2, 'static', 'static-git', 'wordpress', and 'known' are supported)
   * For the 'wordpress' image, all you need is the TLS certificate. Use the 'static-git' image if you already have some static
     content that should go on there, and which you can put in a public git repository somewhere.
   * Unless you already have a TLS certificate for example.com, get one