From 5ac539137a8e63471a0d714b1a3eee81a5b2f664 Mon Sep 17 00:00:00 2001
From: Luca Matei Pintilie <luca@lucamatei.com>
Date: Sun, 26 Jul 2026 15:57:31 +0200
Subject: [PATCH 1/3] Fix various links

---
 Makefile                                      |   1 +
 blogsource/content/post/distrobox.md          |   2 +
 ...-to-run-profanity-instances-within-tmux.md |   2 +-
 blogsource/content/post/lmc.md                |   7 +-
 blogsource/content/post/new-mailing-list.md   |   4 +-
 blogsource/content/post/omemo.md              |   2 +-
 .../content/post/profanity-on-pinephone.md    |   4 +-
 blogsource/content/post/release-0100.md       |   6 +-
 blogsource/content/post/release-080.md        |   2 +-
 blogsource/content/post/release-090.md        |   4 +-
 css/profanity.css                             |  13 +-
 guide/0100/install.html                       |   2 +-
 guide/0100/omemo.html                         |  18 +-
 guide/0100/otr.html                           |  32 +--
 guide/0100/pgp.html                           |  22 +-
 guide/0100/rooms.html                         |   4 +-
 guide/0110/install.html                       |   2 +-
 guide/0110/omemo.html                         | 211 ++++++++++++++++++
 guide/0110/otr.html                           |  32 +--
 guide/0110/pgp.html                           |  22 +-
 guide/0110/rooms.html                         |   4 +-
 guide/0111/install.html                       |   2 +-
 guide/0111/omemo.html                         |  18 +-
 guide/0111/otr.html                           |  32 +--
 guide/0111/pgp.html                           |  22 +-
 guide/0111/rooms.html                         |   4 +-
 guide/0120/install.html                       |   2 +-
 guide/0120/omemo.html                         |  18 +-
 guide/0120/otr.html                           |  32 +--
 guide/0120/pgp.html                           |  22 +-
 guide/0120/rooms.html                         |   4 +-
 guide/0130/install.html                       |   2 +-
 guide/0130/omemo.html                         |  18 +-
 guide/0130/otr.html                           |  32 +--
 guide/0130/pgp.html                           |  22 +-
 guide/0130/rooms.html                         |   4 +-
 guide/0131/install.html                       |   2 +-
 guide/0131/omemo.html                         |  18 +-
 guide/0131/otr.html                           |  32 +--
 guide/0131/pgp.html                           |  22 +-
 guide/0131/rooms.html                         |   4 +-
 guide/0140/install.html                       |   2 +-
 guide/0140/omemo.html                         |  18 +-
 guide/0140/otr.html                           |  32 +--
 guide/0140/pgp.html                           |  22 +-
 guide/0140/rooms.html                         |   4 +-
 guide/0150/install.html                       |   2 +-
 guide/0150/latest/install.html                |   2 +-
 guide/0150/latest/omemo.html                  |  18 +-
 guide/0150/latest/otr.html                    |  32 +--
 guide/0150/latest/pgp.html                    |  22 +-
 guide/0150/latest/rooms.html                  |   4 +-
 guide/0150/omemo.html                         |  18 +-
 guide/0150/otr.html                           |  32 +--
 guide/0150/pgp.html                           |  22 +-
 guide/0150/rooms.html                         |   4 +-
 guide/0160/install.html                       |   2 +-
 guide/0160/omemo.html                         |  18 +-
 guide/0160/otr.html                           |  32 +--
 guide/0160/pgp.html                           |  22 +-
 guide/0160/rooms.html                         |   4 +-
 guide/0170/install.html                       |   2 +-
 guide/0170/omemo.html                         |  18 +-
 guide/0170/otr.html                           |  32 +--
 guide/0170/pgp.html                           |  22 +-
 guide/0170/rooms.html                         |   4 +-
 guide/0180/install.html                       |   2 +-
 guide/0180/omemo.html                         |  18 +-
 guide/0180/otr.html                           |  32 +--
 guide/0180/pgp.html                           |  22 +-
 guide/0180/rooms.html                         |   4 +-
 guide/070/install.html                        |   2 +-
 guide/070/omemo.html                          |  18 +-
 guide/070/otr.html                            |  30 +--
 guide/070/pgp.html                            |  22 +-
 guide/070/rooms.html                          |   4 +-
 guide/080/install.html                        |   2 +-
 guide/080/omemo.html                          |  18 +-
 guide/080/otr.html                            |  32 +--
 guide/080/pgp.html                            |  22 +-
 guide/080/rooms.html                          |   4 +-
 guide/090/install.html                        |   2 +-
 guide/090/omemo.html                          |  18 +-
 guide/090/otr.html                            |  32 +--
 guide/090/pgp.html                            |  22 +-
 guide/090/rooms.html                          |   4 +-
 guide/latest/install.html                     |  11 +-
 guide/latest/omemo.html                       |  18 +-
 guide/latest/otr.html                         |  32 +--
 guide/latest/pgp.html                         |  22 +-
 guide/latest/rooms.html                       |   4 +-
 index.md                                      |   4 +-
 pagesource/faq.md                             |   2 +-
 pagesource/helpout.md                         |  18 +-
 pagesource/plugins.md                         |   2 +-
 95 files changed, 858 insertions(+), 663 deletions(-)
 create mode 100644 guide/0110/omemo.html

diff --git a/Makefile b/Makefile
index 8389dbc..f67ce77 100644
--- a/Makefile
+++ b/Makefile
@@ -35,6 +35,7 @@ install:  index.html $(PAGES) themegallery.html $(BLOG_POSTS_OUT) $(BLOG_POST_OU
 	install -m0444 -p -D -t $(PREFIX)/$(BLOG_POST_OUT_TOP_DIR) $(BLOG_POST_OUT_TOP_DIR)/index.html
 	install -m0444 -p -D -t $(PREFIX)/$(BLOG_POST_OUT_DIR) $(BLOG_POST_OUT_DIR)/*.html
 	install -m0444 -p -D -t $(PREFIX)/$(BLOG_POST_OUT_DIR)/img $(BLOG_POST_OUT_DIR)/img/*.png
+	install -m0444 -p -D -t $(PREFIX)/$(BLOG_POST_OUT_DIR)/img $(BLOG_POST_OUT_DIR)/img/*.jpeg
 	install -m0444 -p -D -t $(PREFIX)/$(CONTRIBUTORS_OUT_DIR) $(CONTRIBUTORS_OUT_DIR)/*.html
 	install -m0444 -p -D -t $(PREFIX)/$(CONTRIBUTORS_OUT_DIR)/img $(CONTRIBUTORS_OUT_DIR)/img/*jpg
 	cp -p -r css $(PREFIX)
diff --git a/blogsource/content/post/distrobox.md b/blogsource/content/post/distrobox.md
index 87fccc3..de296a4 100644
--- a/blogsource/content/post/distrobox.md
+++ b/blogsource/content/post/distrobox.md
@@ -40,6 +40,7 @@ profanity-on-tw
 ```
 
 We can now enter this container and install profanity in it via:
+
 ```
 host$ distrobox-enter profanity-on-tw
 Container profanity-on-tw is not running.
@@ -142,6 +143,7 @@ Type `exit` to get out.
 
 # Usage
 Each time you want to start profanity you now have to do enter the container and start it there:
+
 ```
 host$ distrobox-enter profanity-on-tw
 profanity-on-tw$ profanity
diff --git a/blogsource/content/post/how-to-run-profanity-instances-within-tmux.md b/blogsource/content/post/how-to-run-profanity-instances-within-tmux.md
index 38d27a1..48c6627 100644
--- a/blogsource/content/post/how-to-run-profanity-instances-within-tmux.md
+++ b/blogsource/content/post/how-to-run-profanity-instances-within-tmux.md
@@ -1,7 +1,7 @@
 ---
 title: How to run profanity instances within tmux
 date: 2020-03-03T14:49:55+01:00
-authors: debxwoody 
+authors: debxwoody
 ---
 
 If you have more than one XMPP account, you may run one profanity process per
diff --git a/blogsource/content/post/lmc.md b/blogsource/content/post/lmc.md
index 7e1062f..4fc32e3 100644
--- a/blogsource/content/post/lmc.md
+++ b/blogsource/content/post/lmc.md
@@ -1,14 +1,13 @@
 ---
 title: "Last Message Correction"
 date: 2020-02-14T11:34:38+01:00
-authors:
-  - jubalh
+authors: jubalh
 ---
 
-From 10th to 14th February 2020 we had [Hackweek 19](https://hackweek.suse.com/19/projects) at SUSE.
+From 10th to 14th February 2020 we had [Hackweek 19](https://web.archive.org/web/20210728133610/https://hackweek.suse.com/19/projects) at SUSE.
 Part of that time I used to finally implement the long (since 2016!) [sought after](https://github.com/profanity-im/profanity/issues/805) Last Message Correction feature, aka [XEP-0308](https://xmpp.org/extensions/xep-0308.html).
 
-See my [Hackweek project](https://hackweek.suse.com/projects/implement-xep-0308-last-message-correction-in-profanity) and the corresponding [pull request](https://github.com/profanity-im/profanity/pull/1267).
+See my [Hackweek project](https://web.archive.org/web/20210423141452/https://hackweek.suse.com/projects/implement-xep-0308-last-message-correction-in-profanity) and the corresponding [pull request](https://github.com/profanity-im/profanity/pull/1267).
 
 ## Usage
 To enable incoming and outgoing corrections users need to enable it with `/correction on`, see `/help correction` for more details.
diff --git a/blogsource/content/post/new-mailing-list.md b/blogsource/content/post/new-mailing-list.md
index eaf4dd8..951cff1 100644
--- a/blogsource/content/post/new-mailing-list.md
+++ b/blogsource/content/post/new-mailing-list.md
@@ -4,8 +4,8 @@ date: 2020-04-19T22:50:18+02:00
 authors: jubalh
 ---
 
-I would like to announce that thanks to [toogley](https://github.com/toogley) we have a new mailing list.
-You can register on https://lists.notraces.net/mailman/listinfo/profanity
+I would like to announce that thanks to [toogley](https://web.archive.org/web/20210512220718/https://github.com/toogley) we have a new mailing list.
+You can register on [https://lists.notraces.net/mailman/listinfo/profanity](https://web.archive.org/web/20221019152740/https://lists.notraces.net/mailman/listinfo/profanity)
 
 The list is hosted by [datenkollektiv](https://www.datenkollektiv.net/).
 
diff --git a/blogsource/content/post/omemo.md b/blogsource/content/post/omemo.md
index 5c9db70..54fd513 100644
--- a/blogsource/content/post/omemo.md
+++ b/blogsource/content/post/omemo.md
@@ -1,7 +1,7 @@
 ---
 title: OMEMO
 date: 2020-11-27T17:14:07+01:00
-authors: debxwoody 
+authors: debxwoody
 ---
 
 OMEMO with profanity.
diff --git a/blogsource/content/post/profanity-on-pinephone.md b/blogsource/content/post/profanity-on-pinephone.md
index 5e915d9..14885d4 100644
--- a/blogsource/content/post/profanity-on-pinephone.md
+++ b/blogsource/content/post/profanity-on-pinephone.md
@@ -25,7 +25,7 @@ I also decided to check profanity as I use it on my home server and it works per
 
 But, I still had a trouble scrolling the main window in profanity
 
-[video: ppkb keyboard issue](https://kraut.zone/w/6jG9F41Z7nNUZLFdHE43cN)
+[video: ppkb keyboard issue (video unavailable)](https://kraut.zone/w/6jG9F41Z7nNUZLFdHE43cN)
 
 I looked at [profanity keybindings](http://www.profanity.im/keybindings.html) and in the `User Interface Navigation` section I found that I should use `PageUp/PageDown` keys, but looking at [Pinephone wiki](https://wiki.pine64.org/wiki/PinePhone_(Pro)_Keyboard#Keyboard_layout) this keyboard does not have `PageUp/PageDown` keys.
 
@@ -49,7 +49,7 @@ After starting profanity, I was able to scroll window with content using followi
 - `C-j` - scroll up
 - `C-k` - to scroll down 
 
-[video: ppkb keyboard scroll](https://kraut.zone/w/fA2LeeRRmonkHVB5d3NMYe)
+[video: ppkb keyboard scroll (video unavailable)](https://kraut.zone/w/fA2LeeRRmonkHVB5d3NMYe)
 
 Here you can see some photos. 
 
diff --git a/blogsource/content/post/release-0100.md b/blogsource/content/post/release-0100.md
index 4b04229..64d91aa 100644
--- a/blogsource/content/post/release-0100.md
+++ b/blogsource/content/post/release-0100.md
@@ -16,13 +16,13 @@ I also would like to express my gratitude to my sponsors [mdosch](https://github
 This release bumped a few dependencies. Namely: libstrophe/libmesode >= 0.10.0, glib >= 2.62 sqlite >= 3.22 and gtk3 >= 3.24 (or gtk2 >= 2.24.10).
 
 ## Roadmap
-The roadmap for 0.10.0 was announced on our [mailing list](https://lists.notraces.net/pipermail/profanity/2020/000018.html). The goal was mainly cleanupg and fixes.
+The roadmap for 0.10.0 was announced on our [mailing list](https://web.archive.org/web/20201020033248/https://lists.notraces.net/pipermail/profanity/2020/000018.html). The goal was mainly cleanup and fixes.
 
 ## Contributing to Profanity
-To make it easier for newcomers to contribue to Profanity we added a [Contributing](https://github.com/profanity-im/profanity/blob/master/CONTRIBUTING.md) file which has, as we hope, some quite important information on how to get started. And about our workflow.
+To make it easier for newcomers to contribute to Profanity we added a [Contributing](https://github.com/profanity-im/profanity/blob/master/CONTRIBUTING.md) file which has, as we hope, some quite important information on how to get started. And about our workflow.
 
 ## NetBSD
-It is also the first official Proanity release that got NetBSD support.
+It is also the first official Profanity release that got NetBSD support.
 
 ## OMEMO
 You can now sent OMEMO encrypted files via `/sendfile`.
diff --git a/blogsource/content/post/release-080.md b/blogsource/content/post/release-080.md
index 6eda28c..f3f3fc0 100644
--- a/blogsource/content/post/release-080.md
+++ b/blogsource/content/post/release-080.md
@@ -13,7 +13,7 @@ It's released five months after 0.7.0 and has 295 commits since then.
 Also more and more people contribute to Profanity's development. A big thanks to:
 [@paulfariello](https://github.com/paulfariello), [@svensp](https://github.com/svensp), [@aaptel](https://github.com/aaptel), [@aszlig](https://github.com/), [@mdosch](https://github.com/mdosch), [@pasis](https://github.com/pasis), [@mzagozen](https://github.com/mzagozen), [@quite](https://github.com/quite), [@weiss](https://github.com/weiss), [@Misaflo](https://github.com/Misaflo) and [@jubalh](https://github.com/).
 
-![Profanity](/blog/img/profanity-rel-080.jpeg)
+![Profanity](img/profanity-rel-080.jpeg)
 
 ## New features
 We got fingerprint autocompletion for the `/omemo trust` command.      
diff --git a/blogsource/content/post/release-090.md b/blogsource/content/post/release-090.md
index 5a316d3..4d8bd4d 100644
--- a/blogsource/content/post/release-090.md
+++ b/blogsource/content/post/release-090.md
@@ -6,7 +6,7 @@ authors: jubalh
 
 Four months and 350 commits after 0.8.1 we are happy to release [0.9.0](https://github.com/profanity-im/profanity/releases/tag/0.9.0).
 
-7 people contributed code to it: [pasis](https://github.com/pasis), [wstrm](https://github.com/wstrm), [DebXWoody](https://github.com/DebXWoody), [toogley](https://github.com/toogley), [pmaziere](https://github.com/pmaziere), [moppman](https://github.com/moppman) and [jubalh](https://github.com/jubalh).
+7 people contributed code to it: [pasis](https://github.com/pasis), [wstrm](https://github.com/wstrm), [DebXWoody](https://github.com/DebXWoody), [toogley](https://web.archive.org/web/20210512220718/https://github.com/toogley), [pmaziere](https://github.com/pmaziere), [moppman](https://github.com/moppman) and [jubalh](https://github.com/jubalh).
 
 Thanks to everybody who was involved, be it testing, writing documentation, updating the website or whatever you did!
 I also would like to express my gratitude to my sponsors [mdosch](https://github.com/mdosch) and [wstrm](https://github.com/wstrm)!
@@ -31,7 +31,7 @@ Hopefully this is useful for our testers!
 The new `-t` option will let you select a theme right at startup: `/profanity -t bios`.
 This is useful if you run multiple instances of Profanity. Maybe you have multiple accounts and want to visually destinguish between them.
 
-Did you know we have a [blogpost](https://profanity-im.github.io/blog/post/how-to-run-profanity-instances-within-tmux/) that should help you create such a setup with tmux?
+Did you know we have a [blogpost](https://profanity-im.github.io/blog/post/how-to-run-profanity-instances-within-tmux.html) that should help you create such a setup with tmux?
 
 ## Titlebar
 Previously you could choose whether to display the MUC name or MUC title in the titlebar. Now you can choose to do both or neither.
diff --git a/css/profanity.css b/css/profanity.css
index 2d52098..83a5f16 100644
--- a/css/profanity.css
+++ b/css/profanity.css
@@ -716,7 +716,7 @@ article#manual ol,article#manual ul{
     list-style:none
 }
 #Zoomer{
-    background:rgba(0,0,0,.5) url(../images/stripey-dark.png) repeat;
+    background:rgba(0,0,0,.5);
     display:none;
     height:100%;
     margin-left:-1.8em;
@@ -739,17 +739,6 @@ article#manual ol,article#manual ul{
     max-width:100%;
     width:auto
 }
-#Zoomer .control-icon{
-    background:url(../images/close-button.svg);
-    background-size:contain;
-    height:5em;
-    opacity:.8;
-    position:absolute;
-    right:10%;
-    top:2.5em;
-    width:5em;
-    z-index:30
-}
 #Zoomer .control-icon:hover{
     opacity:1
 }
diff --git a/guide/0100/install.html b/guide/0100/install.html
index 07d27f6..8c40788 100644
--- a/guide/0100/install.html
+++ b/guide/0100/install.html
@@ -133,7 +133,7 @@ <h3>Linux/*BSD</h3>
                 </tr>
             </table>
             <p>To add to this list, submit a pull request to the <a
-                    href="https://github.com/boothj5/www_profanity_im/blob/master/install.html" target="_blank">website
+                    href="https://github.com/profanity-im/profanity-im.github.io/" target="_blank">website
                     source</a>, or email the <a href="https://lists.notraces.net/mailman/listinfo/profanity"
                     target="_blank">Mailing list</a> with details.</p>
         </section>
diff --git a/guide/0100/omemo.html b/guide/0100/omemo.html
index cafc639..0b9cc4a 100644
--- a/guide/0100/omemo.html
+++ b/guide/0100/omemo.html
@@ -78,7 +78,7 @@ <h4>Generating Crypto Materials</h4>
             <p>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as <code>haveged</code>, to increase the available entropy.
             </p>
-            <img  src="../../images/omemo/key_generated.png"/><br><br>
+            <img  src="../../images/omemo/key_generated.webp"/><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again. If you want to check your own fingerprint or see the fingerprints of your other devices type:
             </p>
@@ -98,12 +98,12 @@ <h4>Fingerprint authentication</h4>
                 You should exchange fingerprints with your contact's via another secure communication channel. To display your fingerprint, use the following command:
             </p>
             <pre><code>/omemo fingerprint</code></pre>
-            <img src="../../images/omemo/myfp.png"/><br><br>
+            <img src="../../images/omemo/myfp.webp"/><br><br>
             <p>
                 To view the fingerprint of a contact use the following command:
             </p>
             <pre><code>/omemo fingerprint bob</code></pre>
-            <img src="../../images/omemo/theirfp.png"/><br><br>
+            <img src="../../images/omemo/theirfp.webp"/><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually authenticate the contact with the following command:
             </p>
@@ -127,7 +127,7 @@ <h3>Starting a private conversation</h3>
                 If you are already in a conversation window without OMEMO, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/omemo start bob</code></pre>
-            <img src="../../images/omemo/started.png"/><br><br>
+            <img src="../../images/omemo/started.webp"/><br><br>
             <p>
                 The <code>[OMEMO]</code> shown in the titlebar indicates that the conversation is now encrypted.
             </p>
@@ -159,25 +159,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used.
             </p>
-            <img src="../../images/omemo/encwarn.png"/><br><br>
+            <img src="../../images/omemo/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/omemo/encwarnoff.png"/><br><br>
+            <img src="../../images/omemo/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/omemo/plainchar.png"/><br><br>
+            <img src="../../images/omemo/plainchar.webp"/><br><br>
             <p>
                 By default OMEMO encrypted messages are preceeded by the '<code>*</code>' character.
             </p>
-            <img src="../../images/omemo/omemochar.png"/><br><br>
+            <img src="../../images/omemo/omemochar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/omemo char</code> command.
             </p>
             <pre><code>/omemo char O</code></pre>
-            <img src="../../images/omemo/newchar.png"/><br><br>
+            <img src="../../images/omemo/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="omemo-message-logging"></a>
diff --git a/guide/0100/otr.html b/guide/0100/otr.html
index 93a64d6..0361955 100644
--- a/guide/0100/otr.html
+++ b/guide/0100/otr.html
@@ -95,7 +95,7 @@ <h3>Generating a private key</h3>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as
                 <code>haveged</code>, to increase the available entropy.
             </p>
-            <img src="../../images/otr/key_generated.png" /><br><br>
+            <img src="../../images/otr/key_generated.webp" /><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again.
             </p>
@@ -116,7 +116,7 @@ <h3>Starting a private conversation</h3>
                 the same command omitting the contact:
             </p>
             <pre><code>/otr start</code></pre>
-            <img src="../../images/otr/started.png" /><br><br>
+            <img src="../../images/otr/started.webp" /><br><br>
             <p>
                 The <code>[untrusted]</code> shown in the titlebar indicates that although this conversation is
                 encrypted, the contact has not yet been authenticated.
@@ -155,21 +155,21 @@ <h4>Question and answer</h4>
             <p>
                 A message will be displayed showing that the authentication process has started.
             </p>
-            <img src="../../images/otr/question_sent.png" /><br><br>
+            <img src="../../images/otr/question_sent.webp" /><br><br>
             <p>
                 If Bob answers correctly a message will be shown indicating that Bob is now trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_success.png" /><br><br>
+            <img src="../../images/otr/question_received_success.webp" /><br><br>
             <p>
                 If Bob answers incorrectly a message will be shown indicating that Bob is not trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_fail.png" /><br><br>
+            <img src="../../images/otr/question_received_fail.webp" /><br><br>
             <p>
                 Bob may also wish to authenticate Alice. If he does, Alice will receive a message showing Bob's
                 question, and prompting her to answer. Alice may answer using the <code>/otr answer</code> command:
             </p>
             <pre><code>/otr answer red</code></pre>
-            <img src="../../images/otr/bobquestion.png" /><br><br>
+            <img src="../../images/otr/bobquestion.webp" /><br><br>
             <p>
                 Note that question and answer authentication is a way for one contact to verify the identity of another.
                 If the recipient answers correctly then the sender has authenticated them, however the recipient must
@@ -190,14 +190,14 @@ <h4>Shared secret</h4>
             <p>
                 Bob enters the same secret using his client, Alice and Bob now trust each other.
             </p>
-            <img src="../../images/otr/secret_received_success.png" /><br><br>
+            <img src="../../images/otr/secret_received_success.webp" /><br><br>
 
             <p>
                 If Bob started the shared secret authentication, Alice will receive a message asking her to enter the
                 secret using the <code>/otr secret</code> command:
             </p>
             <pre><code>/otr secret 5up3r53cr3t</code></pre>
-            <img src="../../images/otr/secret_sent_success.png" /><br><br>
+            <img src="../../images/otr/secret_sent_success.webp" /><br><br>
 
             <a name="fingerprints"></a>
             <h4>Manual fingerprint authentication</h4>
@@ -210,12 +210,12 @@ <h4>Manual fingerprint authentication</h4>
                 display your fingerprint, use the following command:
             </p>
             <pre><code>/otr myfp</code></pre>
-            <img src="../../images/otr/myfp.png" /><br><br>
+            <img src="../../images/otr/myfp.webp" /><br><br>
             <p>
                 To view the fingerprint of a contact whilst in an OTR session, use the following command:
             </p>
             <pre><code>/otr theirfp</code></pre>
-            <img src="../../images/otr/theirfp.png" /><br><br>
+            <img src="../../images/otr/theirfp.webp" /><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually
                 authenticate the contact with the following command:
@@ -300,26 +300,26 @@ <h3>User Interface options</h3>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a
                     href="pgp.html">PGP</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png" /><br><br>
+            <img src="../../images/pgp/encwarn.webp" /><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a>
                 command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png" /><br><br>
+            <img src="../../images/pgp/encwarnoff.webp" /><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png" /><br><br>
+            <img src="../../images/pgp/plainchar.webp" /><br><br>
             <p>
                 By default OTR encrypted messages are preceeded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/otr/otrchar.png" /><br><br>
+            <img src="../../images/otr/otrchar.webp" /><br><br>
             <p>
                 This character can be changed using the <code>/otr char</code> command.
             </p>
             <pre><code>/otr char O</code></pre>
-            <img src="../../images/otr/newchar.png" /><br><br>
+            <img src="../../images/otr/newchar.webp" /><br><br>
         </section>
         <section>
             <a name="otr-message-logging"></a>
@@ -374,4 +374,4 @@ <h3>Importing OTR keys</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/0100/pgp.html b/guide/0100/pgp.html
index 55454b3..2fdc519 100644
--- a/guide/0100/pgp.html
+++ b/guide/0100/pgp.html
@@ -50,7 +50,7 @@ <h3>Assigning a key to your account</h3>
             <p>
                 To allow contacts to send you PGP encrypted messages you must have a PGP key assigned to your account. To list all available keys on your system, use the command <code>/pgp keys</code>
             </p>
-            <img src="../../images/pgp/pgpkeys.png"/><br><br>
+            <img src="../../images/pgp/pgpkeys.webp"/><br><br>
             <p>
                 Set the account <code>pgpkeyid</code> property with the <a href="reference.html#account"><code>/account</code></a> command.
             </p>
@@ -71,7 +71,7 @@ <h3>Assigning keys to contacts</h3>
                 To view a list of all currently known public keys, either through received signed presence or set manually.
             </p>
             <pre><code>/pgp contacts</code></pre>
-            <img src="../../images/pgp/contacts.png"/><br><br>
+            <img src="../../images/pgp/contacts.webp"/><br><br>
         </section>
         <section>
             <a name="sending"></a>
@@ -85,7 +85,7 @@ <h3>Sending PGP encrypted messages</h3>
                 If you are already in a conversation window without PGP, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/pgp start</code></pre>
-            <img src="../../images/pgp/sending.png"/><br><br>
+            <img src="../../images/pgp/sending.webp"/><br><br>
         </section>
         <section>
             <a name="receiving"></a>
@@ -94,7 +94,7 @@ <h3>Receiving PGP encrypted messages</h3>
             <p>
                 Assuming a public key is associated with the contact, they must also have enabled PGP encryption at their end.
             </p>
-            <img src="../../images/pgp/receiving.png"/><br><br>
+            <img src="../../images/pgp/receiving.webp"/><br><br>
         </section>
         <section>
             <a name="ending"></a>
@@ -104,11 +104,11 @@ <h3>Ending PGP encryption</h3>
                 To stop sending PGP encrypted messages to a contact:
             </p>
             <pre><code>/pgp end</code></pre>
-            <img src="../../images/pgp/endingsend.png"/><br><br>
+            <img src="../../images/pgp/endingsend.webp"/><br><br>
             <p>
                 The contact may also end PGP encryption at their end at any time.
             </p>
-            <img src="../../images/pgp/endingrecv.png"/><br><br>
+            <img src="../../images/pgp/endingrecv.webp"/><br><br>
         </section>
         <section>
             <a name="ui-opts"></a>
@@ -117,25 +117,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a href="otr.html">OTR</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png"/><br><br>
+            <img src="../../images/pgp/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png"/><br><br>
+            <img src="../../images/pgp/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png"/><br><br>
+            <img src="../../images/pgp/plainchar.webp"/><br><br>
             <p>
                 By default PGP encrypted messages are preceded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/pgp/pgpchar.png"/><br><br>
+            <img src="../../images/pgp/pgpchar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/pgp char</code> command.
             </p>
             <pre><code>/pgp char P</code></pre>
-            <img src="../../images/pgp/newchar.png"/><br><br>
+            <img src="../../images/pgp/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="pgp-message-logging"></a>
diff --git a/guide/0100/rooms.html b/guide/0100/rooms.html
index 272c5fd..0079911 100644
--- a/guide/0100/rooms.html
+++ b/guide/0100/rooms.html
@@ -69,7 +69,7 @@ <h3>Creating a chat room</h3>
                     Room Configuration and Administration</a>.</p>
 
             <p>If you are using Google Talk, creating a new room is slightly different. See the <a
-                    href="faq.html#gtalkrooms">FAQ</a>.</p>
+                    href="../../../faq.html#will-profanity-work-with-google-talk">FAQ</a>.</p>
         </section>
         <section>
             <a name="changing-your-nickname"></a>
@@ -138,4 +138,4 @@ <h3>Bookmarking rooms</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/0110/install.html b/guide/0110/install.html
index 2db1891..734a889 100644
--- a/guide/0110/install.html
+++ b/guide/0110/install.html
@@ -133,7 +133,7 @@ <h3>Linux/*BSD</h3>
                 </tr>
             </table>
             <p>To add to this list, submit a pull request to the <a
-                    href="https://github.com/boothj5/www_profanity_im/blob/master/install.html" target="_blank">website
+                    href="https://github.com/profanity-im/profanity-im.github.io/" target="_blank">website
                     source</a>, or email the <a href="https://lists.notraces.net/mailman/listinfo/profanity"
                     target="_blank">Mailing list</a> with details.</p>
         </section>
diff --git a/guide/0110/omemo.html b/guide/0110/omemo.html
new file mode 100644
index 0000000..054973f
--- /dev/null
+++ b/guide/0110/omemo.html
@@ -0,0 +1,211 @@
+<!DOCTYPE html>
+<html>
+<head>
+    <title>Profanity, a console based XMPP client - OMEMO Encryption</title>
+    <meta charset="utf-8">
+    <meta http-equiv="Expires" content="-1">
+    <meta http-equiv="Pragma" content="no-cache">
+    <meta http-equiv="Cache-Control" content="no-cache">
+    <link href="../../css/profanity.css" type="text/css" rel="stylesheet">
+    
+</head>
+<body id="article">
+    <img class="overlay" src="../../images/profanity_mouth-only.png" alt="Profanity Illustration">
+    <header>
+        <h1>
+            <a href="userguide.html">
+                User Guide
+            </a>
+        </h1>
+        <h2>OMEMO Encryption</h2>
+    </header>
+    <article id="manual">
+        <section>
+            <h3>Contents</h3>
+
+            <ul>
+                <li><a href="#state">Current state</a></li>
+                <li><a href="#installing-omemo">Building with OMEMO support</a></li>
+                <li><a href="#prelim-setup">Setup</a></li>
+                <ul>
+                    <li><a href="#private-key-gen">Generating Crypto Materials</a>,
+                        <a href="#fingerprints">Fingerprint authentication</a>,
+                        <a href="#private-conversation">Starting a private conversation</a></li>
+                </ul>
+                <li><a href="#policy">Setting OMEMO policy</a></li>
+                <li><a href="#ui-opts">User Interface options</a></li>
+                <li><a href="#omemo-message-logging">OMEMO message logging</a></li>
+            </ul>
+        </section>
+        <section>
+            <a name="state"></a>
+            <h3>Current state</h3>
+            <p>Profanity has OMEMO support since 0.7.0. Regular 1:1 chats should work without problems. We consider OMEMO MUC as experimental. You might encounter problems there. Make sure to check our <a href="https://github.com/profanity-im/profanity/issues/1070">tracker bug</a> for details. And report anything you find on the issue tracker.</p>
+            <p>Enabling carbons (<code>/carbons on</code>) is recommended in order to enhance OMEMO and overall chat experience.</p>
+            <p>To be able to read on other devices (eg your phone) what you wrote on profanity you need to trust the fingerprints of your other devices manually (<code>/omemo fingerprint <yourjid> <fingerprint></code>).</p>
+            <p>Filetransfer is not OMEMO encrypted since this is not part of the original <a href="https://xmpp.org/extensions/xep-0384.html">XEP-0384</a> but only a <a href="https://xmpp.org/extensions/inbox/omemo-media-sharing.html">proto XEP.</a></p>
+            <p><code>/omemo fingerprint</code> does autocomplete <b>all</b> fingerprints not just the ones for the JID mentioned.</p>
+        </section>
+        <section>
+            <a name="installing-omemo"></a>
+            <h3>Building with OMEMO support</h3>
+            <p>
+            <a href="https://conversations.im/omemo/">OMEMO</a> is an XMPP Extension Protocol (XEP) for secure multi-client end-to-end encryption. It is an open standard based on a Double Ratchet and PEP.
+            </p>
+            <p>
+                Profanity supports OMEMO only if you build from current git master. Support is planned for the 0.7.0 release.
+            </p>
+            <p>
+                If you have <code>libsignal-protocol-c</code> installed, support will be included by default. To force the build to fail if support cannot be included, configure with the following:
+            </p>
+            <pre><code>./configure --enable-omemo</code></pre>
+            <p>
+                Supported <code>libsignal-protocol-c</code> versions are 2.3.1, and 2.3.2.
+            </p>
+        </section>
+        <section>
+            <a name="prelim-setup"></a>
+            <h3>Setup</h3>
+            <a name="private-key-gen"></a>
+            <h4>Generating Crypto Materials</h4>
+            <p>
+                Before you can start using OMEMO for a particular account, you must generate the cryptographic material. Use the following command:
+            </p>
+            <pre><code>/omemo gen</code></pre>
+            <p>
+                A message will appear informing you that the key is being generated which may take a few minutes. We use /dev/random for this.
+            </p>
+            <p>
+                If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as <code>haveged</code>, to increase the available entropy.
+            </p>
+            <img  src="../../images/omemo/key_generated.webp"/><br><br>
+            <p>
+                Once you have generated a key, you will not need to do so again. If you want to check your own fingerprint or see the fingerprints of your other devices type:
+            </p>
+			<pre><code>/omemo fingerprint</code></pre>
+			<p>
+				Hint: To be able to receive messages from your other devices you need to enable carbons. Also trust your own devices analogous to your buddies fingerprints, as described in the next paragraph.
+			</p>
+			<pre><code>/carbons on</code></pre>
+        </section>
+        <section>
+            <a name="fingerprints"></a>
+            <h4>Fingerprint authentication</h4>
+            <p>
+                Before you can start talking with a contact you need to authenticate him by trusting his fingerprint(s).
+            </p>
+            <p>
+                You should exchange fingerprints with your contact's via another secure communication channel. To display your fingerprint, use the following command:
+            </p>
+            <pre><code>/omemo fingerprint</code></pre>
+            <img src="../../images/omemo/myfp.webp"/><br><br>
+            <p>
+                To view the fingerprint of a contact use the following command:
+            </p>
+            <pre><code>/omemo fingerprint bob</code></pre>
+            <img src="../../images/omemo/theirfp.webp"/><br><br>
+            <p>
+                If the fingerprint you see matches the fingerprint you communicated via another means, you can manually authenticate the contact with the following command:
+            </p>
+            <pre><code>/omemo trust 7ef54f6a-af23d766-efc9a4ea-da6fca40-3e8a5c82-9c46e4a4-e4c7230f-937b9144</code></pre>
+            <p>
+                You can untrust a contact at anytime using the following command:
+            </p>
+            <pre><code>/omemo untrust 7ef54f6a-af23d766-efc9a4ea-da6fca40-3e8a5c82-9c46e4a4-e4c7230f-937b9144</code></pre>
+        </section>
+        <section>
+            <a name="private-conversation"></a>
+            <h3>Starting a private conversation</h3>
+            <p>
+                Once the cryptographic material is present and you trusted your contacts fingerprint(s) you can start a private conversation with another contact that uses an OMEMO capable client
+            </p>
+            <p>
+                To start a new conversation using OMEMO:
+            </p>
+            <pre><code>/omemo start bob@ejabberd.local</code></pre>
+            <p>
+                If you are already in a conversation window without OMEMO, you can start sending encrypted messages with the same command omitting the contact:
+            </p>
+            <pre><code>/omemo start bob</code></pre>
+            <img src="../../images/omemo/started.webp"/><br><br>
+            <p>
+                The <code>[OMEMO]</code> shown in the titlebar indicates that the conversation is now encrypted.
+            </p>
+        </section>
+        <section>
+            <a name="policy"></a>
+            <h3>Setting OMEMO policy</h3>
+
+            <p>
+                By default, OMEMO sessions must be started manually using the <code>/omemo start</code> command.
+            </p>
+            <p>
+                The following three settings are available:
+            </p>
+            <p>
+                <b><code>manual</code></b> - The default. Unencrypted messaging is allowed, OMEMO sessions must be started manually.
+            </p>
+            <p>
+            <b><code>automatic</code></b> - If you start an OMEMO session with a contact once via <code>/omemo start</code> it will remember the OMEMO session for this contact. So if you restart Profanity and use <code>/msg bob@ejabberd.local</code> it will OMEMO encrypt the conversation. You can stop this with <code>/omemo stop</code>.
+            </p>
+            <p>
+            <b><code>always</code></b> - OMEMO sessions are always started. Until you use <code>/omemo stop</code>.
+            </p>
+        </section>
+        <section>
+            <a name="ui-opts"></a>
+            <h3>User Interface options</h3>
+
+            <p>
+                By default, an indicator is displayed in the titlebar when no encryption is being used.
+            </p>
+            <img src="../../images/omemo/encwarn.webp"/><br><br>
+            <p>
+                This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
+            </p>
+            <pre><code>/encwarn off</code></pre>
+            <img src="../../images/omemo/encwarnoff.webp"/><br><br>
+            <p>
+                Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
+            </p>
+            <img src="../../images/omemo/plainchar.webp"/><br><br>
+            <p>
+                By default OMEMO encrypted messages are preceeded by the '<code>*</code>' character.
+            </p>
+            <img src="../../images/omemo/omemochar.webp"/><br><br>
+            <p>
+                This character can be changed using the <code>/omemo char</code> command.
+            </p>
+            <pre><code>/omemo char O</code></pre>
+            <img src="../../images/omemo/newchar.webp"/><br><br>
+        </section>
+        <section>
+            <a name="omemo-message-logging"></a>
+            <h3>OMEMO message logging</h3>
+            <p>
+                The <code>/omemo log</code> command may be used with the following options to control if and how OMEMO messages are recorded in chat logs.
+            </p>
+            <table>
+                <tr>
+                    <td><pre><code>on</code></pre></td>
+                    <td>OMEMO messages will be logged in plaintext</td>
+                </tr>
+                <tr>
+                    <td><pre><code>redact</code></pre></td>
+                    <td>OMEMO messages will be logged, but the message will be replaced with the text '<code>[redacted]</code>'.</td>
+                </tr>
+                <tr>
+                    <td><pre><code>off</code></pre></td>
+                    <td>OMEMO messages will not be logged.</td>
+                </tr>
+            </table>
+            <p>
+                For the <code>on</code> and <code>redact</code> settings, chat logging must also be enabled with the <a href="reference.html#chlog"><code>/chlog</code></a> command.
+            </p>
+        </section>
+    </article>
+    <footer>
+        <p class="matty">site designed by <a href="http://www.matthewbalaam.co.uk">Matthew Balaam</a></p>
+    </footer>
+</body>
+</html>
diff --git a/guide/0110/otr.html b/guide/0110/otr.html
index 93a64d6..0361955 100644
--- a/guide/0110/otr.html
+++ b/guide/0110/otr.html
@@ -95,7 +95,7 @@ <h3>Generating a private key</h3>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as
                 <code>haveged</code>, to increase the available entropy.
             </p>
-            <img src="../../images/otr/key_generated.png" /><br><br>
+            <img src="../../images/otr/key_generated.webp" /><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again.
             </p>
@@ -116,7 +116,7 @@ <h3>Starting a private conversation</h3>
                 the same command omitting the contact:
             </p>
             <pre><code>/otr start</code></pre>
-            <img src="../../images/otr/started.png" /><br><br>
+            <img src="../../images/otr/started.webp" /><br><br>
             <p>
                 The <code>[untrusted]</code> shown in the titlebar indicates that although this conversation is
                 encrypted, the contact has not yet been authenticated.
@@ -155,21 +155,21 @@ <h4>Question and answer</h4>
             <p>
                 A message will be displayed showing that the authentication process has started.
             </p>
-            <img src="../../images/otr/question_sent.png" /><br><br>
+            <img src="../../images/otr/question_sent.webp" /><br><br>
             <p>
                 If Bob answers correctly a message will be shown indicating that Bob is now trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_success.png" /><br><br>
+            <img src="../../images/otr/question_received_success.webp" /><br><br>
             <p>
                 If Bob answers incorrectly a message will be shown indicating that Bob is not trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_fail.png" /><br><br>
+            <img src="../../images/otr/question_received_fail.webp" /><br><br>
             <p>
                 Bob may also wish to authenticate Alice. If he does, Alice will receive a message showing Bob's
                 question, and prompting her to answer. Alice may answer using the <code>/otr answer</code> command:
             </p>
             <pre><code>/otr answer red</code></pre>
-            <img src="../../images/otr/bobquestion.png" /><br><br>
+            <img src="../../images/otr/bobquestion.webp" /><br><br>
             <p>
                 Note that question and answer authentication is a way for one contact to verify the identity of another.
                 If the recipient answers correctly then the sender has authenticated them, however the recipient must
@@ -190,14 +190,14 @@ <h4>Shared secret</h4>
             <p>
                 Bob enters the same secret using his client, Alice and Bob now trust each other.
             </p>
-            <img src="../../images/otr/secret_received_success.png" /><br><br>
+            <img src="../../images/otr/secret_received_success.webp" /><br><br>
 
             <p>
                 If Bob started the shared secret authentication, Alice will receive a message asking her to enter the
                 secret using the <code>/otr secret</code> command:
             </p>
             <pre><code>/otr secret 5up3r53cr3t</code></pre>
-            <img src="../../images/otr/secret_sent_success.png" /><br><br>
+            <img src="../../images/otr/secret_sent_success.webp" /><br><br>
 
             <a name="fingerprints"></a>
             <h4>Manual fingerprint authentication</h4>
@@ -210,12 +210,12 @@ <h4>Manual fingerprint authentication</h4>
                 display your fingerprint, use the following command:
             </p>
             <pre><code>/otr myfp</code></pre>
-            <img src="../../images/otr/myfp.png" /><br><br>
+            <img src="../../images/otr/myfp.webp" /><br><br>
             <p>
                 To view the fingerprint of a contact whilst in an OTR session, use the following command:
             </p>
             <pre><code>/otr theirfp</code></pre>
-            <img src="../../images/otr/theirfp.png" /><br><br>
+            <img src="../../images/otr/theirfp.webp" /><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually
                 authenticate the contact with the following command:
@@ -300,26 +300,26 @@ <h3>User Interface options</h3>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a
                     href="pgp.html">PGP</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png" /><br><br>
+            <img src="../../images/pgp/encwarn.webp" /><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a>
                 command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png" /><br><br>
+            <img src="../../images/pgp/encwarnoff.webp" /><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png" /><br><br>
+            <img src="../../images/pgp/plainchar.webp" /><br><br>
             <p>
                 By default OTR encrypted messages are preceeded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/otr/otrchar.png" /><br><br>
+            <img src="../../images/otr/otrchar.webp" /><br><br>
             <p>
                 This character can be changed using the <code>/otr char</code> command.
             </p>
             <pre><code>/otr char O</code></pre>
-            <img src="../../images/otr/newchar.png" /><br><br>
+            <img src="../../images/otr/newchar.webp" /><br><br>
         </section>
         <section>
             <a name="otr-message-logging"></a>
@@ -374,4 +374,4 @@ <h3>Importing OTR keys</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/0110/pgp.html b/guide/0110/pgp.html
index 55454b3..2fdc519 100644
--- a/guide/0110/pgp.html
+++ b/guide/0110/pgp.html
@@ -50,7 +50,7 @@ <h3>Assigning a key to your account</h3>
             <p>
                 To allow contacts to send you PGP encrypted messages you must have a PGP key assigned to your account. To list all available keys on your system, use the command <code>/pgp keys</code>
             </p>
-            <img src="../../images/pgp/pgpkeys.png"/><br><br>
+            <img src="../../images/pgp/pgpkeys.webp"/><br><br>
             <p>
                 Set the account <code>pgpkeyid</code> property with the <a href="reference.html#account"><code>/account</code></a> command.
             </p>
@@ -71,7 +71,7 @@ <h3>Assigning keys to contacts</h3>
                 To view a list of all currently known public keys, either through received signed presence or set manually.
             </p>
             <pre><code>/pgp contacts</code></pre>
-            <img src="../../images/pgp/contacts.png"/><br><br>
+            <img src="../../images/pgp/contacts.webp"/><br><br>
         </section>
         <section>
             <a name="sending"></a>
@@ -85,7 +85,7 @@ <h3>Sending PGP encrypted messages</h3>
                 If you are already in a conversation window without PGP, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/pgp start</code></pre>
-            <img src="../../images/pgp/sending.png"/><br><br>
+            <img src="../../images/pgp/sending.webp"/><br><br>
         </section>
         <section>
             <a name="receiving"></a>
@@ -94,7 +94,7 @@ <h3>Receiving PGP encrypted messages</h3>
             <p>
                 Assuming a public key is associated with the contact, they must also have enabled PGP encryption at their end.
             </p>
-            <img src="../../images/pgp/receiving.png"/><br><br>
+            <img src="../../images/pgp/receiving.webp"/><br><br>
         </section>
         <section>
             <a name="ending"></a>
@@ -104,11 +104,11 @@ <h3>Ending PGP encryption</h3>
                 To stop sending PGP encrypted messages to a contact:
             </p>
             <pre><code>/pgp end</code></pre>
-            <img src="../../images/pgp/endingsend.png"/><br><br>
+            <img src="../../images/pgp/endingsend.webp"/><br><br>
             <p>
                 The contact may also end PGP encryption at their end at any time.
             </p>
-            <img src="../../images/pgp/endingrecv.png"/><br><br>
+            <img src="../../images/pgp/endingrecv.webp"/><br><br>
         </section>
         <section>
             <a name="ui-opts"></a>
@@ -117,25 +117,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a href="otr.html">OTR</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png"/><br><br>
+            <img src="../../images/pgp/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png"/><br><br>
+            <img src="../../images/pgp/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png"/><br><br>
+            <img src="../../images/pgp/plainchar.webp"/><br><br>
             <p>
                 By default PGP encrypted messages are preceded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/pgp/pgpchar.png"/><br><br>
+            <img src="../../images/pgp/pgpchar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/pgp char</code> command.
             </p>
             <pre><code>/pgp char P</code></pre>
-            <img src="../../images/pgp/newchar.png"/><br><br>
+            <img src="../../images/pgp/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="pgp-message-logging"></a>
diff --git a/guide/0110/rooms.html b/guide/0110/rooms.html
index 272c5fd..0079911 100644
--- a/guide/0110/rooms.html
+++ b/guide/0110/rooms.html
@@ -69,7 +69,7 @@ <h3>Creating a chat room</h3>
                     Room Configuration and Administration</a>.</p>
 
             <p>If you are using Google Talk, creating a new room is slightly different. See the <a
-                    href="faq.html#gtalkrooms">FAQ</a>.</p>
+                    href="../../../faq.html#will-profanity-work-with-google-talk">FAQ</a>.</p>
         </section>
         <section>
             <a name="changing-your-nickname"></a>
@@ -138,4 +138,4 @@ <h3>Bookmarking rooms</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/0111/install.html b/guide/0111/install.html
index 2db1891..734a889 100644
--- a/guide/0111/install.html
+++ b/guide/0111/install.html
@@ -133,7 +133,7 @@ <h3>Linux/*BSD</h3>
                 </tr>
             </table>
             <p>To add to this list, submit a pull request to the <a
-                    href="https://github.com/boothj5/www_profanity_im/blob/master/install.html" target="_blank">website
+                    href="https://github.com/profanity-im/profanity-im.github.io/" target="_blank">website
                     source</a>, or email the <a href="https://lists.notraces.net/mailman/listinfo/profanity"
                     target="_blank">Mailing list</a> with details.</p>
         </section>
diff --git a/guide/0111/omemo.html b/guide/0111/omemo.html
index 7905b84..054973f 100644
--- a/guide/0111/omemo.html
+++ b/guide/0111/omemo.html
@@ -78,7 +78,7 @@ <h4>Generating Crypto Materials</h4>
             <p>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as <code>haveged</code>, to increase the available entropy.
             </p>
-            <img  src="../../images/omemo/key_generated.png"/><br><br>
+            <img  src="../../images/omemo/key_generated.webp"/><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again. If you want to check your own fingerprint or see the fingerprints of your other devices type:
             </p>
@@ -98,12 +98,12 @@ <h4>Fingerprint authentication</h4>
                 You should exchange fingerprints with your contact's via another secure communication channel. To display your fingerprint, use the following command:
             </p>
             <pre><code>/omemo fingerprint</code></pre>
-            <img src="../../images/omemo/myfp.png"/><br><br>
+            <img src="../../images/omemo/myfp.webp"/><br><br>
             <p>
                 To view the fingerprint of a contact use the following command:
             </p>
             <pre><code>/omemo fingerprint bob</code></pre>
-            <img src="../../images/omemo/theirfp.png"/><br><br>
+            <img src="../../images/omemo/theirfp.webp"/><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually authenticate the contact with the following command:
             </p>
@@ -127,7 +127,7 @@ <h3>Starting a private conversation</h3>
                 If you are already in a conversation window without OMEMO, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/omemo start bob</code></pre>
-            <img src="../../images/omemo/started.png"/><br><br>
+            <img src="../../images/omemo/started.webp"/><br><br>
             <p>
                 The <code>[OMEMO]</code> shown in the titlebar indicates that the conversation is now encrypted.
             </p>
@@ -159,25 +159,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used.
             </p>
-            <img src="../../images/omemo/encwarn.png"/><br><br>
+            <img src="../../images/omemo/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/omemo/encwarnoff.png"/><br><br>
+            <img src="../../images/omemo/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/omemo/plainchar.png"/><br><br>
+            <img src="../../images/omemo/plainchar.webp"/><br><br>
             <p>
                 By default OMEMO encrypted messages are preceeded by the '<code>*</code>' character.
             </p>
-            <img src="../../images/omemo/omemochar.png"/><br><br>
+            <img src="../../images/omemo/omemochar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/omemo char</code> command.
             </p>
             <pre><code>/omemo char O</code></pre>
-            <img src="../../images/omemo/newchar.png"/><br><br>
+            <img src="../../images/omemo/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="omemo-message-logging"></a>
diff --git a/guide/0111/otr.html b/guide/0111/otr.html
index 93a64d6..0361955 100644
--- a/guide/0111/otr.html
+++ b/guide/0111/otr.html
@@ -95,7 +95,7 @@ <h3>Generating a private key</h3>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as
                 <code>haveged</code>, to increase the available entropy.
             </p>
-            <img src="../../images/otr/key_generated.png" /><br><br>
+            <img src="../../images/otr/key_generated.webp" /><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again.
             </p>
@@ -116,7 +116,7 @@ <h3>Starting a private conversation</h3>
                 the same command omitting the contact:
             </p>
             <pre><code>/otr start</code></pre>
-            <img src="../../images/otr/started.png" /><br><br>
+            <img src="../../images/otr/started.webp" /><br><br>
             <p>
                 The <code>[untrusted]</code> shown in the titlebar indicates that although this conversation is
                 encrypted, the contact has not yet been authenticated.
@@ -155,21 +155,21 @@ <h4>Question and answer</h4>
             <p>
                 A message will be displayed showing that the authentication process has started.
             </p>
-            <img src="../../images/otr/question_sent.png" /><br><br>
+            <img src="../../images/otr/question_sent.webp" /><br><br>
             <p>
                 If Bob answers correctly a message will be shown indicating that Bob is now trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_success.png" /><br><br>
+            <img src="../../images/otr/question_received_success.webp" /><br><br>
             <p>
                 If Bob answers incorrectly a message will be shown indicating that Bob is not trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_fail.png" /><br><br>
+            <img src="../../images/otr/question_received_fail.webp" /><br><br>
             <p>
                 Bob may also wish to authenticate Alice. If he does, Alice will receive a message showing Bob's
                 question, and prompting her to answer. Alice may answer using the <code>/otr answer</code> command:
             </p>
             <pre><code>/otr answer red</code></pre>
-            <img src="../../images/otr/bobquestion.png" /><br><br>
+            <img src="../../images/otr/bobquestion.webp" /><br><br>
             <p>
                 Note that question and answer authentication is a way for one contact to verify the identity of another.
                 If the recipient answers correctly then the sender has authenticated them, however the recipient must
@@ -190,14 +190,14 @@ <h4>Shared secret</h4>
             <p>
                 Bob enters the same secret using his client, Alice and Bob now trust each other.
             </p>
-            <img src="../../images/otr/secret_received_success.png" /><br><br>
+            <img src="../../images/otr/secret_received_success.webp" /><br><br>
 
             <p>
                 If Bob started the shared secret authentication, Alice will receive a message asking her to enter the
                 secret using the <code>/otr secret</code> command:
             </p>
             <pre><code>/otr secret 5up3r53cr3t</code></pre>
-            <img src="../../images/otr/secret_sent_success.png" /><br><br>
+            <img src="../../images/otr/secret_sent_success.webp" /><br><br>
 
             <a name="fingerprints"></a>
             <h4>Manual fingerprint authentication</h4>
@@ -210,12 +210,12 @@ <h4>Manual fingerprint authentication</h4>
                 display your fingerprint, use the following command:
             </p>
             <pre><code>/otr myfp</code></pre>
-            <img src="../../images/otr/myfp.png" /><br><br>
+            <img src="../../images/otr/myfp.webp" /><br><br>
             <p>
                 To view the fingerprint of a contact whilst in an OTR session, use the following command:
             </p>
             <pre><code>/otr theirfp</code></pre>
-            <img src="../../images/otr/theirfp.png" /><br><br>
+            <img src="../../images/otr/theirfp.webp" /><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually
                 authenticate the contact with the following command:
@@ -300,26 +300,26 @@ <h3>User Interface options</h3>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a
                     href="pgp.html">PGP</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png" /><br><br>
+            <img src="../../images/pgp/encwarn.webp" /><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a>
                 command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png" /><br><br>
+            <img src="../../images/pgp/encwarnoff.webp" /><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png" /><br><br>
+            <img src="../../images/pgp/plainchar.webp" /><br><br>
             <p>
                 By default OTR encrypted messages are preceeded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/otr/otrchar.png" /><br><br>
+            <img src="../../images/otr/otrchar.webp" /><br><br>
             <p>
                 This character can be changed using the <code>/otr char</code> command.
             </p>
             <pre><code>/otr char O</code></pre>
-            <img src="../../images/otr/newchar.png" /><br><br>
+            <img src="../../images/otr/newchar.webp" /><br><br>
         </section>
         <section>
             <a name="otr-message-logging"></a>
@@ -374,4 +374,4 @@ <h3>Importing OTR keys</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/0111/pgp.html b/guide/0111/pgp.html
index 55454b3..2fdc519 100644
--- a/guide/0111/pgp.html
+++ b/guide/0111/pgp.html
@@ -50,7 +50,7 @@ <h3>Assigning a key to your account</h3>
             <p>
                 To allow contacts to send you PGP encrypted messages you must have a PGP key assigned to your account. To list all available keys on your system, use the command <code>/pgp keys</code>
             </p>
-            <img src="../../images/pgp/pgpkeys.png"/><br><br>
+            <img src="../../images/pgp/pgpkeys.webp"/><br><br>
             <p>
                 Set the account <code>pgpkeyid</code> property with the <a href="reference.html#account"><code>/account</code></a> command.
             </p>
@@ -71,7 +71,7 @@ <h3>Assigning keys to contacts</h3>
                 To view a list of all currently known public keys, either through received signed presence or set manually.
             </p>
             <pre><code>/pgp contacts</code></pre>
-            <img src="../../images/pgp/contacts.png"/><br><br>
+            <img src="../../images/pgp/contacts.webp"/><br><br>
         </section>
         <section>
             <a name="sending"></a>
@@ -85,7 +85,7 @@ <h3>Sending PGP encrypted messages</h3>
                 If you are already in a conversation window without PGP, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/pgp start</code></pre>
-            <img src="../../images/pgp/sending.png"/><br><br>
+            <img src="../../images/pgp/sending.webp"/><br><br>
         </section>
         <section>
             <a name="receiving"></a>
@@ -94,7 +94,7 @@ <h3>Receiving PGP encrypted messages</h3>
             <p>
                 Assuming a public key is associated with the contact, they must also have enabled PGP encryption at their end.
             </p>
-            <img src="../../images/pgp/receiving.png"/><br><br>
+            <img src="../../images/pgp/receiving.webp"/><br><br>
         </section>
         <section>
             <a name="ending"></a>
@@ -104,11 +104,11 @@ <h3>Ending PGP encryption</h3>
                 To stop sending PGP encrypted messages to a contact:
             </p>
             <pre><code>/pgp end</code></pre>
-            <img src="../../images/pgp/endingsend.png"/><br><br>
+            <img src="../../images/pgp/endingsend.webp"/><br><br>
             <p>
                 The contact may also end PGP encryption at their end at any time.
             </p>
-            <img src="../../images/pgp/endingrecv.png"/><br><br>
+            <img src="../../images/pgp/endingrecv.webp"/><br><br>
         </section>
         <section>
             <a name="ui-opts"></a>
@@ -117,25 +117,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a href="otr.html">OTR</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png"/><br><br>
+            <img src="../../images/pgp/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png"/><br><br>
+            <img src="../../images/pgp/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png"/><br><br>
+            <img src="../../images/pgp/plainchar.webp"/><br><br>
             <p>
                 By default PGP encrypted messages are preceded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/pgp/pgpchar.png"/><br><br>
+            <img src="../../images/pgp/pgpchar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/pgp char</code> command.
             </p>
             <pre><code>/pgp char P</code></pre>
-            <img src="../../images/pgp/newchar.png"/><br><br>
+            <img src="../../images/pgp/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="pgp-message-logging"></a>
diff --git a/guide/0111/rooms.html b/guide/0111/rooms.html
index 272c5fd..0079911 100644
--- a/guide/0111/rooms.html
+++ b/guide/0111/rooms.html
@@ -69,7 +69,7 @@ <h3>Creating a chat room</h3>
                     Room Configuration and Administration</a>.</p>
 
             <p>If you are using Google Talk, creating a new room is slightly different. See the <a
-                    href="faq.html#gtalkrooms">FAQ</a>.</p>
+                    href="../../../faq.html#will-profanity-work-with-google-talk">FAQ</a>.</p>
         </section>
         <section>
             <a name="changing-your-nickname"></a>
@@ -138,4 +138,4 @@ <h3>Bookmarking rooms</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/0120/install.html b/guide/0120/install.html
index e348361..8a658b9 100644
--- a/guide/0120/install.html
+++ b/guide/0120/install.html
@@ -133,7 +133,7 @@ <h3>Linux/*BSD</h3>
                 </tr>
             </table>
             <p>To add to this list, submit a pull request to the <a
-                    href="https://github.com/boothj5/www_profanity_im/blob/master/install.html" target="_blank">website
+                    href="https://github.com/profanity-im/profanity-im.github.io/" target="_blank">website
                     source</a>, or email the <a href="https://lists.notraces.net/mailman/listinfo/profanity"
                     target="_blank">Mailing list</a> with details.</p>
         </section>
diff --git a/guide/0120/omemo.html b/guide/0120/omemo.html
index cafc639..0b9cc4a 100644
--- a/guide/0120/omemo.html
+++ b/guide/0120/omemo.html
@@ -78,7 +78,7 @@ <h4>Generating Crypto Materials</h4>
             <p>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as <code>haveged</code>, to increase the available entropy.
             </p>
-            <img  src="../../images/omemo/key_generated.png"/><br><br>
+            <img  src="../../images/omemo/key_generated.webp"/><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again. If you want to check your own fingerprint or see the fingerprints of your other devices type:
             </p>
@@ -98,12 +98,12 @@ <h4>Fingerprint authentication</h4>
                 You should exchange fingerprints with your contact's via another secure communication channel. To display your fingerprint, use the following command:
             </p>
             <pre><code>/omemo fingerprint</code></pre>
-            <img src="../../images/omemo/myfp.png"/><br><br>
+            <img src="../../images/omemo/myfp.webp"/><br><br>
             <p>
                 To view the fingerprint of a contact use the following command:
             </p>
             <pre><code>/omemo fingerprint bob</code></pre>
-            <img src="../../images/omemo/theirfp.png"/><br><br>
+            <img src="../../images/omemo/theirfp.webp"/><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually authenticate the contact with the following command:
             </p>
@@ -127,7 +127,7 @@ <h3>Starting a private conversation</h3>
                 If you are already in a conversation window without OMEMO, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/omemo start bob</code></pre>
-            <img src="../../images/omemo/started.png"/><br><br>
+            <img src="../../images/omemo/started.webp"/><br><br>
             <p>
                 The <code>[OMEMO]</code> shown in the titlebar indicates that the conversation is now encrypted.
             </p>
@@ -159,25 +159,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used.
             </p>
-            <img src="../../images/omemo/encwarn.png"/><br><br>
+            <img src="../../images/omemo/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/omemo/encwarnoff.png"/><br><br>
+            <img src="../../images/omemo/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/omemo/plainchar.png"/><br><br>
+            <img src="../../images/omemo/plainchar.webp"/><br><br>
             <p>
                 By default OMEMO encrypted messages are preceeded by the '<code>*</code>' character.
             </p>
-            <img src="../../images/omemo/omemochar.png"/><br><br>
+            <img src="../../images/omemo/omemochar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/omemo char</code> command.
             </p>
             <pre><code>/omemo char O</code></pre>
-            <img src="../../images/omemo/newchar.png"/><br><br>
+            <img src="../../images/omemo/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="omemo-message-logging"></a>
diff --git a/guide/0120/otr.html b/guide/0120/otr.html
index 93a64d6..0361955 100644
--- a/guide/0120/otr.html
+++ b/guide/0120/otr.html
@@ -95,7 +95,7 @@ <h3>Generating a private key</h3>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as
                 <code>haveged</code>, to increase the available entropy.
             </p>
-            <img src="../../images/otr/key_generated.png" /><br><br>
+            <img src="../../images/otr/key_generated.webp" /><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again.
             </p>
@@ -116,7 +116,7 @@ <h3>Starting a private conversation</h3>
                 the same command omitting the contact:
             </p>
             <pre><code>/otr start</code></pre>
-            <img src="../../images/otr/started.png" /><br><br>
+            <img src="../../images/otr/started.webp" /><br><br>
             <p>
                 The <code>[untrusted]</code> shown in the titlebar indicates that although this conversation is
                 encrypted, the contact has not yet been authenticated.
@@ -155,21 +155,21 @@ <h4>Question and answer</h4>
             <p>
                 A message will be displayed showing that the authentication process has started.
             </p>
-            <img src="../../images/otr/question_sent.png" /><br><br>
+            <img src="../../images/otr/question_sent.webp" /><br><br>
             <p>
                 If Bob answers correctly a message will be shown indicating that Bob is now trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_success.png" /><br><br>
+            <img src="../../images/otr/question_received_success.webp" /><br><br>
             <p>
                 If Bob answers incorrectly a message will be shown indicating that Bob is not trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_fail.png" /><br><br>
+            <img src="../../images/otr/question_received_fail.webp" /><br><br>
             <p>
                 Bob may also wish to authenticate Alice. If he does, Alice will receive a message showing Bob's
                 question, and prompting her to answer. Alice may answer using the <code>/otr answer</code> command:
             </p>
             <pre><code>/otr answer red</code></pre>
-            <img src="../../images/otr/bobquestion.png" /><br><br>
+            <img src="../../images/otr/bobquestion.webp" /><br><br>
             <p>
                 Note that question and answer authentication is a way for one contact to verify the identity of another.
                 If the recipient answers correctly then the sender has authenticated them, however the recipient must
@@ -190,14 +190,14 @@ <h4>Shared secret</h4>
             <p>
                 Bob enters the same secret using his client, Alice and Bob now trust each other.
             </p>
-            <img src="../../images/otr/secret_received_success.png" /><br><br>
+            <img src="../../images/otr/secret_received_success.webp" /><br><br>
 
             <p>
                 If Bob started the shared secret authentication, Alice will receive a message asking her to enter the
                 secret using the <code>/otr secret</code> command:
             </p>
             <pre><code>/otr secret 5up3r53cr3t</code></pre>
-            <img src="../../images/otr/secret_sent_success.png" /><br><br>
+            <img src="../../images/otr/secret_sent_success.webp" /><br><br>
 
             <a name="fingerprints"></a>
             <h4>Manual fingerprint authentication</h4>
@@ -210,12 +210,12 @@ <h4>Manual fingerprint authentication</h4>
                 display your fingerprint, use the following command:
             </p>
             <pre><code>/otr myfp</code></pre>
-            <img src="../../images/otr/myfp.png" /><br><br>
+            <img src="../../images/otr/myfp.webp" /><br><br>
             <p>
                 To view the fingerprint of a contact whilst in an OTR session, use the following command:
             </p>
             <pre><code>/otr theirfp</code></pre>
-            <img src="../../images/otr/theirfp.png" /><br><br>
+            <img src="../../images/otr/theirfp.webp" /><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually
                 authenticate the contact with the following command:
@@ -300,26 +300,26 @@ <h3>User Interface options</h3>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a
                     href="pgp.html">PGP</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png" /><br><br>
+            <img src="../../images/pgp/encwarn.webp" /><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a>
                 command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png" /><br><br>
+            <img src="../../images/pgp/encwarnoff.webp" /><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png" /><br><br>
+            <img src="../../images/pgp/plainchar.webp" /><br><br>
             <p>
                 By default OTR encrypted messages are preceeded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/otr/otrchar.png" /><br><br>
+            <img src="../../images/otr/otrchar.webp" /><br><br>
             <p>
                 This character can be changed using the <code>/otr char</code> command.
             </p>
             <pre><code>/otr char O</code></pre>
-            <img src="../../images/otr/newchar.png" /><br><br>
+            <img src="../../images/otr/newchar.webp" /><br><br>
         </section>
         <section>
             <a name="otr-message-logging"></a>
@@ -374,4 +374,4 @@ <h3>Importing OTR keys</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/0120/pgp.html b/guide/0120/pgp.html
index 55454b3..2fdc519 100644
--- a/guide/0120/pgp.html
+++ b/guide/0120/pgp.html
@@ -50,7 +50,7 @@ <h3>Assigning a key to your account</h3>
             <p>
                 To allow contacts to send you PGP encrypted messages you must have a PGP key assigned to your account. To list all available keys on your system, use the command <code>/pgp keys</code>
             </p>
-            <img src="../../images/pgp/pgpkeys.png"/><br><br>
+            <img src="../../images/pgp/pgpkeys.webp"/><br><br>
             <p>
                 Set the account <code>pgpkeyid</code> property with the <a href="reference.html#account"><code>/account</code></a> command.
             </p>
@@ -71,7 +71,7 @@ <h3>Assigning keys to contacts</h3>
                 To view a list of all currently known public keys, either through received signed presence or set manually.
             </p>
             <pre><code>/pgp contacts</code></pre>
-            <img src="../../images/pgp/contacts.png"/><br><br>
+            <img src="../../images/pgp/contacts.webp"/><br><br>
         </section>
         <section>
             <a name="sending"></a>
@@ -85,7 +85,7 @@ <h3>Sending PGP encrypted messages</h3>
                 If you are already in a conversation window without PGP, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/pgp start</code></pre>
-            <img src="../../images/pgp/sending.png"/><br><br>
+            <img src="../../images/pgp/sending.webp"/><br><br>
         </section>
         <section>
             <a name="receiving"></a>
@@ -94,7 +94,7 @@ <h3>Receiving PGP encrypted messages</h3>
             <p>
                 Assuming a public key is associated with the contact, they must also have enabled PGP encryption at their end.
             </p>
-            <img src="../../images/pgp/receiving.png"/><br><br>
+            <img src="../../images/pgp/receiving.webp"/><br><br>
         </section>
         <section>
             <a name="ending"></a>
@@ -104,11 +104,11 @@ <h3>Ending PGP encryption</h3>
                 To stop sending PGP encrypted messages to a contact:
             </p>
             <pre><code>/pgp end</code></pre>
-            <img src="../../images/pgp/endingsend.png"/><br><br>
+            <img src="../../images/pgp/endingsend.webp"/><br><br>
             <p>
                 The contact may also end PGP encryption at their end at any time.
             </p>
-            <img src="../../images/pgp/endingrecv.png"/><br><br>
+            <img src="../../images/pgp/endingrecv.webp"/><br><br>
         </section>
         <section>
             <a name="ui-opts"></a>
@@ -117,25 +117,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a href="otr.html">OTR</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png"/><br><br>
+            <img src="../../images/pgp/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png"/><br><br>
+            <img src="../../images/pgp/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png"/><br><br>
+            <img src="../../images/pgp/plainchar.webp"/><br><br>
             <p>
                 By default PGP encrypted messages are preceded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/pgp/pgpchar.png"/><br><br>
+            <img src="../../images/pgp/pgpchar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/pgp char</code> command.
             </p>
             <pre><code>/pgp char P</code></pre>
-            <img src="../../images/pgp/newchar.png"/><br><br>
+            <img src="../../images/pgp/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="pgp-message-logging"></a>
diff --git a/guide/0120/rooms.html b/guide/0120/rooms.html
index 272c5fd..0079911 100644
--- a/guide/0120/rooms.html
+++ b/guide/0120/rooms.html
@@ -69,7 +69,7 @@ <h3>Creating a chat room</h3>
                     Room Configuration and Administration</a>.</p>
 
             <p>If you are using Google Talk, creating a new room is slightly different. See the <a
-                    href="faq.html#gtalkrooms">FAQ</a>.</p>
+                    href="../../../faq.html#will-profanity-work-with-google-talk">FAQ</a>.</p>
         </section>
         <section>
             <a name="changing-your-nickname"></a>
@@ -138,4 +138,4 @@ <h3>Bookmarking rooms</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/0130/install.html b/guide/0130/install.html
index e348361..8a658b9 100644
--- a/guide/0130/install.html
+++ b/guide/0130/install.html
@@ -133,7 +133,7 @@ <h3>Linux/*BSD</h3>
                 </tr>
             </table>
             <p>To add to this list, submit a pull request to the <a
-                    href="https://github.com/boothj5/www_profanity_im/blob/master/install.html" target="_blank">website
+                    href="https://github.com/profanity-im/profanity-im.github.io/" target="_blank">website
                     source</a>, or email the <a href="https://lists.notraces.net/mailman/listinfo/profanity"
                     target="_blank">Mailing list</a> with details.</p>
         </section>
diff --git a/guide/0130/omemo.html b/guide/0130/omemo.html
index cafc639..0b9cc4a 100644
--- a/guide/0130/omemo.html
+++ b/guide/0130/omemo.html
@@ -78,7 +78,7 @@ <h4>Generating Crypto Materials</h4>
             <p>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as <code>haveged</code>, to increase the available entropy.
             </p>
-            <img  src="../../images/omemo/key_generated.png"/><br><br>
+            <img  src="../../images/omemo/key_generated.webp"/><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again. If you want to check your own fingerprint or see the fingerprints of your other devices type:
             </p>
@@ -98,12 +98,12 @@ <h4>Fingerprint authentication</h4>
                 You should exchange fingerprints with your contact's via another secure communication channel. To display your fingerprint, use the following command:
             </p>
             <pre><code>/omemo fingerprint</code></pre>
-            <img src="../../images/omemo/myfp.png"/><br><br>
+            <img src="../../images/omemo/myfp.webp"/><br><br>
             <p>
                 To view the fingerprint of a contact use the following command:
             </p>
             <pre><code>/omemo fingerprint bob</code></pre>
-            <img src="../../images/omemo/theirfp.png"/><br><br>
+            <img src="../../images/omemo/theirfp.webp"/><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually authenticate the contact with the following command:
             </p>
@@ -127,7 +127,7 @@ <h3>Starting a private conversation</h3>
                 If you are already in a conversation window without OMEMO, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/omemo start bob</code></pre>
-            <img src="../../images/omemo/started.png"/><br><br>
+            <img src="../../images/omemo/started.webp"/><br><br>
             <p>
                 The <code>[OMEMO]</code> shown in the titlebar indicates that the conversation is now encrypted.
             </p>
@@ -159,25 +159,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used.
             </p>
-            <img src="../../images/omemo/encwarn.png"/><br><br>
+            <img src="../../images/omemo/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/omemo/encwarnoff.png"/><br><br>
+            <img src="../../images/omemo/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/omemo/plainchar.png"/><br><br>
+            <img src="../../images/omemo/plainchar.webp"/><br><br>
             <p>
                 By default OMEMO encrypted messages are preceeded by the '<code>*</code>' character.
             </p>
-            <img src="../../images/omemo/omemochar.png"/><br><br>
+            <img src="../../images/omemo/omemochar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/omemo char</code> command.
             </p>
             <pre><code>/omemo char O</code></pre>
-            <img src="../../images/omemo/newchar.png"/><br><br>
+            <img src="../../images/omemo/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="omemo-message-logging"></a>
diff --git a/guide/0130/otr.html b/guide/0130/otr.html
index 93a64d6..0361955 100644
--- a/guide/0130/otr.html
+++ b/guide/0130/otr.html
@@ -95,7 +95,7 @@ <h3>Generating a private key</h3>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as
                 <code>haveged</code>, to increase the available entropy.
             </p>
-            <img src="../../images/otr/key_generated.png" /><br><br>
+            <img src="../../images/otr/key_generated.webp" /><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again.
             </p>
@@ -116,7 +116,7 @@ <h3>Starting a private conversation</h3>
                 the same command omitting the contact:
             </p>
             <pre><code>/otr start</code></pre>
-            <img src="../../images/otr/started.png" /><br><br>
+            <img src="../../images/otr/started.webp" /><br><br>
             <p>
                 The <code>[untrusted]</code> shown in the titlebar indicates that although this conversation is
                 encrypted, the contact has not yet been authenticated.
@@ -155,21 +155,21 @@ <h4>Question and answer</h4>
             <p>
                 A message will be displayed showing that the authentication process has started.
             </p>
-            <img src="../../images/otr/question_sent.png" /><br><br>
+            <img src="../../images/otr/question_sent.webp" /><br><br>
             <p>
                 If Bob answers correctly a message will be shown indicating that Bob is now trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_success.png" /><br><br>
+            <img src="../../images/otr/question_received_success.webp" /><br><br>
             <p>
                 If Bob answers incorrectly a message will be shown indicating that Bob is not trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_fail.png" /><br><br>
+            <img src="../../images/otr/question_received_fail.webp" /><br><br>
             <p>
                 Bob may also wish to authenticate Alice. If he does, Alice will receive a message showing Bob's
                 question, and prompting her to answer. Alice may answer using the <code>/otr answer</code> command:
             </p>
             <pre><code>/otr answer red</code></pre>
-            <img src="../../images/otr/bobquestion.png" /><br><br>
+            <img src="../../images/otr/bobquestion.webp" /><br><br>
             <p>
                 Note that question and answer authentication is a way for one contact to verify the identity of another.
                 If the recipient answers correctly then the sender has authenticated them, however the recipient must
@@ -190,14 +190,14 @@ <h4>Shared secret</h4>
             <p>
                 Bob enters the same secret using his client, Alice and Bob now trust each other.
             </p>
-            <img src="../../images/otr/secret_received_success.png" /><br><br>
+            <img src="../../images/otr/secret_received_success.webp" /><br><br>
 
             <p>
                 If Bob started the shared secret authentication, Alice will receive a message asking her to enter the
                 secret using the <code>/otr secret</code> command:
             </p>
             <pre><code>/otr secret 5up3r53cr3t</code></pre>
-            <img src="../../images/otr/secret_sent_success.png" /><br><br>
+            <img src="../../images/otr/secret_sent_success.webp" /><br><br>
 
             <a name="fingerprints"></a>
             <h4>Manual fingerprint authentication</h4>
@@ -210,12 +210,12 @@ <h4>Manual fingerprint authentication</h4>
                 display your fingerprint, use the following command:
             </p>
             <pre><code>/otr myfp</code></pre>
-            <img src="../../images/otr/myfp.png" /><br><br>
+            <img src="../../images/otr/myfp.webp" /><br><br>
             <p>
                 To view the fingerprint of a contact whilst in an OTR session, use the following command:
             </p>
             <pre><code>/otr theirfp</code></pre>
-            <img src="../../images/otr/theirfp.png" /><br><br>
+            <img src="../../images/otr/theirfp.webp" /><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually
                 authenticate the contact with the following command:
@@ -300,26 +300,26 @@ <h3>User Interface options</h3>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a
                     href="pgp.html">PGP</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png" /><br><br>
+            <img src="../../images/pgp/encwarn.webp" /><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a>
                 command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png" /><br><br>
+            <img src="../../images/pgp/encwarnoff.webp" /><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png" /><br><br>
+            <img src="../../images/pgp/plainchar.webp" /><br><br>
             <p>
                 By default OTR encrypted messages are preceeded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/otr/otrchar.png" /><br><br>
+            <img src="../../images/otr/otrchar.webp" /><br><br>
             <p>
                 This character can be changed using the <code>/otr char</code> command.
             </p>
             <pre><code>/otr char O</code></pre>
-            <img src="../../images/otr/newchar.png" /><br><br>
+            <img src="../../images/otr/newchar.webp" /><br><br>
         </section>
         <section>
             <a name="otr-message-logging"></a>
@@ -374,4 +374,4 @@ <h3>Importing OTR keys</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/0130/pgp.html b/guide/0130/pgp.html
index 55454b3..2fdc519 100644
--- a/guide/0130/pgp.html
+++ b/guide/0130/pgp.html
@@ -50,7 +50,7 @@ <h3>Assigning a key to your account</h3>
             <p>
                 To allow contacts to send you PGP encrypted messages you must have a PGP key assigned to your account. To list all available keys on your system, use the command <code>/pgp keys</code>
             </p>
-            <img src="../../images/pgp/pgpkeys.png"/><br><br>
+            <img src="../../images/pgp/pgpkeys.webp"/><br><br>
             <p>
                 Set the account <code>pgpkeyid</code> property with the <a href="reference.html#account"><code>/account</code></a> command.
             </p>
@@ -71,7 +71,7 @@ <h3>Assigning keys to contacts</h3>
                 To view a list of all currently known public keys, either through received signed presence or set manually.
             </p>
             <pre><code>/pgp contacts</code></pre>
-            <img src="../../images/pgp/contacts.png"/><br><br>
+            <img src="../../images/pgp/contacts.webp"/><br><br>
         </section>
         <section>
             <a name="sending"></a>
@@ -85,7 +85,7 @@ <h3>Sending PGP encrypted messages</h3>
                 If you are already in a conversation window without PGP, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/pgp start</code></pre>
-            <img src="../../images/pgp/sending.png"/><br><br>
+            <img src="../../images/pgp/sending.webp"/><br><br>
         </section>
         <section>
             <a name="receiving"></a>
@@ -94,7 +94,7 @@ <h3>Receiving PGP encrypted messages</h3>
             <p>
                 Assuming a public key is associated with the contact, they must also have enabled PGP encryption at their end.
             </p>
-            <img src="../../images/pgp/receiving.png"/><br><br>
+            <img src="../../images/pgp/receiving.webp"/><br><br>
         </section>
         <section>
             <a name="ending"></a>
@@ -104,11 +104,11 @@ <h3>Ending PGP encryption</h3>
                 To stop sending PGP encrypted messages to a contact:
             </p>
             <pre><code>/pgp end</code></pre>
-            <img src="../../images/pgp/endingsend.png"/><br><br>
+            <img src="../../images/pgp/endingsend.webp"/><br><br>
             <p>
                 The contact may also end PGP encryption at their end at any time.
             </p>
-            <img src="../../images/pgp/endingrecv.png"/><br><br>
+            <img src="../../images/pgp/endingrecv.webp"/><br><br>
         </section>
         <section>
             <a name="ui-opts"></a>
@@ -117,25 +117,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a href="otr.html">OTR</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png"/><br><br>
+            <img src="../../images/pgp/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png"/><br><br>
+            <img src="../../images/pgp/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png"/><br><br>
+            <img src="../../images/pgp/plainchar.webp"/><br><br>
             <p>
                 By default PGP encrypted messages are preceded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/pgp/pgpchar.png"/><br><br>
+            <img src="../../images/pgp/pgpchar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/pgp char</code> command.
             </p>
             <pre><code>/pgp char P</code></pre>
-            <img src="../../images/pgp/newchar.png"/><br><br>
+            <img src="../../images/pgp/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="pgp-message-logging"></a>
diff --git a/guide/0130/rooms.html b/guide/0130/rooms.html
index 272c5fd..0079911 100644
--- a/guide/0130/rooms.html
+++ b/guide/0130/rooms.html
@@ -69,7 +69,7 @@ <h3>Creating a chat room</h3>
                     Room Configuration and Administration</a>.</p>
 
             <p>If you are using Google Talk, creating a new room is slightly different. See the <a
-                    href="faq.html#gtalkrooms">FAQ</a>.</p>
+                    href="../../../faq.html#will-profanity-work-with-google-talk">FAQ</a>.</p>
         </section>
         <section>
             <a name="changing-your-nickname"></a>
@@ -138,4 +138,4 @@ <h3>Bookmarking rooms</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/0131/install.html b/guide/0131/install.html
index e348361..8a658b9 100644
--- a/guide/0131/install.html
+++ b/guide/0131/install.html
@@ -133,7 +133,7 @@ <h3>Linux/*BSD</h3>
                 </tr>
             </table>
             <p>To add to this list, submit a pull request to the <a
-                    href="https://github.com/boothj5/www_profanity_im/blob/master/install.html" target="_blank">website
+                    href="https://github.com/profanity-im/profanity-im.github.io/" target="_blank">website
                     source</a>, or email the <a href="https://lists.notraces.net/mailman/listinfo/profanity"
                     target="_blank">Mailing list</a> with details.</p>
         </section>
diff --git a/guide/0131/omemo.html b/guide/0131/omemo.html
index cafc639..0b9cc4a 100644
--- a/guide/0131/omemo.html
+++ b/guide/0131/omemo.html
@@ -78,7 +78,7 @@ <h4>Generating Crypto Materials</h4>
             <p>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as <code>haveged</code>, to increase the available entropy.
             </p>
-            <img  src="../../images/omemo/key_generated.png"/><br><br>
+            <img  src="../../images/omemo/key_generated.webp"/><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again. If you want to check your own fingerprint or see the fingerprints of your other devices type:
             </p>
@@ -98,12 +98,12 @@ <h4>Fingerprint authentication</h4>
                 You should exchange fingerprints with your contact's via another secure communication channel. To display your fingerprint, use the following command:
             </p>
             <pre><code>/omemo fingerprint</code></pre>
-            <img src="../../images/omemo/myfp.png"/><br><br>
+            <img src="../../images/omemo/myfp.webp"/><br><br>
             <p>
                 To view the fingerprint of a contact use the following command:
             </p>
             <pre><code>/omemo fingerprint bob</code></pre>
-            <img src="../../images/omemo/theirfp.png"/><br><br>
+            <img src="../../images/omemo/theirfp.webp"/><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually authenticate the contact with the following command:
             </p>
@@ -127,7 +127,7 @@ <h3>Starting a private conversation</h3>
                 If you are already in a conversation window without OMEMO, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/omemo start bob</code></pre>
-            <img src="../../images/omemo/started.png"/><br><br>
+            <img src="../../images/omemo/started.webp"/><br><br>
             <p>
                 The <code>[OMEMO]</code> shown in the titlebar indicates that the conversation is now encrypted.
             </p>
@@ -159,25 +159,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used.
             </p>
-            <img src="../../images/omemo/encwarn.png"/><br><br>
+            <img src="../../images/omemo/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/omemo/encwarnoff.png"/><br><br>
+            <img src="../../images/omemo/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/omemo/plainchar.png"/><br><br>
+            <img src="../../images/omemo/plainchar.webp"/><br><br>
             <p>
                 By default OMEMO encrypted messages are preceeded by the '<code>*</code>' character.
             </p>
-            <img src="../../images/omemo/omemochar.png"/><br><br>
+            <img src="../../images/omemo/omemochar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/omemo char</code> command.
             </p>
             <pre><code>/omemo char O</code></pre>
-            <img src="../../images/omemo/newchar.png"/><br><br>
+            <img src="../../images/omemo/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="omemo-message-logging"></a>
diff --git a/guide/0131/otr.html b/guide/0131/otr.html
index 93a64d6..0361955 100644
--- a/guide/0131/otr.html
+++ b/guide/0131/otr.html
@@ -95,7 +95,7 @@ <h3>Generating a private key</h3>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as
                 <code>haveged</code>, to increase the available entropy.
             </p>
-            <img src="../../images/otr/key_generated.png" /><br><br>
+            <img src="../../images/otr/key_generated.webp" /><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again.
             </p>
@@ -116,7 +116,7 @@ <h3>Starting a private conversation</h3>
                 the same command omitting the contact:
             </p>
             <pre><code>/otr start</code></pre>
-            <img src="../../images/otr/started.png" /><br><br>
+            <img src="../../images/otr/started.webp" /><br><br>
             <p>
                 The <code>[untrusted]</code> shown in the titlebar indicates that although this conversation is
                 encrypted, the contact has not yet been authenticated.
@@ -155,21 +155,21 @@ <h4>Question and answer</h4>
             <p>
                 A message will be displayed showing that the authentication process has started.
             </p>
-            <img src="../../images/otr/question_sent.png" /><br><br>
+            <img src="../../images/otr/question_sent.webp" /><br><br>
             <p>
                 If Bob answers correctly a message will be shown indicating that Bob is now trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_success.png" /><br><br>
+            <img src="../../images/otr/question_received_success.webp" /><br><br>
             <p>
                 If Bob answers incorrectly a message will be shown indicating that Bob is not trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_fail.png" /><br><br>
+            <img src="../../images/otr/question_received_fail.webp" /><br><br>
             <p>
                 Bob may also wish to authenticate Alice. If he does, Alice will receive a message showing Bob's
                 question, and prompting her to answer. Alice may answer using the <code>/otr answer</code> command:
             </p>
             <pre><code>/otr answer red</code></pre>
-            <img src="../../images/otr/bobquestion.png" /><br><br>
+            <img src="../../images/otr/bobquestion.webp" /><br><br>
             <p>
                 Note that question and answer authentication is a way for one contact to verify the identity of another.
                 If the recipient answers correctly then the sender has authenticated them, however the recipient must
@@ -190,14 +190,14 @@ <h4>Shared secret</h4>
             <p>
                 Bob enters the same secret using his client, Alice and Bob now trust each other.
             </p>
-            <img src="../../images/otr/secret_received_success.png" /><br><br>
+            <img src="../../images/otr/secret_received_success.webp" /><br><br>
 
             <p>
                 If Bob started the shared secret authentication, Alice will receive a message asking her to enter the
                 secret using the <code>/otr secret</code> command:
             </p>
             <pre><code>/otr secret 5up3r53cr3t</code></pre>
-            <img src="../../images/otr/secret_sent_success.png" /><br><br>
+            <img src="../../images/otr/secret_sent_success.webp" /><br><br>
 
             <a name="fingerprints"></a>
             <h4>Manual fingerprint authentication</h4>
@@ -210,12 +210,12 @@ <h4>Manual fingerprint authentication</h4>
                 display your fingerprint, use the following command:
             </p>
             <pre><code>/otr myfp</code></pre>
-            <img src="../../images/otr/myfp.png" /><br><br>
+            <img src="../../images/otr/myfp.webp" /><br><br>
             <p>
                 To view the fingerprint of a contact whilst in an OTR session, use the following command:
             </p>
             <pre><code>/otr theirfp</code></pre>
-            <img src="../../images/otr/theirfp.png" /><br><br>
+            <img src="../../images/otr/theirfp.webp" /><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually
                 authenticate the contact with the following command:
@@ -300,26 +300,26 @@ <h3>User Interface options</h3>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a
                     href="pgp.html">PGP</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png" /><br><br>
+            <img src="../../images/pgp/encwarn.webp" /><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a>
                 command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png" /><br><br>
+            <img src="../../images/pgp/encwarnoff.webp" /><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png" /><br><br>
+            <img src="../../images/pgp/plainchar.webp" /><br><br>
             <p>
                 By default OTR encrypted messages are preceeded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/otr/otrchar.png" /><br><br>
+            <img src="../../images/otr/otrchar.webp" /><br><br>
             <p>
                 This character can be changed using the <code>/otr char</code> command.
             </p>
             <pre><code>/otr char O</code></pre>
-            <img src="../../images/otr/newchar.png" /><br><br>
+            <img src="../../images/otr/newchar.webp" /><br><br>
         </section>
         <section>
             <a name="otr-message-logging"></a>
@@ -374,4 +374,4 @@ <h3>Importing OTR keys</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/0131/pgp.html b/guide/0131/pgp.html
index 55454b3..2fdc519 100644
--- a/guide/0131/pgp.html
+++ b/guide/0131/pgp.html
@@ -50,7 +50,7 @@ <h3>Assigning a key to your account</h3>
             <p>
                 To allow contacts to send you PGP encrypted messages you must have a PGP key assigned to your account. To list all available keys on your system, use the command <code>/pgp keys</code>
             </p>
-            <img src="../../images/pgp/pgpkeys.png"/><br><br>
+            <img src="../../images/pgp/pgpkeys.webp"/><br><br>
             <p>
                 Set the account <code>pgpkeyid</code> property with the <a href="reference.html#account"><code>/account</code></a> command.
             </p>
@@ -71,7 +71,7 @@ <h3>Assigning keys to contacts</h3>
                 To view a list of all currently known public keys, either through received signed presence or set manually.
             </p>
             <pre><code>/pgp contacts</code></pre>
-            <img src="../../images/pgp/contacts.png"/><br><br>
+            <img src="../../images/pgp/contacts.webp"/><br><br>
         </section>
         <section>
             <a name="sending"></a>
@@ -85,7 +85,7 @@ <h3>Sending PGP encrypted messages</h3>
                 If you are already in a conversation window without PGP, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/pgp start</code></pre>
-            <img src="../../images/pgp/sending.png"/><br><br>
+            <img src="../../images/pgp/sending.webp"/><br><br>
         </section>
         <section>
             <a name="receiving"></a>
@@ -94,7 +94,7 @@ <h3>Receiving PGP encrypted messages</h3>
             <p>
                 Assuming a public key is associated with the contact, they must also have enabled PGP encryption at their end.
             </p>
-            <img src="../../images/pgp/receiving.png"/><br><br>
+            <img src="../../images/pgp/receiving.webp"/><br><br>
         </section>
         <section>
             <a name="ending"></a>
@@ -104,11 +104,11 @@ <h3>Ending PGP encryption</h3>
                 To stop sending PGP encrypted messages to a contact:
             </p>
             <pre><code>/pgp end</code></pre>
-            <img src="../../images/pgp/endingsend.png"/><br><br>
+            <img src="../../images/pgp/endingsend.webp"/><br><br>
             <p>
                 The contact may also end PGP encryption at their end at any time.
             </p>
-            <img src="../../images/pgp/endingrecv.png"/><br><br>
+            <img src="../../images/pgp/endingrecv.webp"/><br><br>
         </section>
         <section>
             <a name="ui-opts"></a>
@@ -117,25 +117,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a href="otr.html">OTR</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png"/><br><br>
+            <img src="../../images/pgp/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png"/><br><br>
+            <img src="../../images/pgp/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png"/><br><br>
+            <img src="../../images/pgp/plainchar.webp"/><br><br>
             <p>
                 By default PGP encrypted messages are preceded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/pgp/pgpchar.png"/><br><br>
+            <img src="../../images/pgp/pgpchar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/pgp char</code> command.
             </p>
             <pre><code>/pgp char P</code></pre>
-            <img src="../../images/pgp/newchar.png"/><br><br>
+            <img src="../../images/pgp/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="pgp-message-logging"></a>
diff --git a/guide/0131/rooms.html b/guide/0131/rooms.html
index 272c5fd..0079911 100644
--- a/guide/0131/rooms.html
+++ b/guide/0131/rooms.html
@@ -69,7 +69,7 @@ <h3>Creating a chat room</h3>
                     Room Configuration and Administration</a>.</p>
 
             <p>If you are using Google Talk, creating a new room is slightly different. See the <a
-                    href="faq.html#gtalkrooms">FAQ</a>.</p>
+                    href="../../../faq.html#will-profanity-work-with-google-talk">FAQ</a>.</p>
         </section>
         <section>
             <a name="changing-your-nickname"></a>
@@ -138,4 +138,4 @@ <h3>Bookmarking rooms</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/0140/install.html b/guide/0140/install.html
index e348361..8a658b9 100644
--- a/guide/0140/install.html
+++ b/guide/0140/install.html
@@ -133,7 +133,7 @@ <h3>Linux/*BSD</h3>
                 </tr>
             </table>
             <p>To add to this list, submit a pull request to the <a
-                    href="https://github.com/boothj5/www_profanity_im/blob/master/install.html" target="_blank">website
+                    href="https://github.com/profanity-im/profanity-im.github.io/" target="_blank">website
                     source</a>, or email the <a href="https://lists.notraces.net/mailman/listinfo/profanity"
                     target="_blank">Mailing list</a> with details.</p>
         </section>
diff --git a/guide/0140/omemo.html b/guide/0140/omemo.html
index cafc639..0b9cc4a 100644
--- a/guide/0140/omemo.html
+++ b/guide/0140/omemo.html
@@ -78,7 +78,7 @@ <h4>Generating Crypto Materials</h4>
             <p>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as <code>haveged</code>, to increase the available entropy.
             </p>
-            <img  src="../../images/omemo/key_generated.png"/><br><br>
+            <img  src="../../images/omemo/key_generated.webp"/><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again. If you want to check your own fingerprint or see the fingerprints of your other devices type:
             </p>
@@ -98,12 +98,12 @@ <h4>Fingerprint authentication</h4>
                 You should exchange fingerprints with your contact's via another secure communication channel. To display your fingerprint, use the following command:
             </p>
             <pre><code>/omemo fingerprint</code></pre>
-            <img src="../../images/omemo/myfp.png"/><br><br>
+            <img src="../../images/omemo/myfp.webp"/><br><br>
             <p>
                 To view the fingerprint of a contact use the following command:
             </p>
             <pre><code>/omemo fingerprint bob</code></pre>
-            <img src="../../images/omemo/theirfp.png"/><br><br>
+            <img src="../../images/omemo/theirfp.webp"/><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually authenticate the contact with the following command:
             </p>
@@ -127,7 +127,7 @@ <h3>Starting a private conversation</h3>
                 If you are already in a conversation window without OMEMO, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/omemo start bob</code></pre>
-            <img src="../../images/omemo/started.png"/><br><br>
+            <img src="../../images/omemo/started.webp"/><br><br>
             <p>
                 The <code>[OMEMO]</code> shown in the titlebar indicates that the conversation is now encrypted.
             </p>
@@ -159,25 +159,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used.
             </p>
-            <img src="../../images/omemo/encwarn.png"/><br><br>
+            <img src="../../images/omemo/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/omemo/encwarnoff.png"/><br><br>
+            <img src="../../images/omemo/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/omemo/plainchar.png"/><br><br>
+            <img src="../../images/omemo/plainchar.webp"/><br><br>
             <p>
                 By default OMEMO encrypted messages are preceeded by the '<code>*</code>' character.
             </p>
-            <img src="../../images/omemo/omemochar.png"/><br><br>
+            <img src="../../images/omemo/omemochar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/omemo char</code> command.
             </p>
             <pre><code>/omemo char O</code></pre>
-            <img src="../../images/omemo/newchar.png"/><br><br>
+            <img src="../../images/omemo/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="omemo-message-logging"></a>
diff --git a/guide/0140/otr.html b/guide/0140/otr.html
index 93a64d6..0361955 100644
--- a/guide/0140/otr.html
+++ b/guide/0140/otr.html
@@ -95,7 +95,7 @@ <h3>Generating a private key</h3>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as
                 <code>haveged</code>, to increase the available entropy.
             </p>
-            <img src="../../images/otr/key_generated.png" /><br><br>
+            <img src="../../images/otr/key_generated.webp" /><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again.
             </p>
@@ -116,7 +116,7 @@ <h3>Starting a private conversation</h3>
                 the same command omitting the contact:
             </p>
             <pre><code>/otr start</code></pre>
-            <img src="../../images/otr/started.png" /><br><br>
+            <img src="../../images/otr/started.webp" /><br><br>
             <p>
                 The <code>[untrusted]</code> shown in the titlebar indicates that although this conversation is
                 encrypted, the contact has not yet been authenticated.
@@ -155,21 +155,21 @@ <h4>Question and answer</h4>
             <p>
                 A message will be displayed showing that the authentication process has started.
             </p>
-            <img src="../../images/otr/question_sent.png" /><br><br>
+            <img src="../../images/otr/question_sent.webp" /><br><br>
             <p>
                 If Bob answers correctly a message will be shown indicating that Bob is now trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_success.png" /><br><br>
+            <img src="../../images/otr/question_received_success.webp" /><br><br>
             <p>
                 If Bob answers incorrectly a message will be shown indicating that Bob is not trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_fail.png" /><br><br>
+            <img src="../../images/otr/question_received_fail.webp" /><br><br>
             <p>
                 Bob may also wish to authenticate Alice. If he does, Alice will receive a message showing Bob's
                 question, and prompting her to answer. Alice may answer using the <code>/otr answer</code> command:
             </p>
             <pre><code>/otr answer red</code></pre>
-            <img src="../../images/otr/bobquestion.png" /><br><br>
+            <img src="../../images/otr/bobquestion.webp" /><br><br>
             <p>
                 Note that question and answer authentication is a way for one contact to verify the identity of another.
                 If the recipient answers correctly then the sender has authenticated them, however the recipient must
@@ -190,14 +190,14 @@ <h4>Shared secret</h4>
             <p>
                 Bob enters the same secret using his client, Alice and Bob now trust each other.
             </p>
-            <img src="../../images/otr/secret_received_success.png" /><br><br>
+            <img src="../../images/otr/secret_received_success.webp" /><br><br>
 
             <p>
                 If Bob started the shared secret authentication, Alice will receive a message asking her to enter the
                 secret using the <code>/otr secret</code> command:
             </p>
             <pre><code>/otr secret 5up3r53cr3t</code></pre>
-            <img src="../../images/otr/secret_sent_success.png" /><br><br>
+            <img src="../../images/otr/secret_sent_success.webp" /><br><br>
 
             <a name="fingerprints"></a>
             <h4>Manual fingerprint authentication</h4>
@@ -210,12 +210,12 @@ <h4>Manual fingerprint authentication</h4>
                 display your fingerprint, use the following command:
             </p>
             <pre><code>/otr myfp</code></pre>
-            <img src="../../images/otr/myfp.png" /><br><br>
+            <img src="../../images/otr/myfp.webp" /><br><br>
             <p>
                 To view the fingerprint of a contact whilst in an OTR session, use the following command:
             </p>
             <pre><code>/otr theirfp</code></pre>
-            <img src="../../images/otr/theirfp.png" /><br><br>
+            <img src="../../images/otr/theirfp.webp" /><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually
                 authenticate the contact with the following command:
@@ -300,26 +300,26 @@ <h3>User Interface options</h3>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a
                     href="pgp.html">PGP</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png" /><br><br>
+            <img src="../../images/pgp/encwarn.webp" /><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a>
                 command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png" /><br><br>
+            <img src="../../images/pgp/encwarnoff.webp" /><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png" /><br><br>
+            <img src="../../images/pgp/plainchar.webp" /><br><br>
             <p>
                 By default OTR encrypted messages are preceeded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/otr/otrchar.png" /><br><br>
+            <img src="../../images/otr/otrchar.webp" /><br><br>
             <p>
                 This character can be changed using the <code>/otr char</code> command.
             </p>
             <pre><code>/otr char O</code></pre>
-            <img src="../../images/otr/newchar.png" /><br><br>
+            <img src="../../images/otr/newchar.webp" /><br><br>
         </section>
         <section>
             <a name="otr-message-logging"></a>
@@ -374,4 +374,4 @@ <h3>Importing OTR keys</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/0140/pgp.html b/guide/0140/pgp.html
index 55454b3..2fdc519 100644
--- a/guide/0140/pgp.html
+++ b/guide/0140/pgp.html
@@ -50,7 +50,7 @@ <h3>Assigning a key to your account</h3>
             <p>
                 To allow contacts to send you PGP encrypted messages you must have a PGP key assigned to your account. To list all available keys on your system, use the command <code>/pgp keys</code>
             </p>
-            <img src="../../images/pgp/pgpkeys.png"/><br><br>
+            <img src="../../images/pgp/pgpkeys.webp"/><br><br>
             <p>
                 Set the account <code>pgpkeyid</code> property with the <a href="reference.html#account"><code>/account</code></a> command.
             </p>
@@ -71,7 +71,7 @@ <h3>Assigning keys to contacts</h3>
                 To view a list of all currently known public keys, either through received signed presence or set manually.
             </p>
             <pre><code>/pgp contacts</code></pre>
-            <img src="../../images/pgp/contacts.png"/><br><br>
+            <img src="../../images/pgp/contacts.webp"/><br><br>
         </section>
         <section>
             <a name="sending"></a>
@@ -85,7 +85,7 @@ <h3>Sending PGP encrypted messages</h3>
                 If you are already in a conversation window without PGP, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/pgp start</code></pre>
-            <img src="../../images/pgp/sending.png"/><br><br>
+            <img src="../../images/pgp/sending.webp"/><br><br>
         </section>
         <section>
             <a name="receiving"></a>
@@ -94,7 +94,7 @@ <h3>Receiving PGP encrypted messages</h3>
             <p>
                 Assuming a public key is associated with the contact, they must also have enabled PGP encryption at their end.
             </p>
-            <img src="../../images/pgp/receiving.png"/><br><br>
+            <img src="../../images/pgp/receiving.webp"/><br><br>
         </section>
         <section>
             <a name="ending"></a>
@@ -104,11 +104,11 @@ <h3>Ending PGP encryption</h3>
                 To stop sending PGP encrypted messages to a contact:
             </p>
             <pre><code>/pgp end</code></pre>
-            <img src="../../images/pgp/endingsend.png"/><br><br>
+            <img src="../../images/pgp/endingsend.webp"/><br><br>
             <p>
                 The contact may also end PGP encryption at their end at any time.
             </p>
-            <img src="../../images/pgp/endingrecv.png"/><br><br>
+            <img src="../../images/pgp/endingrecv.webp"/><br><br>
         </section>
         <section>
             <a name="ui-opts"></a>
@@ -117,25 +117,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a href="otr.html">OTR</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png"/><br><br>
+            <img src="../../images/pgp/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png"/><br><br>
+            <img src="../../images/pgp/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png"/><br><br>
+            <img src="../../images/pgp/plainchar.webp"/><br><br>
             <p>
                 By default PGP encrypted messages are preceded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/pgp/pgpchar.png"/><br><br>
+            <img src="../../images/pgp/pgpchar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/pgp char</code> command.
             </p>
             <pre><code>/pgp char P</code></pre>
-            <img src="../../images/pgp/newchar.png"/><br><br>
+            <img src="../../images/pgp/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="pgp-message-logging"></a>
diff --git a/guide/0140/rooms.html b/guide/0140/rooms.html
index 272c5fd..0079911 100644
--- a/guide/0140/rooms.html
+++ b/guide/0140/rooms.html
@@ -69,7 +69,7 @@ <h3>Creating a chat room</h3>
                     Room Configuration and Administration</a>.</p>
 
             <p>If you are using Google Talk, creating a new room is slightly different. See the <a
-                    href="faq.html#gtalkrooms">FAQ</a>.</p>
+                    href="../../../faq.html#will-profanity-work-with-google-talk">FAQ</a>.</p>
         </section>
         <section>
             <a name="changing-your-nickname"></a>
@@ -138,4 +138,4 @@ <h3>Bookmarking rooms</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/0150/install.html b/guide/0150/install.html
index e348361..8a658b9 100644
--- a/guide/0150/install.html
+++ b/guide/0150/install.html
@@ -133,7 +133,7 @@ <h3>Linux/*BSD</h3>
                 </tr>
             </table>
             <p>To add to this list, submit a pull request to the <a
-                    href="https://github.com/boothj5/www_profanity_im/blob/master/install.html" target="_blank">website
+                    href="https://github.com/profanity-im/profanity-im.github.io/" target="_blank">website
                     source</a>, or email the <a href="https://lists.notraces.net/mailman/listinfo/profanity"
                     target="_blank">Mailing list</a> with details.</p>
         </section>
diff --git a/guide/0150/latest/install.html b/guide/0150/latest/install.html
index e348361..8a658b9 100644
--- a/guide/0150/latest/install.html
+++ b/guide/0150/latest/install.html
@@ -133,7 +133,7 @@ <h3>Linux/*BSD</h3>
                 </tr>
             </table>
             <p>To add to this list, submit a pull request to the <a
-                    href="https://github.com/boothj5/www_profanity_im/blob/master/install.html" target="_blank">website
+                    href="https://github.com/profanity-im/profanity-im.github.io/" target="_blank">website
                     source</a>, or email the <a href="https://lists.notraces.net/mailman/listinfo/profanity"
                     target="_blank">Mailing list</a> with details.</p>
         </section>
diff --git a/guide/0150/latest/omemo.html b/guide/0150/latest/omemo.html
index cafc639..0b9cc4a 100644
--- a/guide/0150/latest/omemo.html
+++ b/guide/0150/latest/omemo.html
@@ -78,7 +78,7 @@ <h4>Generating Crypto Materials</h4>
             <p>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as <code>haveged</code>, to increase the available entropy.
             </p>
-            <img  src="../../images/omemo/key_generated.png"/><br><br>
+            <img  src="../../images/omemo/key_generated.webp"/><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again. If you want to check your own fingerprint or see the fingerprints of your other devices type:
             </p>
@@ -98,12 +98,12 @@ <h4>Fingerprint authentication</h4>
                 You should exchange fingerprints with your contact's via another secure communication channel. To display your fingerprint, use the following command:
             </p>
             <pre><code>/omemo fingerprint</code></pre>
-            <img src="../../images/omemo/myfp.png"/><br><br>
+            <img src="../../images/omemo/myfp.webp"/><br><br>
             <p>
                 To view the fingerprint of a contact use the following command:
             </p>
             <pre><code>/omemo fingerprint bob</code></pre>
-            <img src="../../images/omemo/theirfp.png"/><br><br>
+            <img src="../../images/omemo/theirfp.webp"/><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually authenticate the contact with the following command:
             </p>
@@ -127,7 +127,7 @@ <h3>Starting a private conversation</h3>
                 If you are already in a conversation window without OMEMO, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/omemo start bob</code></pre>
-            <img src="../../images/omemo/started.png"/><br><br>
+            <img src="../../images/omemo/started.webp"/><br><br>
             <p>
                 The <code>[OMEMO]</code> shown in the titlebar indicates that the conversation is now encrypted.
             </p>
@@ -159,25 +159,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used.
             </p>
-            <img src="../../images/omemo/encwarn.png"/><br><br>
+            <img src="../../images/omemo/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/omemo/encwarnoff.png"/><br><br>
+            <img src="../../images/omemo/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/omemo/plainchar.png"/><br><br>
+            <img src="../../images/omemo/plainchar.webp"/><br><br>
             <p>
                 By default OMEMO encrypted messages are preceeded by the '<code>*</code>' character.
             </p>
-            <img src="../../images/omemo/omemochar.png"/><br><br>
+            <img src="../../images/omemo/omemochar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/omemo char</code> command.
             </p>
             <pre><code>/omemo char O</code></pre>
-            <img src="../../images/omemo/newchar.png"/><br><br>
+            <img src="../../images/omemo/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="omemo-message-logging"></a>
diff --git a/guide/0150/latest/otr.html b/guide/0150/latest/otr.html
index 93a64d6..0361955 100644
--- a/guide/0150/latest/otr.html
+++ b/guide/0150/latest/otr.html
@@ -95,7 +95,7 @@ <h3>Generating a private key</h3>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as
                 <code>haveged</code>, to increase the available entropy.
             </p>
-            <img src="../../images/otr/key_generated.png" /><br><br>
+            <img src="../../images/otr/key_generated.webp" /><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again.
             </p>
@@ -116,7 +116,7 @@ <h3>Starting a private conversation</h3>
                 the same command omitting the contact:
             </p>
             <pre><code>/otr start</code></pre>
-            <img src="../../images/otr/started.png" /><br><br>
+            <img src="../../images/otr/started.webp" /><br><br>
             <p>
                 The <code>[untrusted]</code> shown in the titlebar indicates that although this conversation is
                 encrypted, the contact has not yet been authenticated.
@@ -155,21 +155,21 @@ <h4>Question and answer</h4>
             <p>
                 A message will be displayed showing that the authentication process has started.
             </p>
-            <img src="../../images/otr/question_sent.png" /><br><br>
+            <img src="../../images/otr/question_sent.webp" /><br><br>
             <p>
                 If Bob answers correctly a message will be shown indicating that Bob is now trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_success.png" /><br><br>
+            <img src="../../images/otr/question_received_success.webp" /><br><br>
             <p>
                 If Bob answers incorrectly a message will be shown indicating that Bob is not trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_fail.png" /><br><br>
+            <img src="../../images/otr/question_received_fail.webp" /><br><br>
             <p>
                 Bob may also wish to authenticate Alice. If he does, Alice will receive a message showing Bob's
                 question, and prompting her to answer. Alice may answer using the <code>/otr answer</code> command:
             </p>
             <pre><code>/otr answer red</code></pre>
-            <img src="../../images/otr/bobquestion.png" /><br><br>
+            <img src="../../images/otr/bobquestion.webp" /><br><br>
             <p>
                 Note that question and answer authentication is a way for one contact to verify the identity of another.
                 If the recipient answers correctly then the sender has authenticated them, however the recipient must
@@ -190,14 +190,14 @@ <h4>Shared secret</h4>
             <p>
                 Bob enters the same secret using his client, Alice and Bob now trust each other.
             </p>
-            <img src="../../images/otr/secret_received_success.png" /><br><br>
+            <img src="../../images/otr/secret_received_success.webp" /><br><br>
 
             <p>
                 If Bob started the shared secret authentication, Alice will receive a message asking her to enter the
                 secret using the <code>/otr secret</code> command:
             </p>
             <pre><code>/otr secret 5up3r53cr3t</code></pre>
-            <img src="../../images/otr/secret_sent_success.png" /><br><br>
+            <img src="../../images/otr/secret_sent_success.webp" /><br><br>
 
             <a name="fingerprints"></a>
             <h4>Manual fingerprint authentication</h4>
@@ -210,12 +210,12 @@ <h4>Manual fingerprint authentication</h4>
                 display your fingerprint, use the following command:
             </p>
             <pre><code>/otr myfp</code></pre>
-            <img src="../../images/otr/myfp.png" /><br><br>
+            <img src="../../images/otr/myfp.webp" /><br><br>
             <p>
                 To view the fingerprint of a contact whilst in an OTR session, use the following command:
             </p>
             <pre><code>/otr theirfp</code></pre>
-            <img src="../../images/otr/theirfp.png" /><br><br>
+            <img src="../../images/otr/theirfp.webp" /><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually
                 authenticate the contact with the following command:
@@ -300,26 +300,26 @@ <h3>User Interface options</h3>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a
                     href="pgp.html">PGP</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png" /><br><br>
+            <img src="../../images/pgp/encwarn.webp" /><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a>
                 command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png" /><br><br>
+            <img src="../../images/pgp/encwarnoff.webp" /><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png" /><br><br>
+            <img src="../../images/pgp/plainchar.webp" /><br><br>
             <p>
                 By default OTR encrypted messages are preceeded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/otr/otrchar.png" /><br><br>
+            <img src="../../images/otr/otrchar.webp" /><br><br>
             <p>
                 This character can be changed using the <code>/otr char</code> command.
             </p>
             <pre><code>/otr char O</code></pre>
-            <img src="../../images/otr/newchar.png" /><br><br>
+            <img src="../../images/otr/newchar.webp" /><br><br>
         </section>
         <section>
             <a name="otr-message-logging"></a>
@@ -374,4 +374,4 @@ <h3>Importing OTR keys</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/0150/latest/pgp.html b/guide/0150/latest/pgp.html
index 55454b3..2fdc519 100644
--- a/guide/0150/latest/pgp.html
+++ b/guide/0150/latest/pgp.html
@@ -50,7 +50,7 @@ <h3>Assigning a key to your account</h3>
             <p>
                 To allow contacts to send you PGP encrypted messages you must have a PGP key assigned to your account. To list all available keys on your system, use the command <code>/pgp keys</code>
             </p>
-            <img src="../../images/pgp/pgpkeys.png"/><br><br>
+            <img src="../../images/pgp/pgpkeys.webp"/><br><br>
             <p>
                 Set the account <code>pgpkeyid</code> property with the <a href="reference.html#account"><code>/account</code></a> command.
             </p>
@@ -71,7 +71,7 @@ <h3>Assigning keys to contacts</h3>
                 To view a list of all currently known public keys, either through received signed presence or set manually.
             </p>
             <pre><code>/pgp contacts</code></pre>
-            <img src="../../images/pgp/contacts.png"/><br><br>
+            <img src="../../images/pgp/contacts.webp"/><br><br>
         </section>
         <section>
             <a name="sending"></a>
@@ -85,7 +85,7 @@ <h3>Sending PGP encrypted messages</h3>
                 If you are already in a conversation window without PGP, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/pgp start</code></pre>
-            <img src="../../images/pgp/sending.png"/><br><br>
+            <img src="../../images/pgp/sending.webp"/><br><br>
         </section>
         <section>
             <a name="receiving"></a>
@@ -94,7 +94,7 @@ <h3>Receiving PGP encrypted messages</h3>
             <p>
                 Assuming a public key is associated with the contact, they must also have enabled PGP encryption at their end.
             </p>
-            <img src="../../images/pgp/receiving.png"/><br><br>
+            <img src="../../images/pgp/receiving.webp"/><br><br>
         </section>
         <section>
             <a name="ending"></a>
@@ -104,11 +104,11 @@ <h3>Ending PGP encryption</h3>
                 To stop sending PGP encrypted messages to a contact:
             </p>
             <pre><code>/pgp end</code></pre>
-            <img src="../../images/pgp/endingsend.png"/><br><br>
+            <img src="../../images/pgp/endingsend.webp"/><br><br>
             <p>
                 The contact may also end PGP encryption at their end at any time.
             </p>
-            <img src="../../images/pgp/endingrecv.png"/><br><br>
+            <img src="../../images/pgp/endingrecv.webp"/><br><br>
         </section>
         <section>
             <a name="ui-opts"></a>
@@ -117,25 +117,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a href="otr.html">OTR</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png"/><br><br>
+            <img src="../../images/pgp/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png"/><br><br>
+            <img src="../../images/pgp/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png"/><br><br>
+            <img src="../../images/pgp/plainchar.webp"/><br><br>
             <p>
                 By default PGP encrypted messages are preceded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/pgp/pgpchar.png"/><br><br>
+            <img src="../../images/pgp/pgpchar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/pgp char</code> command.
             </p>
             <pre><code>/pgp char P</code></pre>
-            <img src="../../images/pgp/newchar.png"/><br><br>
+            <img src="../../images/pgp/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="pgp-message-logging"></a>
diff --git a/guide/0150/latest/rooms.html b/guide/0150/latest/rooms.html
index 272c5fd..0079911 100644
--- a/guide/0150/latest/rooms.html
+++ b/guide/0150/latest/rooms.html
@@ -69,7 +69,7 @@ <h3>Creating a chat room</h3>
                     Room Configuration and Administration</a>.</p>
 
             <p>If you are using Google Talk, creating a new room is slightly different. See the <a
-                    href="faq.html#gtalkrooms">FAQ</a>.</p>
+                    href="../../../faq.html#will-profanity-work-with-google-talk">FAQ</a>.</p>
         </section>
         <section>
             <a name="changing-your-nickname"></a>
@@ -138,4 +138,4 @@ <h3>Bookmarking rooms</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/0150/omemo.html b/guide/0150/omemo.html
index cafc639..0b9cc4a 100644
--- a/guide/0150/omemo.html
+++ b/guide/0150/omemo.html
@@ -78,7 +78,7 @@ <h4>Generating Crypto Materials</h4>
             <p>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as <code>haveged</code>, to increase the available entropy.
             </p>
-            <img  src="../../images/omemo/key_generated.png"/><br><br>
+            <img  src="../../images/omemo/key_generated.webp"/><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again. If you want to check your own fingerprint or see the fingerprints of your other devices type:
             </p>
@@ -98,12 +98,12 @@ <h4>Fingerprint authentication</h4>
                 You should exchange fingerprints with your contact's via another secure communication channel. To display your fingerprint, use the following command:
             </p>
             <pre><code>/omemo fingerprint</code></pre>
-            <img src="../../images/omemo/myfp.png"/><br><br>
+            <img src="../../images/omemo/myfp.webp"/><br><br>
             <p>
                 To view the fingerprint of a contact use the following command:
             </p>
             <pre><code>/omemo fingerprint bob</code></pre>
-            <img src="../../images/omemo/theirfp.png"/><br><br>
+            <img src="../../images/omemo/theirfp.webp"/><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually authenticate the contact with the following command:
             </p>
@@ -127,7 +127,7 @@ <h3>Starting a private conversation</h3>
                 If you are already in a conversation window without OMEMO, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/omemo start bob</code></pre>
-            <img src="../../images/omemo/started.png"/><br><br>
+            <img src="../../images/omemo/started.webp"/><br><br>
             <p>
                 The <code>[OMEMO]</code> shown in the titlebar indicates that the conversation is now encrypted.
             </p>
@@ -159,25 +159,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used.
             </p>
-            <img src="../../images/omemo/encwarn.png"/><br><br>
+            <img src="../../images/omemo/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/omemo/encwarnoff.png"/><br><br>
+            <img src="../../images/omemo/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/omemo/plainchar.png"/><br><br>
+            <img src="../../images/omemo/plainchar.webp"/><br><br>
             <p>
                 By default OMEMO encrypted messages are preceeded by the '<code>*</code>' character.
             </p>
-            <img src="../../images/omemo/omemochar.png"/><br><br>
+            <img src="../../images/omemo/omemochar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/omemo char</code> command.
             </p>
             <pre><code>/omemo char O</code></pre>
-            <img src="../../images/omemo/newchar.png"/><br><br>
+            <img src="../../images/omemo/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="omemo-message-logging"></a>
diff --git a/guide/0150/otr.html b/guide/0150/otr.html
index 93a64d6..0361955 100644
--- a/guide/0150/otr.html
+++ b/guide/0150/otr.html
@@ -95,7 +95,7 @@ <h3>Generating a private key</h3>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as
                 <code>haveged</code>, to increase the available entropy.
             </p>
-            <img src="../../images/otr/key_generated.png" /><br><br>
+            <img src="../../images/otr/key_generated.webp" /><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again.
             </p>
@@ -116,7 +116,7 @@ <h3>Starting a private conversation</h3>
                 the same command omitting the contact:
             </p>
             <pre><code>/otr start</code></pre>
-            <img src="../../images/otr/started.png" /><br><br>
+            <img src="../../images/otr/started.webp" /><br><br>
             <p>
                 The <code>[untrusted]</code> shown in the titlebar indicates that although this conversation is
                 encrypted, the contact has not yet been authenticated.
@@ -155,21 +155,21 @@ <h4>Question and answer</h4>
             <p>
                 A message will be displayed showing that the authentication process has started.
             </p>
-            <img src="../../images/otr/question_sent.png" /><br><br>
+            <img src="../../images/otr/question_sent.webp" /><br><br>
             <p>
                 If Bob answers correctly a message will be shown indicating that Bob is now trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_success.png" /><br><br>
+            <img src="../../images/otr/question_received_success.webp" /><br><br>
             <p>
                 If Bob answers incorrectly a message will be shown indicating that Bob is not trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_fail.png" /><br><br>
+            <img src="../../images/otr/question_received_fail.webp" /><br><br>
             <p>
                 Bob may also wish to authenticate Alice. If he does, Alice will receive a message showing Bob's
                 question, and prompting her to answer. Alice may answer using the <code>/otr answer</code> command:
             </p>
             <pre><code>/otr answer red</code></pre>
-            <img src="../../images/otr/bobquestion.png" /><br><br>
+            <img src="../../images/otr/bobquestion.webp" /><br><br>
             <p>
                 Note that question and answer authentication is a way for one contact to verify the identity of another.
                 If the recipient answers correctly then the sender has authenticated them, however the recipient must
@@ -190,14 +190,14 @@ <h4>Shared secret</h4>
             <p>
                 Bob enters the same secret using his client, Alice and Bob now trust each other.
             </p>
-            <img src="../../images/otr/secret_received_success.png" /><br><br>
+            <img src="../../images/otr/secret_received_success.webp" /><br><br>
 
             <p>
                 If Bob started the shared secret authentication, Alice will receive a message asking her to enter the
                 secret using the <code>/otr secret</code> command:
             </p>
             <pre><code>/otr secret 5up3r53cr3t</code></pre>
-            <img src="../../images/otr/secret_sent_success.png" /><br><br>
+            <img src="../../images/otr/secret_sent_success.webp" /><br><br>
 
             <a name="fingerprints"></a>
             <h4>Manual fingerprint authentication</h4>
@@ -210,12 +210,12 @@ <h4>Manual fingerprint authentication</h4>
                 display your fingerprint, use the following command:
             </p>
             <pre><code>/otr myfp</code></pre>
-            <img src="../../images/otr/myfp.png" /><br><br>
+            <img src="../../images/otr/myfp.webp" /><br><br>
             <p>
                 To view the fingerprint of a contact whilst in an OTR session, use the following command:
             </p>
             <pre><code>/otr theirfp</code></pre>
-            <img src="../../images/otr/theirfp.png" /><br><br>
+            <img src="../../images/otr/theirfp.webp" /><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually
                 authenticate the contact with the following command:
@@ -300,26 +300,26 @@ <h3>User Interface options</h3>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a
                     href="pgp.html">PGP</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png" /><br><br>
+            <img src="../../images/pgp/encwarn.webp" /><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a>
                 command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png" /><br><br>
+            <img src="../../images/pgp/encwarnoff.webp" /><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png" /><br><br>
+            <img src="../../images/pgp/plainchar.webp" /><br><br>
             <p>
                 By default OTR encrypted messages are preceeded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/otr/otrchar.png" /><br><br>
+            <img src="../../images/otr/otrchar.webp" /><br><br>
             <p>
                 This character can be changed using the <code>/otr char</code> command.
             </p>
             <pre><code>/otr char O</code></pre>
-            <img src="../../images/otr/newchar.png" /><br><br>
+            <img src="../../images/otr/newchar.webp" /><br><br>
         </section>
         <section>
             <a name="otr-message-logging"></a>
@@ -374,4 +374,4 @@ <h3>Importing OTR keys</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/0150/pgp.html b/guide/0150/pgp.html
index 55454b3..2fdc519 100644
--- a/guide/0150/pgp.html
+++ b/guide/0150/pgp.html
@@ -50,7 +50,7 @@ <h3>Assigning a key to your account</h3>
             <p>
                 To allow contacts to send you PGP encrypted messages you must have a PGP key assigned to your account. To list all available keys on your system, use the command <code>/pgp keys</code>
             </p>
-            <img src="../../images/pgp/pgpkeys.png"/><br><br>
+            <img src="../../images/pgp/pgpkeys.webp"/><br><br>
             <p>
                 Set the account <code>pgpkeyid</code> property with the <a href="reference.html#account"><code>/account</code></a> command.
             </p>
@@ -71,7 +71,7 @@ <h3>Assigning keys to contacts</h3>
                 To view a list of all currently known public keys, either through received signed presence or set manually.
             </p>
             <pre><code>/pgp contacts</code></pre>
-            <img src="../../images/pgp/contacts.png"/><br><br>
+            <img src="../../images/pgp/contacts.webp"/><br><br>
         </section>
         <section>
             <a name="sending"></a>
@@ -85,7 +85,7 @@ <h3>Sending PGP encrypted messages</h3>
                 If you are already in a conversation window without PGP, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/pgp start</code></pre>
-            <img src="../../images/pgp/sending.png"/><br><br>
+            <img src="../../images/pgp/sending.webp"/><br><br>
         </section>
         <section>
             <a name="receiving"></a>
@@ -94,7 +94,7 @@ <h3>Receiving PGP encrypted messages</h3>
             <p>
                 Assuming a public key is associated with the contact, they must also have enabled PGP encryption at their end.
             </p>
-            <img src="../../images/pgp/receiving.png"/><br><br>
+            <img src="../../images/pgp/receiving.webp"/><br><br>
         </section>
         <section>
             <a name="ending"></a>
@@ -104,11 +104,11 @@ <h3>Ending PGP encryption</h3>
                 To stop sending PGP encrypted messages to a contact:
             </p>
             <pre><code>/pgp end</code></pre>
-            <img src="../../images/pgp/endingsend.png"/><br><br>
+            <img src="../../images/pgp/endingsend.webp"/><br><br>
             <p>
                 The contact may also end PGP encryption at their end at any time.
             </p>
-            <img src="../../images/pgp/endingrecv.png"/><br><br>
+            <img src="../../images/pgp/endingrecv.webp"/><br><br>
         </section>
         <section>
             <a name="ui-opts"></a>
@@ -117,25 +117,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a href="otr.html">OTR</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png"/><br><br>
+            <img src="../../images/pgp/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png"/><br><br>
+            <img src="../../images/pgp/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png"/><br><br>
+            <img src="../../images/pgp/plainchar.webp"/><br><br>
             <p>
                 By default PGP encrypted messages are preceded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/pgp/pgpchar.png"/><br><br>
+            <img src="../../images/pgp/pgpchar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/pgp char</code> command.
             </p>
             <pre><code>/pgp char P</code></pre>
-            <img src="../../images/pgp/newchar.png"/><br><br>
+            <img src="../../images/pgp/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="pgp-message-logging"></a>
diff --git a/guide/0150/rooms.html b/guide/0150/rooms.html
index 272c5fd..0079911 100644
--- a/guide/0150/rooms.html
+++ b/guide/0150/rooms.html
@@ -69,7 +69,7 @@ <h3>Creating a chat room</h3>
                     Room Configuration and Administration</a>.</p>
 
             <p>If you are using Google Talk, creating a new room is slightly different. See the <a
-                    href="faq.html#gtalkrooms">FAQ</a>.</p>
+                    href="../../../faq.html#will-profanity-work-with-google-talk">FAQ</a>.</p>
         </section>
         <section>
             <a name="changing-your-nickname"></a>
@@ -138,4 +138,4 @@ <h3>Bookmarking rooms</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/0160/install.html b/guide/0160/install.html
index ac691e0..3fa19d7 100644
--- a/guide/0160/install.html
+++ b/guide/0160/install.html
@@ -154,7 +154,7 @@ <h3>Linux/*BSD</h3>
                 </tr>
             </table>
             <p>To add to this list, submit a pull request to the <a
-                    href="https://github.com/boothj5/www_profanity_im/blob/master/install.html" target="_blank">website
+                    href="https://github.com/profanity-im/profanity-im.github.io/" target="_blank">website
                     source</a>, or email the <a href="https://lists.notraces.net/mailman/listinfo/profanity"
                     target="_blank">Mailing list</a> with details.</p>
         </section>
diff --git a/guide/0160/omemo.html b/guide/0160/omemo.html
index cafc639..0b9cc4a 100644
--- a/guide/0160/omemo.html
+++ b/guide/0160/omemo.html
@@ -78,7 +78,7 @@ <h4>Generating Crypto Materials</h4>
             <p>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as <code>haveged</code>, to increase the available entropy.
             </p>
-            <img  src="../../images/omemo/key_generated.png"/><br><br>
+            <img  src="../../images/omemo/key_generated.webp"/><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again. If you want to check your own fingerprint or see the fingerprints of your other devices type:
             </p>
@@ -98,12 +98,12 @@ <h4>Fingerprint authentication</h4>
                 You should exchange fingerprints with your contact's via another secure communication channel. To display your fingerprint, use the following command:
             </p>
             <pre><code>/omemo fingerprint</code></pre>
-            <img src="../../images/omemo/myfp.png"/><br><br>
+            <img src="../../images/omemo/myfp.webp"/><br><br>
             <p>
                 To view the fingerprint of a contact use the following command:
             </p>
             <pre><code>/omemo fingerprint bob</code></pre>
-            <img src="../../images/omemo/theirfp.png"/><br><br>
+            <img src="../../images/omemo/theirfp.webp"/><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually authenticate the contact with the following command:
             </p>
@@ -127,7 +127,7 @@ <h3>Starting a private conversation</h3>
                 If you are already in a conversation window without OMEMO, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/omemo start bob</code></pre>
-            <img src="../../images/omemo/started.png"/><br><br>
+            <img src="../../images/omemo/started.webp"/><br><br>
             <p>
                 The <code>[OMEMO]</code> shown in the titlebar indicates that the conversation is now encrypted.
             </p>
@@ -159,25 +159,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used.
             </p>
-            <img src="../../images/omemo/encwarn.png"/><br><br>
+            <img src="../../images/omemo/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/omemo/encwarnoff.png"/><br><br>
+            <img src="../../images/omemo/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/omemo/plainchar.png"/><br><br>
+            <img src="../../images/omemo/plainchar.webp"/><br><br>
             <p>
                 By default OMEMO encrypted messages are preceeded by the '<code>*</code>' character.
             </p>
-            <img src="../../images/omemo/omemochar.png"/><br><br>
+            <img src="../../images/omemo/omemochar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/omemo char</code> command.
             </p>
             <pre><code>/omemo char O</code></pre>
-            <img src="../../images/omemo/newchar.png"/><br><br>
+            <img src="../../images/omemo/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="omemo-message-logging"></a>
diff --git a/guide/0160/otr.html b/guide/0160/otr.html
index 93a64d6..0361955 100644
--- a/guide/0160/otr.html
+++ b/guide/0160/otr.html
@@ -95,7 +95,7 @@ <h3>Generating a private key</h3>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as
                 <code>haveged</code>, to increase the available entropy.
             </p>
-            <img src="../../images/otr/key_generated.png" /><br><br>
+            <img src="../../images/otr/key_generated.webp" /><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again.
             </p>
@@ -116,7 +116,7 @@ <h3>Starting a private conversation</h3>
                 the same command omitting the contact:
             </p>
             <pre><code>/otr start</code></pre>
-            <img src="../../images/otr/started.png" /><br><br>
+            <img src="../../images/otr/started.webp" /><br><br>
             <p>
                 The <code>[untrusted]</code> shown in the titlebar indicates that although this conversation is
                 encrypted, the contact has not yet been authenticated.
@@ -155,21 +155,21 @@ <h4>Question and answer</h4>
             <p>
                 A message will be displayed showing that the authentication process has started.
             </p>
-            <img src="../../images/otr/question_sent.png" /><br><br>
+            <img src="../../images/otr/question_sent.webp" /><br><br>
             <p>
                 If Bob answers correctly a message will be shown indicating that Bob is now trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_success.png" /><br><br>
+            <img src="../../images/otr/question_received_success.webp" /><br><br>
             <p>
                 If Bob answers incorrectly a message will be shown indicating that Bob is not trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_fail.png" /><br><br>
+            <img src="../../images/otr/question_received_fail.webp" /><br><br>
             <p>
                 Bob may also wish to authenticate Alice. If he does, Alice will receive a message showing Bob's
                 question, and prompting her to answer. Alice may answer using the <code>/otr answer</code> command:
             </p>
             <pre><code>/otr answer red</code></pre>
-            <img src="../../images/otr/bobquestion.png" /><br><br>
+            <img src="../../images/otr/bobquestion.webp" /><br><br>
             <p>
                 Note that question and answer authentication is a way for one contact to verify the identity of another.
                 If the recipient answers correctly then the sender has authenticated them, however the recipient must
@@ -190,14 +190,14 @@ <h4>Shared secret</h4>
             <p>
                 Bob enters the same secret using his client, Alice and Bob now trust each other.
             </p>
-            <img src="../../images/otr/secret_received_success.png" /><br><br>
+            <img src="../../images/otr/secret_received_success.webp" /><br><br>
 
             <p>
                 If Bob started the shared secret authentication, Alice will receive a message asking her to enter the
                 secret using the <code>/otr secret</code> command:
             </p>
             <pre><code>/otr secret 5up3r53cr3t</code></pre>
-            <img src="../../images/otr/secret_sent_success.png" /><br><br>
+            <img src="../../images/otr/secret_sent_success.webp" /><br><br>
 
             <a name="fingerprints"></a>
             <h4>Manual fingerprint authentication</h4>
@@ -210,12 +210,12 @@ <h4>Manual fingerprint authentication</h4>
                 display your fingerprint, use the following command:
             </p>
             <pre><code>/otr myfp</code></pre>
-            <img src="../../images/otr/myfp.png" /><br><br>
+            <img src="../../images/otr/myfp.webp" /><br><br>
             <p>
                 To view the fingerprint of a contact whilst in an OTR session, use the following command:
             </p>
             <pre><code>/otr theirfp</code></pre>
-            <img src="../../images/otr/theirfp.png" /><br><br>
+            <img src="../../images/otr/theirfp.webp" /><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually
                 authenticate the contact with the following command:
@@ -300,26 +300,26 @@ <h3>User Interface options</h3>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a
                     href="pgp.html">PGP</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png" /><br><br>
+            <img src="../../images/pgp/encwarn.webp" /><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a>
                 command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png" /><br><br>
+            <img src="../../images/pgp/encwarnoff.webp" /><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png" /><br><br>
+            <img src="../../images/pgp/plainchar.webp" /><br><br>
             <p>
                 By default OTR encrypted messages are preceeded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/otr/otrchar.png" /><br><br>
+            <img src="../../images/otr/otrchar.webp" /><br><br>
             <p>
                 This character can be changed using the <code>/otr char</code> command.
             </p>
             <pre><code>/otr char O</code></pre>
-            <img src="../../images/otr/newchar.png" /><br><br>
+            <img src="../../images/otr/newchar.webp" /><br><br>
         </section>
         <section>
             <a name="otr-message-logging"></a>
@@ -374,4 +374,4 @@ <h3>Importing OTR keys</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/0160/pgp.html b/guide/0160/pgp.html
index 55454b3..2fdc519 100644
--- a/guide/0160/pgp.html
+++ b/guide/0160/pgp.html
@@ -50,7 +50,7 @@ <h3>Assigning a key to your account</h3>
             <p>
                 To allow contacts to send you PGP encrypted messages you must have a PGP key assigned to your account. To list all available keys on your system, use the command <code>/pgp keys</code>
             </p>
-            <img src="../../images/pgp/pgpkeys.png"/><br><br>
+            <img src="../../images/pgp/pgpkeys.webp"/><br><br>
             <p>
                 Set the account <code>pgpkeyid</code> property with the <a href="reference.html#account"><code>/account</code></a> command.
             </p>
@@ -71,7 +71,7 @@ <h3>Assigning keys to contacts</h3>
                 To view a list of all currently known public keys, either through received signed presence or set manually.
             </p>
             <pre><code>/pgp contacts</code></pre>
-            <img src="../../images/pgp/contacts.png"/><br><br>
+            <img src="../../images/pgp/contacts.webp"/><br><br>
         </section>
         <section>
             <a name="sending"></a>
@@ -85,7 +85,7 @@ <h3>Sending PGP encrypted messages</h3>
                 If you are already in a conversation window without PGP, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/pgp start</code></pre>
-            <img src="../../images/pgp/sending.png"/><br><br>
+            <img src="../../images/pgp/sending.webp"/><br><br>
         </section>
         <section>
             <a name="receiving"></a>
@@ -94,7 +94,7 @@ <h3>Receiving PGP encrypted messages</h3>
             <p>
                 Assuming a public key is associated with the contact, they must also have enabled PGP encryption at their end.
             </p>
-            <img src="../../images/pgp/receiving.png"/><br><br>
+            <img src="../../images/pgp/receiving.webp"/><br><br>
         </section>
         <section>
             <a name="ending"></a>
@@ -104,11 +104,11 @@ <h3>Ending PGP encryption</h3>
                 To stop sending PGP encrypted messages to a contact:
             </p>
             <pre><code>/pgp end</code></pre>
-            <img src="../../images/pgp/endingsend.png"/><br><br>
+            <img src="../../images/pgp/endingsend.webp"/><br><br>
             <p>
                 The contact may also end PGP encryption at their end at any time.
             </p>
-            <img src="../../images/pgp/endingrecv.png"/><br><br>
+            <img src="../../images/pgp/endingrecv.webp"/><br><br>
         </section>
         <section>
             <a name="ui-opts"></a>
@@ -117,25 +117,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a href="otr.html">OTR</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png"/><br><br>
+            <img src="../../images/pgp/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png"/><br><br>
+            <img src="../../images/pgp/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png"/><br><br>
+            <img src="../../images/pgp/plainchar.webp"/><br><br>
             <p>
                 By default PGP encrypted messages are preceded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/pgp/pgpchar.png"/><br><br>
+            <img src="../../images/pgp/pgpchar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/pgp char</code> command.
             </p>
             <pre><code>/pgp char P</code></pre>
-            <img src="../../images/pgp/newchar.png"/><br><br>
+            <img src="../../images/pgp/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="pgp-message-logging"></a>
diff --git a/guide/0160/rooms.html b/guide/0160/rooms.html
index 272c5fd..0079911 100644
--- a/guide/0160/rooms.html
+++ b/guide/0160/rooms.html
@@ -69,7 +69,7 @@ <h3>Creating a chat room</h3>
                     Room Configuration and Administration</a>.</p>
 
             <p>If you are using Google Talk, creating a new room is slightly different. See the <a
-                    href="faq.html#gtalkrooms">FAQ</a>.</p>
+                    href="../../../faq.html#will-profanity-work-with-google-talk">FAQ</a>.</p>
         </section>
         <section>
             <a name="changing-your-nickname"></a>
@@ -138,4 +138,4 @@ <h3>Bookmarking rooms</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/0170/install.html b/guide/0170/install.html
index ac691e0..3fa19d7 100644
--- a/guide/0170/install.html
+++ b/guide/0170/install.html
@@ -154,7 +154,7 @@ <h3>Linux/*BSD</h3>
                 </tr>
             </table>
             <p>To add to this list, submit a pull request to the <a
-                    href="https://github.com/boothj5/www_profanity_im/blob/master/install.html" target="_blank">website
+                    href="https://github.com/profanity-im/profanity-im.github.io/" target="_blank">website
                     source</a>, or email the <a href="https://lists.notraces.net/mailman/listinfo/profanity"
                     target="_blank">Mailing list</a> with details.</p>
         </section>
diff --git a/guide/0170/omemo.html b/guide/0170/omemo.html
index cafc639..0b9cc4a 100644
--- a/guide/0170/omemo.html
+++ b/guide/0170/omemo.html
@@ -78,7 +78,7 @@ <h4>Generating Crypto Materials</h4>
             <p>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as <code>haveged</code>, to increase the available entropy.
             </p>
-            <img  src="../../images/omemo/key_generated.png"/><br><br>
+            <img  src="../../images/omemo/key_generated.webp"/><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again. If you want to check your own fingerprint or see the fingerprints of your other devices type:
             </p>
@@ -98,12 +98,12 @@ <h4>Fingerprint authentication</h4>
                 You should exchange fingerprints with your contact's via another secure communication channel. To display your fingerprint, use the following command:
             </p>
             <pre><code>/omemo fingerprint</code></pre>
-            <img src="../../images/omemo/myfp.png"/><br><br>
+            <img src="../../images/omemo/myfp.webp"/><br><br>
             <p>
                 To view the fingerprint of a contact use the following command:
             </p>
             <pre><code>/omemo fingerprint bob</code></pre>
-            <img src="../../images/omemo/theirfp.png"/><br><br>
+            <img src="../../images/omemo/theirfp.webp"/><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually authenticate the contact with the following command:
             </p>
@@ -127,7 +127,7 @@ <h3>Starting a private conversation</h3>
                 If you are already in a conversation window without OMEMO, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/omemo start bob</code></pre>
-            <img src="../../images/omemo/started.png"/><br><br>
+            <img src="../../images/omemo/started.webp"/><br><br>
             <p>
                 The <code>[OMEMO]</code> shown in the titlebar indicates that the conversation is now encrypted.
             </p>
@@ -159,25 +159,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used.
             </p>
-            <img src="../../images/omemo/encwarn.png"/><br><br>
+            <img src="../../images/omemo/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/omemo/encwarnoff.png"/><br><br>
+            <img src="../../images/omemo/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/omemo/plainchar.png"/><br><br>
+            <img src="../../images/omemo/plainchar.webp"/><br><br>
             <p>
                 By default OMEMO encrypted messages are preceeded by the '<code>*</code>' character.
             </p>
-            <img src="../../images/omemo/omemochar.png"/><br><br>
+            <img src="../../images/omemo/omemochar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/omemo char</code> command.
             </p>
             <pre><code>/omemo char O</code></pre>
-            <img src="../../images/omemo/newchar.png"/><br><br>
+            <img src="../../images/omemo/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="omemo-message-logging"></a>
diff --git a/guide/0170/otr.html b/guide/0170/otr.html
index 93a64d6..0361955 100644
--- a/guide/0170/otr.html
+++ b/guide/0170/otr.html
@@ -95,7 +95,7 @@ <h3>Generating a private key</h3>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as
                 <code>haveged</code>, to increase the available entropy.
             </p>
-            <img src="../../images/otr/key_generated.png" /><br><br>
+            <img src="../../images/otr/key_generated.webp" /><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again.
             </p>
@@ -116,7 +116,7 @@ <h3>Starting a private conversation</h3>
                 the same command omitting the contact:
             </p>
             <pre><code>/otr start</code></pre>
-            <img src="../../images/otr/started.png" /><br><br>
+            <img src="../../images/otr/started.webp" /><br><br>
             <p>
                 The <code>[untrusted]</code> shown in the titlebar indicates that although this conversation is
                 encrypted, the contact has not yet been authenticated.
@@ -155,21 +155,21 @@ <h4>Question and answer</h4>
             <p>
                 A message will be displayed showing that the authentication process has started.
             </p>
-            <img src="../../images/otr/question_sent.png" /><br><br>
+            <img src="../../images/otr/question_sent.webp" /><br><br>
             <p>
                 If Bob answers correctly a message will be shown indicating that Bob is now trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_success.png" /><br><br>
+            <img src="../../images/otr/question_received_success.webp" /><br><br>
             <p>
                 If Bob answers incorrectly a message will be shown indicating that Bob is not trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_fail.png" /><br><br>
+            <img src="../../images/otr/question_received_fail.webp" /><br><br>
             <p>
                 Bob may also wish to authenticate Alice. If he does, Alice will receive a message showing Bob's
                 question, and prompting her to answer. Alice may answer using the <code>/otr answer</code> command:
             </p>
             <pre><code>/otr answer red</code></pre>
-            <img src="../../images/otr/bobquestion.png" /><br><br>
+            <img src="../../images/otr/bobquestion.webp" /><br><br>
             <p>
                 Note that question and answer authentication is a way for one contact to verify the identity of another.
                 If the recipient answers correctly then the sender has authenticated them, however the recipient must
@@ -190,14 +190,14 @@ <h4>Shared secret</h4>
             <p>
                 Bob enters the same secret using his client, Alice and Bob now trust each other.
             </p>
-            <img src="../../images/otr/secret_received_success.png" /><br><br>
+            <img src="../../images/otr/secret_received_success.webp" /><br><br>
 
             <p>
                 If Bob started the shared secret authentication, Alice will receive a message asking her to enter the
                 secret using the <code>/otr secret</code> command:
             </p>
             <pre><code>/otr secret 5up3r53cr3t</code></pre>
-            <img src="../../images/otr/secret_sent_success.png" /><br><br>
+            <img src="../../images/otr/secret_sent_success.webp" /><br><br>
 
             <a name="fingerprints"></a>
             <h4>Manual fingerprint authentication</h4>
@@ -210,12 +210,12 @@ <h4>Manual fingerprint authentication</h4>
                 display your fingerprint, use the following command:
             </p>
             <pre><code>/otr myfp</code></pre>
-            <img src="../../images/otr/myfp.png" /><br><br>
+            <img src="../../images/otr/myfp.webp" /><br><br>
             <p>
                 To view the fingerprint of a contact whilst in an OTR session, use the following command:
             </p>
             <pre><code>/otr theirfp</code></pre>
-            <img src="../../images/otr/theirfp.png" /><br><br>
+            <img src="../../images/otr/theirfp.webp" /><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually
                 authenticate the contact with the following command:
@@ -300,26 +300,26 @@ <h3>User Interface options</h3>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a
                     href="pgp.html">PGP</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png" /><br><br>
+            <img src="../../images/pgp/encwarn.webp" /><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a>
                 command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png" /><br><br>
+            <img src="../../images/pgp/encwarnoff.webp" /><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png" /><br><br>
+            <img src="../../images/pgp/plainchar.webp" /><br><br>
             <p>
                 By default OTR encrypted messages are preceeded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/otr/otrchar.png" /><br><br>
+            <img src="../../images/otr/otrchar.webp" /><br><br>
             <p>
                 This character can be changed using the <code>/otr char</code> command.
             </p>
             <pre><code>/otr char O</code></pre>
-            <img src="../../images/otr/newchar.png" /><br><br>
+            <img src="../../images/otr/newchar.webp" /><br><br>
         </section>
         <section>
             <a name="otr-message-logging"></a>
@@ -374,4 +374,4 @@ <h3>Importing OTR keys</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/0170/pgp.html b/guide/0170/pgp.html
index 55454b3..2fdc519 100644
--- a/guide/0170/pgp.html
+++ b/guide/0170/pgp.html
@@ -50,7 +50,7 @@ <h3>Assigning a key to your account</h3>
             <p>
                 To allow contacts to send you PGP encrypted messages you must have a PGP key assigned to your account. To list all available keys on your system, use the command <code>/pgp keys</code>
             </p>
-            <img src="../../images/pgp/pgpkeys.png"/><br><br>
+            <img src="../../images/pgp/pgpkeys.webp"/><br><br>
             <p>
                 Set the account <code>pgpkeyid</code> property with the <a href="reference.html#account"><code>/account</code></a> command.
             </p>
@@ -71,7 +71,7 @@ <h3>Assigning keys to contacts</h3>
                 To view a list of all currently known public keys, either through received signed presence or set manually.
             </p>
             <pre><code>/pgp contacts</code></pre>
-            <img src="../../images/pgp/contacts.png"/><br><br>
+            <img src="../../images/pgp/contacts.webp"/><br><br>
         </section>
         <section>
             <a name="sending"></a>
@@ -85,7 +85,7 @@ <h3>Sending PGP encrypted messages</h3>
                 If you are already in a conversation window without PGP, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/pgp start</code></pre>
-            <img src="../../images/pgp/sending.png"/><br><br>
+            <img src="../../images/pgp/sending.webp"/><br><br>
         </section>
         <section>
             <a name="receiving"></a>
@@ -94,7 +94,7 @@ <h3>Receiving PGP encrypted messages</h3>
             <p>
                 Assuming a public key is associated with the contact, they must also have enabled PGP encryption at their end.
             </p>
-            <img src="../../images/pgp/receiving.png"/><br><br>
+            <img src="../../images/pgp/receiving.webp"/><br><br>
         </section>
         <section>
             <a name="ending"></a>
@@ -104,11 +104,11 @@ <h3>Ending PGP encryption</h3>
                 To stop sending PGP encrypted messages to a contact:
             </p>
             <pre><code>/pgp end</code></pre>
-            <img src="../../images/pgp/endingsend.png"/><br><br>
+            <img src="../../images/pgp/endingsend.webp"/><br><br>
             <p>
                 The contact may also end PGP encryption at their end at any time.
             </p>
-            <img src="../../images/pgp/endingrecv.png"/><br><br>
+            <img src="../../images/pgp/endingrecv.webp"/><br><br>
         </section>
         <section>
             <a name="ui-opts"></a>
@@ -117,25 +117,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a href="otr.html">OTR</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png"/><br><br>
+            <img src="../../images/pgp/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png"/><br><br>
+            <img src="../../images/pgp/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png"/><br><br>
+            <img src="../../images/pgp/plainchar.webp"/><br><br>
             <p>
                 By default PGP encrypted messages are preceded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/pgp/pgpchar.png"/><br><br>
+            <img src="../../images/pgp/pgpchar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/pgp char</code> command.
             </p>
             <pre><code>/pgp char P</code></pre>
-            <img src="../../images/pgp/newchar.png"/><br><br>
+            <img src="../../images/pgp/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="pgp-message-logging"></a>
diff --git a/guide/0170/rooms.html b/guide/0170/rooms.html
index 272c5fd..0079911 100644
--- a/guide/0170/rooms.html
+++ b/guide/0170/rooms.html
@@ -69,7 +69,7 @@ <h3>Creating a chat room</h3>
                     Room Configuration and Administration</a>.</p>
 
             <p>If you are using Google Talk, creating a new room is slightly different. See the <a
-                    href="faq.html#gtalkrooms">FAQ</a>.</p>
+                    href="../../../faq.html#will-profanity-work-with-google-talk">FAQ</a>.</p>
         </section>
         <section>
             <a name="changing-your-nickname"></a>
@@ -138,4 +138,4 @@ <h3>Bookmarking rooms</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/0180/install.html b/guide/0180/install.html
index ac691e0..3fa19d7 100644
--- a/guide/0180/install.html
+++ b/guide/0180/install.html
@@ -154,7 +154,7 @@ <h3>Linux/*BSD</h3>
                 </tr>
             </table>
             <p>To add to this list, submit a pull request to the <a
-                    href="https://github.com/boothj5/www_profanity_im/blob/master/install.html" target="_blank">website
+                    href="https://github.com/profanity-im/profanity-im.github.io/" target="_blank">website
                     source</a>, or email the <a href="https://lists.notraces.net/mailman/listinfo/profanity"
                     target="_blank">Mailing list</a> with details.</p>
         </section>
diff --git a/guide/0180/omemo.html b/guide/0180/omemo.html
index cafc639..0b9cc4a 100644
--- a/guide/0180/omemo.html
+++ b/guide/0180/omemo.html
@@ -78,7 +78,7 @@ <h4>Generating Crypto Materials</h4>
             <p>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as <code>haveged</code>, to increase the available entropy.
             </p>
-            <img  src="../../images/omemo/key_generated.png"/><br><br>
+            <img  src="../../images/omemo/key_generated.webp"/><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again. If you want to check your own fingerprint or see the fingerprints of your other devices type:
             </p>
@@ -98,12 +98,12 @@ <h4>Fingerprint authentication</h4>
                 You should exchange fingerprints with your contact's via another secure communication channel. To display your fingerprint, use the following command:
             </p>
             <pre><code>/omemo fingerprint</code></pre>
-            <img src="../../images/omemo/myfp.png"/><br><br>
+            <img src="../../images/omemo/myfp.webp"/><br><br>
             <p>
                 To view the fingerprint of a contact use the following command:
             </p>
             <pre><code>/omemo fingerprint bob</code></pre>
-            <img src="../../images/omemo/theirfp.png"/><br><br>
+            <img src="../../images/omemo/theirfp.webp"/><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually authenticate the contact with the following command:
             </p>
@@ -127,7 +127,7 @@ <h3>Starting a private conversation</h3>
                 If you are already in a conversation window without OMEMO, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/omemo start bob</code></pre>
-            <img src="../../images/omemo/started.png"/><br><br>
+            <img src="../../images/omemo/started.webp"/><br><br>
             <p>
                 The <code>[OMEMO]</code> shown in the titlebar indicates that the conversation is now encrypted.
             </p>
@@ -159,25 +159,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used.
             </p>
-            <img src="../../images/omemo/encwarn.png"/><br><br>
+            <img src="../../images/omemo/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/omemo/encwarnoff.png"/><br><br>
+            <img src="../../images/omemo/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/omemo/plainchar.png"/><br><br>
+            <img src="../../images/omemo/plainchar.webp"/><br><br>
             <p>
                 By default OMEMO encrypted messages are preceeded by the '<code>*</code>' character.
             </p>
-            <img src="../../images/omemo/omemochar.png"/><br><br>
+            <img src="../../images/omemo/omemochar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/omemo char</code> command.
             </p>
             <pre><code>/omemo char O</code></pre>
-            <img src="../../images/omemo/newchar.png"/><br><br>
+            <img src="../../images/omemo/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="omemo-message-logging"></a>
diff --git a/guide/0180/otr.html b/guide/0180/otr.html
index 93a64d6..0361955 100644
--- a/guide/0180/otr.html
+++ b/guide/0180/otr.html
@@ -95,7 +95,7 @@ <h3>Generating a private key</h3>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as
                 <code>haveged</code>, to increase the available entropy.
             </p>
-            <img src="../../images/otr/key_generated.png" /><br><br>
+            <img src="../../images/otr/key_generated.webp" /><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again.
             </p>
@@ -116,7 +116,7 @@ <h3>Starting a private conversation</h3>
                 the same command omitting the contact:
             </p>
             <pre><code>/otr start</code></pre>
-            <img src="../../images/otr/started.png" /><br><br>
+            <img src="../../images/otr/started.webp" /><br><br>
             <p>
                 The <code>[untrusted]</code> shown in the titlebar indicates that although this conversation is
                 encrypted, the contact has not yet been authenticated.
@@ -155,21 +155,21 @@ <h4>Question and answer</h4>
             <p>
                 A message will be displayed showing that the authentication process has started.
             </p>
-            <img src="../../images/otr/question_sent.png" /><br><br>
+            <img src="../../images/otr/question_sent.webp" /><br><br>
             <p>
                 If Bob answers correctly a message will be shown indicating that Bob is now trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_success.png" /><br><br>
+            <img src="../../images/otr/question_received_success.webp" /><br><br>
             <p>
                 If Bob answers incorrectly a message will be shown indicating that Bob is not trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_fail.png" /><br><br>
+            <img src="../../images/otr/question_received_fail.webp" /><br><br>
             <p>
                 Bob may also wish to authenticate Alice. If he does, Alice will receive a message showing Bob's
                 question, and prompting her to answer. Alice may answer using the <code>/otr answer</code> command:
             </p>
             <pre><code>/otr answer red</code></pre>
-            <img src="../../images/otr/bobquestion.png" /><br><br>
+            <img src="../../images/otr/bobquestion.webp" /><br><br>
             <p>
                 Note that question and answer authentication is a way for one contact to verify the identity of another.
                 If the recipient answers correctly then the sender has authenticated them, however the recipient must
@@ -190,14 +190,14 @@ <h4>Shared secret</h4>
             <p>
                 Bob enters the same secret using his client, Alice and Bob now trust each other.
             </p>
-            <img src="../../images/otr/secret_received_success.png" /><br><br>
+            <img src="../../images/otr/secret_received_success.webp" /><br><br>
 
             <p>
                 If Bob started the shared secret authentication, Alice will receive a message asking her to enter the
                 secret using the <code>/otr secret</code> command:
             </p>
             <pre><code>/otr secret 5up3r53cr3t</code></pre>
-            <img src="../../images/otr/secret_sent_success.png" /><br><br>
+            <img src="../../images/otr/secret_sent_success.webp" /><br><br>
 
             <a name="fingerprints"></a>
             <h4>Manual fingerprint authentication</h4>
@@ -210,12 +210,12 @@ <h4>Manual fingerprint authentication</h4>
                 display your fingerprint, use the following command:
             </p>
             <pre><code>/otr myfp</code></pre>
-            <img src="../../images/otr/myfp.png" /><br><br>
+            <img src="../../images/otr/myfp.webp" /><br><br>
             <p>
                 To view the fingerprint of a contact whilst in an OTR session, use the following command:
             </p>
             <pre><code>/otr theirfp</code></pre>
-            <img src="../../images/otr/theirfp.png" /><br><br>
+            <img src="../../images/otr/theirfp.webp" /><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually
                 authenticate the contact with the following command:
@@ -300,26 +300,26 @@ <h3>User Interface options</h3>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a
                     href="pgp.html">PGP</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png" /><br><br>
+            <img src="../../images/pgp/encwarn.webp" /><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a>
                 command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png" /><br><br>
+            <img src="../../images/pgp/encwarnoff.webp" /><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png" /><br><br>
+            <img src="../../images/pgp/plainchar.webp" /><br><br>
             <p>
                 By default OTR encrypted messages are preceeded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/otr/otrchar.png" /><br><br>
+            <img src="../../images/otr/otrchar.webp" /><br><br>
             <p>
                 This character can be changed using the <code>/otr char</code> command.
             </p>
             <pre><code>/otr char O</code></pre>
-            <img src="../../images/otr/newchar.png" /><br><br>
+            <img src="../../images/otr/newchar.webp" /><br><br>
         </section>
         <section>
             <a name="otr-message-logging"></a>
@@ -374,4 +374,4 @@ <h3>Importing OTR keys</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/0180/pgp.html b/guide/0180/pgp.html
index 55454b3..2fdc519 100644
--- a/guide/0180/pgp.html
+++ b/guide/0180/pgp.html
@@ -50,7 +50,7 @@ <h3>Assigning a key to your account</h3>
             <p>
                 To allow contacts to send you PGP encrypted messages you must have a PGP key assigned to your account. To list all available keys on your system, use the command <code>/pgp keys</code>
             </p>
-            <img src="../../images/pgp/pgpkeys.png"/><br><br>
+            <img src="../../images/pgp/pgpkeys.webp"/><br><br>
             <p>
                 Set the account <code>pgpkeyid</code> property with the <a href="reference.html#account"><code>/account</code></a> command.
             </p>
@@ -71,7 +71,7 @@ <h3>Assigning keys to contacts</h3>
                 To view a list of all currently known public keys, either through received signed presence or set manually.
             </p>
             <pre><code>/pgp contacts</code></pre>
-            <img src="../../images/pgp/contacts.png"/><br><br>
+            <img src="../../images/pgp/contacts.webp"/><br><br>
         </section>
         <section>
             <a name="sending"></a>
@@ -85,7 +85,7 @@ <h3>Sending PGP encrypted messages</h3>
                 If you are already in a conversation window without PGP, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/pgp start</code></pre>
-            <img src="../../images/pgp/sending.png"/><br><br>
+            <img src="../../images/pgp/sending.webp"/><br><br>
         </section>
         <section>
             <a name="receiving"></a>
@@ -94,7 +94,7 @@ <h3>Receiving PGP encrypted messages</h3>
             <p>
                 Assuming a public key is associated with the contact, they must also have enabled PGP encryption at their end.
             </p>
-            <img src="../../images/pgp/receiving.png"/><br><br>
+            <img src="../../images/pgp/receiving.webp"/><br><br>
         </section>
         <section>
             <a name="ending"></a>
@@ -104,11 +104,11 @@ <h3>Ending PGP encryption</h3>
                 To stop sending PGP encrypted messages to a contact:
             </p>
             <pre><code>/pgp end</code></pre>
-            <img src="../../images/pgp/endingsend.png"/><br><br>
+            <img src="../../images/pgp/endingsend.webp"/><br><br>
             <p>
                 The contact may also end PGP encryption at their end at any time.
             </p>
-            <img src="../../images/pgp/endingrecv.png"/><br><br>
+            <img src="../../images/pgp/endingrecv.webp"/><br><br>
         </section>
         <section>
             <a name="ui-opts"></a>
@@ -117,25 +117,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a href="otr.html">OTR</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png"/><br><br>
+            <img src="../../images/pgp/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png"/><br><br>
+            <img src="../../images/pgp/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png"/><br><br>
+            <img src="../../images/pgp/plainchar.webp"/><br><br>
             <p>
                 By default PGP encrypted messages are preceded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/pgp/pgpchar.png"/><br><br>
+            <img src="../../images/pgp/pgpchar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/pgp char</code> command.
             </p>
             <pre><code>/pgp char P</code></pre>
-            <img src="../../images/pgp/newchar.png"/><br><br>
+            <img src="../../images/pgp/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="pgp-message-logging"></a>
diff --git a/guide/0180/rooms.html b/guide/0180/rooms.html
index 272c5fd..0079911 100644
--- a/guide/0180/rooms.html
+++ b/guide/0180/rooms.html
@@ -69,7 +69,7 @@ <h3>Creating a chat room</h3>
                     Room Configuration and Administration</a>.</p>
 
             <p>If you are using Google Talk, creating a new room is slightly different. See the <a
-                    href="faq.html#gtalkrooms">FAQ</a>.</p>
+                    href="../../../faq.html#will-profanity-work-with-google-talk">FAQ</a>.</p>
         </section>
         <section>
             <a name="changing-your-nickname"></a>
@@ -138,4 +138,4 @@ <h3>Bookmarking rooms</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/070/install.html b/guide/070/install.html
index acfd6e7..6eee2f5 100644
--- a/guide/070/install.html
+++ b/guide/070/install.html
@@ -126,7 +126,7 @@ <h3>Linux/*BSD</h3>
                 </tr>
             </table>
             <p>To add to this list, submit a pull request to the <a
-                    href="https://github.com/boothj5/www_profanity_im/blob/master/install.html" target="_blank">website
+                    href="https://github.com/profanity-im/profanity-im.github.io/" target="_blank">website
                     source</a>, or email the <a href="https://lists.notraces.net/mailman/listinfo/profanity"
                     target="_blank">Mailing list</a> with details.</p>
         </section>
diff --git a/guide/070/omemo.html b/guide/070/omemo.html
index 7905b84..054973f 100644
--- a/guide/070/omemo.html
+++ b/guide/070/omemo.html
@@ -78,7 +78,7 @@ <h4>Generating Crypto Materials</h4>
             <p>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as <code>haveged</code>, to increase the available entropy.
             </p>
-            <img  src="../../images/omemo/key_generated.png"/><br><br>
+            <img  src="../../images/omemo/key_generated.webp"/><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again. If you want to check your own fingerprint or see the fingerprints of your other devices type:
             </p>
@@ -98,12 +98,12 @@ <h4>Fingerprint authentication</h4>
                 You should exchange fingerprints with your contact's via another secure communication channel. To display your fingerprint, use the following command:
             </p>
             <pre><code>/omemo fingerprint</code></pre>
-            <img src="../../images/omemo/myfp.png"/><br><br>
+            <img src="../../images/omemo/myfp.webp"/><br><br>
             <p>
                 To view the fingerprint of a contact use the following command:
             </p>
             <pre><code>/omemo fingerprint bob</code></pre>
-            <img src="../../images/omemo/theirfp.png"/><br><br>
+            <img src="../../images/omemo/theirfp.webp"/><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually authenticate the contact with the following command:
             </p>
@@ -127,7 +127,7 @@ <h3>Starting a private conversation</h3>
                 If you are already in a conversation window without OMEMO, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/omemo start bob</code></pre>
-            <img src="../../images/omemo/started.png"/><br><br>
+            <img src="../../images/omemo/started.webp"/><br><br>
             <p>
                 The <code>[OMEMO]</code> shown in the titlebar indicates that the conversation is now encrypted.
             </p>
@@ -159,25 +159,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used.
             </p>
-            <img src="../../images/omemo/encwarn.png"/><br><br>
+            <img src="../../images/omemo/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/omemo/encwarnoff.png"/><br><br>
+            <img src="../../images/omemo/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/omemo/plainchar.png"/><br><br>
+            <img src="../../images/omemo/plainchar.webp"/><br><br>
             <p>
                 By default OMEMO encrypted messages are preceeded by the '<code>*</code>' character.
             </p>
-            <img src="../../images/omemo/omemochar.png"/><br><br>
+            <img src="../../images/omemo/omemochar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/omemo char</code> command.
             </p>
             <pre><code>/omemo char O</code></pre>
-            <img src="../../images/omemo/newchar.png"/><br><br>
+            <img src="../../images/omemo/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="omemo-message-logging"></a>
diff --git a/guide/070/otr.html b/guide/070/otr.html
index cbb586e..419489a 100644
--- a/guide/070/otr.html
+++ b/guide/070/otr.html
@@ -83,7 +83,7 @@ <h3>Generating a private key</h3>
             <p>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as <code>haveged</code>, to increase the available entropy.
             </p>
-            <img src="../../images/otr/key_generated.png"/><br><br>
+            <img src="../../images/otr/key_generated.webp"/><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again.
             </p>
@@ -102,7 +102,7 @@ <h3>Starting a private conversation</h3>
                 If you are already in a conversation window without OTR, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/otr start</code></pre>
-            <img src="../../images/otr/started.png"/><br><br>
+            <img src="../../images/otr/started.webp"/><br><br>
             <p>
                 The <code>[untrusted]</code> shown in the titlebar indicates that although this conversation is encrypted, the contact has not yet been authenticated.
             </p>
@@ -135,20 +135,20 @@ <h4>Question and answer</h4>
             <p>
                 A message will be displayed showing that the authentication process has started.
             </p>
-            <img src="../../images/otr/question_sent.png"/><br><br>
+            <img src="../../images/otr/question_sent.webp"/><br><br>
             <p>
                 If Bob answers correctly a message will be shown indicating that Bob is now trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_success.png"/><br><br>
+            <img src="../../images/otr/question_received_success.webp"/><br><br>
             <p>
                 If Bob answers incorrectly a message will be shown indicating that Bob is not trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_fail.png"/><br><br>
+            <img src="../../images/otr/question_received_fail.webp"/><br><br>
             <p>
                 Bob may also wish to authenticate Alice. If he does, Alice will receive a message showing Bob's question, and prompting her to answer. Alice may answer using the <code>/otr answer</code> command:
             </p>
             <pre><code>/otr answer red</code></pre>
-            <img src="../../images/otr/bobquestion.png"/><br><br>
+            <img src="../../images/otr/bobquestion.webp"/><br><br>
             <p>
                 Note that question and answer authentication is a way for one contact to verify the identity of another. If the recipient answers correctly then the sender has authenticated them, however the recipient must also authenticate the sender with another question.
             </p>
@@ -165,13 +165,13 @@ <h4>Shared secret</h4>
             <p>
                 Bob enters the same secret using his client, Alice and Bob now trust each other.
             </p>
-            <img src="../../images/otr/secret_received_success.png"/><br><br>
+            <img src="../../images/otr/secret_received_success.webp"/><br><br>
 
             <p>
                 If Bob started the shared secret authentication, Alice will receive a message asking her to enter the secret using the <code>/otr secret</code> command:
             </p>
             <pre><code>/otr secret 5up3r53cr3t</code></pre>
-            <img src="../../images/otr/secret_sent_success.png"/><br><br>
+            <img src="../../images/otr/secret_sent_success.webp"/><br><br>
 
             <a name="fingerprints"></a>
             <h4>Manual fingerprint authentication</h4>
@@ -182,12 +182,12 @@ <h4>Manual fingerprint authentication</h4>
                 You should exchange fingerprints with your contact's via another secure communication channel. To display your fingerprint, use the following command:
             </p>
             <pre><code>/otr myfp</code></pre>
-            <img src="../../images/otr/myfp.png"/><br><br>
+            <img src="../../images/otr/myfp.webp"/><br><br>
             <p>
                 To view the fingerprint of a contact whilst in an OTR session, use the following command:
             </p>
             <pre><code>/otr theirfp</code></pre>
-            <img src="../../images/otr/theirfp.png"/><br><br>
+            <img src="../../images/otr/theirfp.webp"/><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually authenticate the contact with the following command:
             </p>
@@ -265,25 +265,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a href="pgp.html">PGP</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png"/><br><br>
+            <img src="../../images/pgp/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png"/><br><br>
+            <img src="../../images/pgp/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png"/><br><br>
+            <img src="../../images/pgp/plainchar.webp"/><br><br>
             <p>
                 By default OTR encrypted messages are preceeded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/otr/otrchar.png"/><br><br>
+            <img src="../../images/otr/otrchar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/otr char</code> command.
             </p>
             <pre><code>/otr char O</code></pre>
-            <img src="../../images/otr/newchar.png"/><br><br>
+            <img src="../../images/otr/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="otr-message-logging"></a>
diff --git a/guide/070/pgp.html b/guide/070/pgp.html
index 55454b3..2fdc519 100644
--- a/guide/070/pgp.html
+++ b/guide/070/pgp.html
@@ -50,7 +50,7 @@ <h3>Assigning a key to your account</h3>
             <p>
                 To allow contacts to send you PGP encrypted messages you must have a PGP key assigned to your account. To list all available keys on your system, use the command <code>/pgp keys</code>
             </p>
-            <img src="../../images/pgp/pgpkeys.png"/><br><br>
+            <img src="../../images/pgp/pgpkeys.webp"/><br><br>
             <p>
                 Set the account <code>pgpkeyid</code> property with the <a href="reference.html#account"><code>/account</code></a> command.
             </p>
@@ -71,7 +71,7 @@ <h3>Assigning keys to contacts</h3>
                 To view a list of all currently known public keys, either through received signed presence or set manually.
             </p>
             <pre><code>/pgp contacts</code></pre>
-            <img src="../../images/pgp/contacts.png"/><br><br>
+            <img src="../../images/pgp/contacts.webp"/><br><br>
         </section>
         <section>
             <a name="sending"></a>
@@ -85,7 +85,7 @@ <h3>Sending PGP encrypted messages</h3>
                 If you are already in a conversation window without PGP, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/pgp start</code></pre>
-            <img src="../../images/pgp/sending.png"/><br><br>
+            <img src="../../images/pgp/sending.webp"/><br><br>
         </section>
         <section>
             <a name="receiving"></a>
@@ -94,7 +94,7 @@ <h3>Receiving PGP encrypted messages</h3>
             <p>
                 Assuming a public key is associated with the contact, they must also have enabled PGP encryption at their end.
             </p>
-            <img src="../../images/pgp/receiving.png"/><br><br>
+            <img src="../../images/pgp/receiving.webp"/><br><br>
         </section>
         <section>
             <a name="ending"></a>
@@ -104,11 +104,11 @@ <h3>Ending PGP encryption</h3>
                 To stop sending PGP encrypted messages to a contact:
             </p>
             <pre><code>/pgp end</code></pre>
-            <img src="../../images/pgp/endingsend.png"/><br><br>
+            <img src="../../images/pgp/endingsend.webp"/><br><br>
             <p>
                 The contact may also end PGP encryption at their end at any time.
             </p>
-            <img src="../../images/pgp/endingrecv.png"/><br><br>
+            <img src="../../images/pgp/endingrecv.webp"/><br><br>
         </section>
         <section>
             <a name="ui-opts"></a>
@@ -117,25 +117,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a href="otr.html">OTR</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png"/><br><br>
+            <img src="../../images/pgp/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png"/><br><br>
+            <img src="../../images/pgp/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png"/><br><br>
+            <img src="../../images/pgp/plainchar.webp"/><br><br>
             <p>
                 By default PGP encrypted messages are preceded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/pgp/pgpchar.png"/><br><br>
+            <img src="../../images/pgp/pgpchar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/pgp char</code> command.
             </p>
             <pre><code>/pgp char P</code></pre>
-            <img src="../../images/pgp/newchar.png"/><br><br>
+            <img src="../../images/pgp/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="pgp-message-logging"></a>
diff --git a/guide/070/rooms.html b/guide/070/rooms.html
index 272c5fd..0079911 100644
--- a/guide/070/rooms.html
+++ b/guide/070/rooms.html
@@ -69,7 +69,7 @@ <h3>Creating a chat room</h3>
                     Room Configuration and Administration</a>.</p>
 
             <p>If you are using Google Talk, creating a new room is slightly different. See the <a
-                    href="faq.html#gtalkrooms">FAQ</a>.</p>
+                    href="../../../faq.html#will-profanity-work-with-google-talk">FAQ</a>.</p>
         </section>
         <section>
             <a name="changing-your-nickname"></a>
@@ -138,4 +138,4 @@ <h3>Bookmarking rooms</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/080/install.html b/guide/080/install.html
index 07d27f6..8c40788 100644
--- a/guide/080/install.html
+++ b/guide/080/install.html
@@ -133,7 +133,7 @@ <h3>Linux/*BSD</h3>
                 </tr>
             </table>
             <p>To add to this list, submit a pull request to the <a
-                    href="https://github.com/boothj5/www_profanity_im/blob/master/install.html" target="_blank">website
+                    href="https://github.com/profanity-im/profanity-im.github.io/" target="_blank">website
                     source</a>, or email the <a href="https://lists.notraces.net/mailman/listinfo/profanity"
                     target="_blank">Mailing list</a> with details.</p>
         </section>
diff --git a/guide/080/omemo.html b/guide/080/omemo.html
index 7905b84..054973f 100644
--- a/guide/080/omemo.html
+++ b/guide/080/omemo.html
@@ -78,7 +78,7 @@ <h4>Generating Crypto Materials</h4>
             <p>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as <code>haveged</code>, to increase the available entropy.
             </p>
-            <img  src="../../images/omemo/key_generated.png"/><br><br>
+            <img  src="../../images/omemo/key_generated.webp"/><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again. If you want to check your own fingerprint or see the fingerprints of your other devices type:
             </p>
@@ -98,12 +98,12 @@ <h4>Fingerprint authentication</h4>
                 You should exchange fingerprints with your contact's via another secure communication channel. To display your fingerprint, use the following command:
             </p>
             <pre><code>/omemo fingerprint</code></pre>
-            <img src="../../images/omemo/myfp.png"/><br><br>
+            <img src="../../images/omemo/myfp.webp"/><br><br>
             <p>
                 To view the fingerprint of a contact use the following command:
             </p>
             <pre><code>/omemo fingerprint bob</code></pre>
-            <img src="../../images/omemo/theirfp.png"/><br><br>
+            <img src="../../images/omemo/theirfp.webp"/><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually authenticate the contact with the following command:
             </p>
@@ -127,7 +127,7 @@ <h3>Starting a private conversation</h3>
                 If you are already in a conversation window without OMEMO, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/omemo start bob</code></pre>
-            <img src="../../images/omemo/started.png"/><br><br>
+            <img src="../../images/omemo/started.webp"/><br><br>
             <p>
                 The <code>[OMEMO]</code> shown in the titlebar indicates that the conversation is now encrypted.
             </p>
@@ -159,25 +159,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used.
             </p>
-            <img src="../../images/omemo/encwarn.png"/><br><br>
+            <img src="../../images/omemo/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/omemo/encwarnoff.png"/><br><br>
+            <img src="../../images/omemo/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/omemo/plainchar.png"/><br><br>
+            <img src="../../images/omemo/plainchar.webp"/><br><br>
             <p>
                 By default OMEMO encrypted messages are preceeded by the '<code>*</code>' character.
             </p>
-            <img src="../../images/omemo/omemochar.png"/><br><br>
+            <img src="../../images/omemo/omemochar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/omemo char</code> command.
             </p>
             <pre><code>/omemo char O</code></pre>
-            <img src="../../images/omemo/newchar.png"/><br><br>
+            <img src="../../images/omemo/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="omemo-message-logging"></a>
diff --git a/guide/080/otr.html b/guide/080/otr.html
index 93a64d6..0361955 100644
--- a/guide/080/otr.html
+++ b/guide/080/otr.html
@@ -95,7 +95,7 @@ <h3>Generating a private key</h3>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as
                 <code>haveged</code>, to increase the available entropy.
             </p>
-            <img src="../../images/otr/key_generated.png" /><br><br>
+            <img src="../../images/otr/key_generated.webp" /><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again.
             </p>
@@ -116,7 +116,7 @@ <h3>Starting a private conversation</h3>
                 the same command omitting the contact:
             </p>
             <pre><code>/otr start</code></pre>
-            <img src="../../images/otr/started.png" /><br><br>
+            <img src="../../images/otr/started.webp" /><br><br>
             <p>
                 The <code>[untrusted]</code> shown in the titlebar indicates that although this conversation is
                 encrypted, the contact has not yet been authenticated.
@@ -155,21 +155,21 @@ <h4>Question and answer</h4>
             <p>
                 A message will be displayed showing that the authentication process has started.
             </p>
-            <img src="../../images/otr/question_sent.png" /><br><br>
+            <img src="../../images/otr/question_sent.webp" /><br><br>
             <p>
                 If Bob answers correctly a message will be shown indicating that Bob is now trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_success.png" /><br><br>
+            <img src="../../images/otr/question_received_success.webp" /><br><br>
             <p>
                 If Bob answers incorrectly a message will be shown indicating that Bob is not trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_fail.png" /><br><br>
+            <img src="../../images/otr/question_received_fail.webp" /><br><br>
             <p>
                 Bob may also wish to authenticate Alice. If he does, Alice will receive a message showing Bob's
                 question, and prompting her to answer. Alice may answer using the <code>/otr answer</code> command:
             </p>
             <pre><code>/otr answer red</code></pre>
-            <img src="../../images/otr/bobquestion.png" /><br><br>
+            <img src="../../images/otr/bobquestion.webp" /><br><br>
             <p>
                 Note that question and answer authentication is a way for one contact to verify the identity of another.
                 If the recipient answers correctly then the sender has authenticated them, however the recipient must
@@ -190,14 +190,14 @@ <h4>Shared secret</h4>
             <p>
                 Bob enters the same secret using his client, Alice and Bob now trust each other.
             </p>
-            <img src="../../images/otr/secret_received_success.png" /><br><br>
+            <img src="../../images/otr/secret_received_success.webp" /><br><br>
 
             <p>
                 If Bob started the shared secret authentication, Alice will receive a message asking her to enter the
                 secret using the <code>/otr secret</code> command:
             </p>
             <pre><code>/otr secret 5up3r53cr3t</code></pre>
-            <img src="../../images/otr/secret_sent_success.png" /><br><br>
+            <img src="../../images/otr/secret_sent_success.webp" /><br><br>
 
             <a name="fingerprints"></a>
             <h4>Manual fingerprint authentication</h4>
@@ -210,12 +210,12 @@ <h4>Manual fingerprint authentication</h4>
                 display your fingerprint, use the following command:
             </p>
             <pre><code>/otr myfp</code></pre>
-            <img src="../../images/otr/myfp.png" /><br><br>
+            <img src="../../images/otr/myfp.webp" /><br><br>
             <p>
                 To view the fingerprint of a contact whilst in an OTR session, use the following command:
             </p>
             <pre><code>/otr theirfp</code></pre>
-            <img src="../../images/otr/theirfp.png" /><br><br>
+            <img src="../../images/otr/theirfp.webp" /><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually
                 authenticate the contact with the following command:
@@ -300,26 +300,26 @@ <h3>User Interface options</h3>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a
                     href="pgp.html">PGP</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png" /><br><br>
+            <img src="../../images/pgp/encwarn.webp" /><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a>
                 command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png" /><br><br>
+            <img src="../../images/pgp/encwarnoff.webp" /><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png" /><br><br>
+            <img src="../../images/pgp/plainchar.webp" /><br><br>
             <p>
                 By default OTR encrypted messages are preceeded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/otr/otrchar.png" /><br><br>
+            <img src="../../images/otr/otrchar.webp" /><br><br>
             <p>
                 This character can be changed using the <code>/otr char</code> command.
             </p>
             <pre><code>/otr char O</code></pre>
-            <img src="../../images/otr/newchar.png" /><br><br>
+            <img src="../../images/otr/newchar.webp" /><br><br>
         </section>
         <section>
             <a name="otr-message-logging"></a>
@@ -374,4 +374,4 @@ <h3>Importing OTR keys</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/080/pgp.html b/guide/080/pgp.html
index 55454b3..2fdc519 100644
--- a/guide/080/pgp.html
+++ b/guide/080/pgp.html
@@ -50,7 +50,7 @@ <h3>Assigning a key to your account</h3>
             <p>
                 To allow contacts to send you PGP encrypted messages you must have a PGP key assigned to your account. To list all available keys on your system, use the command <code>/pgp keys</code>
             </p>
-            <img src="../../images/pgp/pgpkeys.png"/><br><br>
+            <img src="../../images/pgp/pgpkeys.webp"/><br><br>
             <p>
                 Set the account <code>pgpkeyid</code> property with the <a href="reference.html#account"><code>/account</code></a> command.
             </p>
@@ -71,7 +71,7 @@ <h3>Assigning keys to contacts</h3>
                 To view a list of all currently known public keys, either through received signed presence or set manually.
             </p>
             <pre><code>/pgp contacts</code></pre>
-            <img src="../../images/pgp/contacts.png"/><br><br>
+            <img src="../../images/pgp/contacts.webp"/><br><br>
         </section>
         <section>
             <a name="sending"></a>
@@ -85,7 +85,7 @@ <h3>Sending PGP encrypted messages</h3>
                 If you are already in a conversation window without PGP, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/pgp start</code></pre>
-            <img src="../../images/pgp/sending.png"/><br><br>
+            <img src="../../images/pgp/sending.webp"/><br><br>
         </section>
         <section>
             <a name="receiving"></a>
@@ -94,7 +94,7 @@ <h3>Receiving PGP encrypted messages</h3>
             <p>
                 Assuming a public key is associated with the contact, they must also have enabled PGP encryption at their end.
             </p>
-            <img src="../../images/pgp/receiving.png"/><br><br>
+            <img src="../../images/pgp/receiving.webp"/><br><br>
         </section>
         <section>
             <a name="ending"></a>
@@ -104,11 +104,11 @@ <h3>Ending PGP encryption</h3>
                 To stop sending PGP encrypted messages to a contact:
             </p>
             <pre><code>/pgp end</code></pre>
-            <img src="../../images/pgp/endingsend.png"/><br><br>
+            <img src="../../images/pgp/endingsend.webp"/><br><br>
             <p>
                 The contact may also end PGP encryption at their end at any time.
             </p>
-            <img src="../../images/pgp/endingrecv.png"/><br><br>
+            <img src="../../images/pgp/endingrecv.webp"/><br><br>
         </section>
         <section>
             <a name="ui-opts"></a>
@@ -117,25 +117,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a href="otr.html">OTR</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png"/><br><br>
+            <img src="../../images/pgp/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png"/><br><br>
+            <img src="../../images/pgp/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png"/><br><br>
+            <img src="../../images/pgp/plainchar.webp"/><br><br>
             <p>
                 By default PGP encrypted messages are preceded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/pgp/pgpchar.png"/><br><br>
+            <img src="../../images/pgp/pgpchar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/pgp char</code> command.
             </p>
             <pre><code>/pgp char P</code></pre>
-            <img src="../../images/pgp/newchar.png"/><br><br>
+            <img src="../../images/pgp/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="pgp-message-logging"></a>
diff --git a/guide/080/rooms.html b/guide/080/rooms.html
index 272c5fd..0079911 100644
--- a/guide/080/rooms.html
+++ b/guide/080/rooms.html
@@ -69,7 +69,7 @@ <h3>Creating a chat room</h3>
                     Room Configuration and Administration</a>.</p>
 
             <p>If you are using Google Talk, creating a new room is slightly different. See the <a
-                    href="faq.html#gtalkrooms">FAQ</a>.</p>
+                    href="../../../faq.html#will-profanity-work-with-google-talk">FAQ</a>.</p>
         </section>
         <section>
             <a name="changing-your-nickname"></a>
@@ -138,4 +138,4 @@ <h3>Bookmarking rooms</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/090/install.html b/guide/090/install.html
index 07d27f6..8c40788 100644
--- a/guide/090/install.html
+++ b/guide/090/install.html
@@ -133,7 +133,7 @@ <h3>Linux/*BSD</h3>
                 </tr>
             </table>
             <p>To add to this list, submit a pull request to the <a
-                    href="https://github.com/boothj5/www_profanity_im/blob/master/install.html" target="_blank">website
+                    href="https://github.com/profanity-im/profanity-im.github.io/" target="_blank">website
                     source</a>, or email the <a href="https://lists.notraces.net/mailman/listinfo/profanity"
                     target="_blank">Mailing list</a> with details.</p>
         </section>
diff --git a/guide/090/omemo.html b/guide/090/omemo.html
index 7905b84..054973f 100644
--- a/guide/090/omemo.html
+++ b/guide/090/omemo.html
@@ -78,7 +78,7 @@ <h4>Generating Crypto Materials</h4>
             <p>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as <code>haveged</code>, to increase the available entropy.
             </p>
-            <img  src="../../images/omemo/key_generated.png"/><br><br>
+            <img  src="../../images/omemo/key_generated.webp"/><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again. If you want to check your own fingerprint or see the fingerprints of your other devices type:
             </p>
@@ -98,12 +98,12 @@ <h4>Fingerprint authentication</h4>
                 You should exchange fingerprints with your contact's via another secure communication channel. To display your fingerprint, use the following command:
             </p>
             <pre><code>/omemo fingerprint</code></pre>
-            <img src="../../images/omemo/myfp.png"/><br><br>
+            <img src="../../images/omemo/myfp.webp"/><br><br>
             <p>
                 To view the fingerprint of a contact use the following command:
             </p>
             <pre><code>/omemo fingerprint bob</code></pre>
-            <img src="../../images/omemo/theirfp.png"/><br><br>
+            <img src="../../images/omemo/theirfp.webp"/><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually authenticate the contact with the following command:
             </p>
@@ -127,7 +127,7 @@ <h3>Starting a private conversation</h3>
                 If you are already in a conversation window without OMEMO, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/omemo start bob</code></pre>
-            <img src="../../images/omemo/started.png"/><br><br>
+            <img src="../../images/omemo/started.webp"/><br><br>
             <p>
                 The <code>[OMEMO]</code> shown in the titlebar indicates that the conversation is now encrypted.
             </p>
@@ -159,25 +159,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used.
             </p>
-            <img src="../../images/omemo/encwarn.png"/><br><br>
+            <img src="../../images/omemo/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/omemo/encwarnoff.png"/><br><br>
+            <img src="../../images/omemo/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/omemo/plainchar.png"/><br><br>
+            <img src="../../images/omemo/plainchar.webp"/><br><br>
             <p>
                 By default OMEMO encrypted messages are preceeded by the '<code>*</code>' character.
             </p>
-            <img src="../../images/omemo/omemochar.png"/><br><br>
+            <img src="../../images/omemo/omemochar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/omemo char</code> command.
             </p>
             <pre><code>/omemo char O</code></pre>
-            <img src="../../images/omemo/newchar.png"/><br><br>
+            <img src="../../images/omemo/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="omemo-message-logging"></a>
diff --git a/guide/090/otr.html b/guide/090/otr.html
index 93a64d6..0361955 100644
--- a/guide/090/otr.html
+++ b/guide/090/otr.html
@@ -95,7 +95,7 @@ <h3>Generating a private key</h3>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as
                 <code>haveged</code>, to increase the available entropy.
             </p>
-            <img src="../../images/otr/key_generated.png" /><br><br>
+            <img src="../../images/otr/key_generated.webp" /><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again.
             </p>
@@ -116,7 +116,7 @@ <h3>Starting a private conversation</h3>
                 the same command omitting the contact:
             </p>
             <pre><code>/otr start</code></pre>
-            <img src="../../images/otr/started.png" /><br><br>
+            <img src="../../images/otr/started.webp" /><br><br>
             <p>
                 The <code>[untrusted]</code> shown in the titlebar indicates that although this conversation is
                 encrypted, the contact has not yet been authenticated.
@@ -155,21 +155,21 @@ <h4>Question and answer</h4>
             <p>
                 A message will be displayed showing that the authentication process has started.
             </p>
-            <img src="../../images/otr/question_sent.png" /><br><br>
+            <img src="../../images/otr/question_sent.webp" /><br><br>
             <p>
                 If Bob answers correctly a message will be shown indicating that Bob is now trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_success.png" /><br><br>
+            <img src="../../images/otr/question_received_success.webp" /><br><br>
             <p>
                 If Bob answers incorrectly a message will be shown indicating that Bob is not trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_fail.png" /><br><br>
+            <img src="../../images/otr/question_received_fail.webp" /><br><br>
             <p>
                 Bob may also wish to authenticate Alice. If he does, Alice will receive a message showing Bob's
                 question, and prompting her to answer. Alice may answer using the <code>/otr answer</code> command:
             </p>
             <pre><code>/otr answer red</code></pre>
-            <img src="../../images/otr/bobquestion.png" /><br><br>
+            <img src="../../images/otr/bobquestion.webp" /><br><br>
             <p>
                 Note that question and answer authentication is a way for one contact to verify the identity of another.
                 If the recipient answers correctly then the sender has authenticated them, however the recipient must
@@ -190,14 +190,14 @@ <h4>Shared secret</h4>
             <p>
                 Bob enters the same secret using his client, Alice and Bob now trust each other.
             </p>
-            <img src="../../images/otr/secret_received_success.png" /><br><br>
+            <img src="../../images/otr/secret_received_success.webp" /><br><br>
 
             <p>
                 If Bob started the shared secret authentication, Alice will receive a message asking her to enter the
                 secret using the <code>/otr secret</code> command:
             </p>
             <pre><code>/otr secret 5up3r53cr3t</code></pre>
-            <img src="../../images/otr/secret_sent_success.png" /><br><br>
+            <img src="../../images/otr/secret_sent_success.webp" /><br><br>
 
             <a name="fingerprints"></a>
             <h4>Manual fingerprint authentication</h4>
@@ -210,12 +210,12 @@ <h4>Manual fingerprint authentication</h4>
                 display your fingerprint, use the following command:
             </p>
             <pre><code>/otr myfp</code></pre>
-            <img src="../../images/otr/myfp.png" /><br><br>
+            <img src="../../images/otr/myfp.webp" /><br><br>
             <p>
                 To view the fingerprint of a contact whilst in an OTR session, use the following command:
             </p>
             <pre><code>/otr theirfp</code></pre>
-            <img src="../../images/otr/theirfp.png" /><br><br>
+            <img src="../../images/otr/theirfp.webp" /><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually
                 authenticate the contact with the following command:
@@ -300,26 +300,26 @@ <h3>User Interface options</h3>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a
                     href="pgp.html">PGP</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png" /><br><br>
+            <img src="../../images/pgp/encwarn.webp" /><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a>
                 command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png" /><br><br>
+            <img src="../../images/pgp/encwarnoff.webp" /><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png" /><br><br>
+            <img src="../../images/pgp/plainchar.webp" /><br><br>
             <p>
                 By default OTR encrypted messages are preceeded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/otr/otrchar.png" /><br><br>
+            <img src="../../images/otr/otrchar.webp" /><br><br>
             <p>
                 This character can be changed using the <code>/otr char</code> command.
             </p>
             <pre><code>/otr char O</code></pre>
-            <img src="../../images/otr/newchar.png" /><br><br>
+            <img src="../../images/otr/newchar.webp" /><br><br>
         </section>
         <section>
             <a name="otr-message-logging"></a>
@@ -374,4 +374,4 @@ <h3>Importing OTR keys</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/090/pgp.html b/guide/090/pgp.html
index 55454b3..2fdc519 100644
--- a/guide/090/pgp.html
+++ b/guide/090/pgp.html
@@ -50,7 +50,7 @@ <h3>Assigning a key to your account</h3>
             <p>
                 To allow contacts to send you PGP encrypted messages you must have a PGP key assigned to your account. To list all available keys on your system, use the command <code>/pgp keys</code>
             </p>
-            <img src="../../images/pgp/pgpkeys.png"/><br><br>
+            <img src="../../images/pgp/pgpkeys.webp"/><br><br>
             <p>
                 Set the account <code>pgpkeyid</code> property with the <a href="reference.html#account"><code>/account</code></a> command.
             </p>
@@ -71,7 +71,7 @@ <h3>Assigning keys to contacts</h3>
                 To view a list of all currently known public keys, either through received signed presence or set manually.
             </p>
             <pre><code>/pgp contacts</code></pre>
-            <img src="../../images/pgp/contacts.png"/><br><br>
+            <img src="../../images/pgp/contacts.webp"/><br><br>
         </section>
         <section>
             <a name="sending"></a>
@@ -85,7 +85,7 @@ <h3>Sending PGP encrypted messages</h3>
                 If you are already in a conversation window without PGP, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/pgp start</code></pre>
-            <img src="../../images/pgp/sending.png"/><br><br>
+            <img src="../../images/pgp/sending.webp"/><br><br>
         </section>
         <section>
             <a name="receiving"></a>
@@ -94,7 +94,7 @@ <h3>Receiving PGP encrypted messages</h3>
             <p>
                 Assuming a public key is associated with the contact, they must also have enabled PGP encryption at their end.
             </p>
-            <img src="../../images/pgp/receiving.png"/><br><br>
+            <img src="../../images/pgp/receiving.webp"/><br><br>
         </section>
         <section>
             <a name="ending"></a>
@@ -104,11 +104,11 @@ <h3>Ending PGP encryption</h3>
                 To stop sending PGP encrypted messages to a contact:
             </p>
             <pre><code>/pgp end</code></pre>
-            <img src="../../images/pgp/endingsend.png"/><br><br>
+            <img src="../../images/pgp/endingsend.webp"/><br><br>
             <p>
                 The contact may also end PGP encryption at their end at any time.
             </p>
-            <img src="../../images/pgp/endingrecv.png"/><br><br>
+            <img src="../../images/pgp/endingrecv.webp"/><br><br>
         </section>
         <section>
             <a name="ui-opts"></a>
@@ -117,25 +117,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a href="otr.html">OTR</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png"/><br><br>
+            <img src="../../images/pgp/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png"/><br><br>
+            <img src="../../images/pgp/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png"/><br><br>
+            <img src="../../images/pgp/plainchar.webp"/><br><br>
             <p>
                 By default PGP encrypted messages are preceded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/pgp/pgpchar.png"/><br><br>
+            <img src="../../images/pgp/pgpchar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/pgp char</code> command.
             </p>
             <pre><code>/pgp char P</code></pre>
-            <img src="../../images/pgp/newchar.png"/><br><br>
+            <img src="../../images/pgp/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="pgp-message-logging"></a>
diff --git a/guide/090/rooms.html b/guide/090/rooms.html
index 272c5fd..0079911 100644
--- a/guide/090/rooms.html
+++ b/guide/090/rooms.html
@@ -69,7 +69,7 @@ <h3>Creating a chat room</h3>
                     Room Configuration and Administration</a>.</p>
 
             <p>If you are using Google Talk, creating a new room is slightly different. See the <a
-                    href="faq.html#gtalkrooms">FAQ</a>.</p>
+                    href="../../../faq.html#will-profanity-work-with-google-talk">FAQ</a>.</p>
         </section>
         <section>
             <a name="changing-your-nickname"></a>
@@ -138,4 +138,4 @@ <h3>Bookmarking rooms</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/latest/install.html b/guide/latest/install.html
index ac691e0..2e4b5c6 100644
--- a/guide/latest/install.html
+++ b/guide/latest/install.html
@@ -65,13 +65,6 @@ <h3>Linux/*BSD</h3>
                             target="_blank">packages.debian.org</a>
                     </td>
                 </tr>
-                <tr>
-                    <td>Exherbo</td>
-                    <td>
-                        <a href="http://git.exherbo.org/summer/packages/net-im/profanity/index.html"
-                            target="_blank">git.exherbo.org</a>
-                    </td>
-                </tr>
                 <tr>
                     <td>Funtoo</td>
                     <td>
@@ -154,8 +147,8 @@ <h3>Linux/*BSD</h3>
                 </tr>
             </table>
             <p>To add to this list, submit a pull request to the <a
-                    href="https://github.com/boothj5/www_profanity_im/blob/master/install.html" target="_blank">website
-                    source</a>, or email the <a href="https://lists.notraces.net/mailman/listinfo/profanity"
+                    href="https://github.com/profanity-im/profanity-im.github.io/" target="_blank">website
+                    source</a>, or email the <a href="https://lists.posteo.de/listinfo/profanity"
                     target="_blank">Mailing list</a> with details.</p>
         </section>
         <section>
diff --git a/guide/latest/omemo.html b/guide/latest/omemo.html
index cafc639..0b9cc4a 100644
--- a/guide/latest/omemo.html
+++ b/guide/latest/omemo.html
@@ -78,7 +78,7 @@ <h4>Generating Crypto Materials</h4>
             <p>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as <code>haveged</code>, to increase the available entropy.
             </p>
-            <img  src="../../images/omemo/key_generated.png"/><br><br>
+            <img  src="../../images/omemo/key_generated.webp"/><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again. If you want to check your own fingerprint or see the fingerprints of your other devices type:
             </p>
@@ -98,12 +98,12 @@ <h4>Fingerprint authentication</h4>
                 You should exchange fingerprints with your contact's via another secure communication channel. To display your fingerprint, use the following command:
             </p>
             <pre><code>/omemo fingerprint</code></pre>
-            <img src="../../images/omemo/myfp.png"/><br><br>
+            <img src="../../images/omemo/myfp.webp"/><br><br>
             <p>
                 To view the fingerprint of a contact use the following command:
             </p>
             <pre><code>/omemo fingerprint bob</code></pre>
-            <img src="../../images/omemo/theirfp.png"/><br><br>
+            <img src="../../images/omemo/theirfp.webp"/><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually authenticate the contact with the following command:
             </p>
@@ -127,7 +127,7 @@ <h3>Starting a private conversation</h3>
                 If you are already in a conversation window without OMEMO, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/omemo start bob</code></pre>
-            <img src="../../images/omemo/started.png"/><br><br>
+            <img src="../../images/omemo/started.webp"/><br><br>
             <p>
                 The <code>[OMEMO]</code> shown in the titlebar indicates that the conversation is now encrypted.
             </p>
@@ -159,25 +159,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used.
             </p>
-            <img src="../../images/omemo/encwarn.png"/><br><br>
+            <img src="../../images/omemo/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/omemo/encwarnoff.png"/><br><br>
+            <img src="../../images/omemo/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/omemo/plainchar.png"/><br><br>
+            <img src="../../images/omemo/plainchar.webp"/><br><br>
             <p>
                 By default OMEMO encrypted messages are preceeded by the '<code>*</code>' character.
             </p>
-            <img src="../../images/omemo/omemochar.png"/><br><br>
+            <img src="../../images/omemo/omemochar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/omemo char</code> command.
             </p>
             <pre><code>/omemo char O</code></pre>
-            <img src="../../images/omemo/newchar.png"/><br><br>
+            <img src="../../images/omemo/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="omemo-message-logging"></a>
diff --git a/guide/latest/otr.html b/guide/latest/otr.html
index 93a64d6..0361955 100644
--- a/guide/latest/otr.html
+++ b/guide/latest/otr.html
@@ -95,7 +95,7 @@ <h3>Generating a private key</h3>
                 If the generation takes a long time you can try to move the mouse or install an entropy daemon, such as
                 <code>haveged</code>, to increase the available entropy.
             </p>
-            <img src="../../images/otr/key_generated.png" /><br><br>
+            <img src="../../images/otr/key_generated.webp" /><br><br>
             <p>
                 Once you have generated a key, you will not need to do so again.
             </p>
@@ -116,7 +116,7 @@ <h3>Starting a private conversation</h3>
                 the same command omitting the contact:
             </p>
             <pre><code>/otr start</code></pre>
-            <img src="../../images/otr/started.png" /><br><br>
+            <img src="../../images/otr/started.webp" /><br><br>
             <p>
                 The <code>[untrusted]</code> shown in the titlebar indicates that although this conversation is
                 encrypted, the contact has not yet been authenticated.
@@ -155,21 +155,21 @@ <h4>Question and answer</h4>
             <p>
                 A message will be displayed showing that the authentication process has started.
             </p>
-            <img src="../../images/otr/question_sent.png" /><br><br>
+            <img src="../../images/otr/question_sent.webp" /><br><br>
             <p>
                 If Bob answers correctly a message will be shown indicating that Bob is now trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_success.png" /><br><br>
+            <img src="../../images/otr/question_received_success.webp" /><br><br>
             <p>
                 If Bob answers incorrectly a message will be shown indicating that Bob is not trusted by Alice.
             </p>
-            <img src="../../images/otr/question_received_fail.png" /><br><br>
+            <img src="../../images/otr/question_received_fail.webp" /><br><br>
             <p>
                 Bob may also wish to authenticate Alice. If he does, Alice will receive a message showing Bob's
                 question, and prompting her to answer. Alice may answer using the <code>/otr answer</code> command:
             </p>
             <pre><code>/otr answer red</code></pre>
-            <img src="../../images/otr/bobquestion.png" /><br><br>
+            <img src="../../images/otr/bobquestion.webp" /><br><br>
             <p>
                 Note that question and answer authentication is a way for one contact to verify the identity of another.
                 If the recipient answers correctly then the sender has authenticated them, however the recipient must
@@ -190,14 +190,14 @@ <h4>Shared secret</h4>
             <p>
                 Bob enters the same secret using his client, Alice and Bob now trust each other.
             </p>
-            <img src="../../images/otr/secret_received_success.png" /><br><br>
+            <img src="../../images/otr/secret_received_success.webp" /><br><br>
 
             <p>
                 If Bob started the shared secret authentication, Alice will receive a message asking her to enter the
                 secret using the <code>/otr secret</code> command:
             </p>
             <pre><code>/otr secret 5up3r53cr3t</code></pre>
-            <img src="../../images/otr/secret_sent_success.png" /><br><br>
+            <img src="../../images/otr/secret_sent_success.webp" /><br><br>
 
             <a name="fingerprints"></a>
             <h4>Manual fingerprint authentication</h4>
@@ -210,12 +210,12 @@ <h4>Manual fingerprint authentication</h4>
                 display your fingerprint, use the following command:
             </p>
             <pre><code>/otr myfp</code></pre>
-            <img src="../../images/otr/myfp.png" /><br><br>
+            <img src="../../images/otr/myfp.webp" /><br><br>
             <p>
                 To view the fingerprint of a contact whilst in an OTR session, use the following command:
             </p>
             <pre><code>/otr theirfp</code></pre>
-            <img src="../../images/otr/theirfp.png" /><br><br>
+            <img src="../../images/otr/theirfp.webp" /><br><br>
             <p>
                 If the fingerprint you see matches the fingerprint you communicated via another means, you can manually
                 authenticate the contact with the following command:
@@ -300,26 +300,26 @@ <h3>User Interface options</h3>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a
                     href="pgp.html">PGP</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png" /><br><br>
+            <img src="../../images/pgp/encwarn.webp" /><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a>
                 command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png" /><br><br>
+            <img src="../../images/pgp/encwarnoff.webp" /><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceeded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png" /><br><br>
+            <img src="../../images/pgp/plainchar.webp" /><br><br>
             <p>
                 By default OTR encrypted messages are preceeded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/otr/otrchar.png" /><br><br>
+            <img src="../../images/otr/otrchar.webp" /><br><br>
             <p>
                 This character can be changed using the <code>/otr char</code> command.
             </p>
             <pre><code>/otr char O</code></pre>
-            <img src="../../images/otr/newchar.png" /><br><br>
+            <img src="../../images/otr/newchar.webp" /><br><br>
         </section>
         <section>
             <a name="otr-message-logging"></a>
@@ -374,4 +374,4 @@ <h3>Importing OTR keys</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/guide/latest/pgp.html b/guide/latest/pgp.html
index 55454b3..2fdc519 100644
--- a/guide/latest/pgp.html
+++ b/guide/latest/pgp.html
@@ -50,7 +50,7 @@ <h3>Assigning a key to your account</h3>
             <p>
                 To allow contacts to send you PGP encrypted messages you must have a PGP key assigned to your account. To list all available keys on your system, use the command <code>/pgp keys</code>
             </p>
-            <img src="../../images/pgp/pgpkeys.png"/><br><br>
+            <img src="../../images/pgp/pgpkeys.webp"/><br><br>
             <p>
                 Set the account <code>pgpkeyid</code> property with the <a href="reference.html#account"><code>/account</code></a> command.
             </p>
@@ -71,7 +71,7 @@ <h3>Assigning keys to contacts</h3>
                 To view a list of all currently known public keys, either through received signed presence or set manually.
             </p>
             <pre><code>/pgp contacts</code></pre>
-            <img src="../../images/pgp/contacts.png"/><br><br>
+            <img src="../../images/pgp/contacts.webp"/><br><br>
         </section>
         <section>
             <a name="sending"></a>
@@ -85,7 +85,7 @@ <h3>Sending PGP encrypted messages</h3>
                 If you are already in a conversation window without PGP, you can start sending encrypted messages with the same command omitting the contact:
             </p>
             <pre><code>/pgp start</code></pre>
-            <img src="../../images/pgp/sending.png"/><br><br>
+            <img src="../../images/pgp/sending.webp"/><br><br>
         </section>
         <section>
             <a name="receiving"></a>
@@ -94,7 +94,7 @@ <h3>Receiving PGP encrypted messages</h3>
             <p>
                 Assuming a public key is associated with the contact, they must also have enabled PGP encryption at their end.
             </p>
-            <img src="../../images/pgp/receiving.png"/><br><br>
+            <img src="../../images/pgp/receiving.webp"/><br><br>
         </section>
         <section>
             <a name="ending"></a>
@@ -104,11 +104,11 @@ <h3>Ending PGP encryption</h3>
                 To stop sending PGP encrypted messages to a contact:
             </p>
             <pre><code>/pgp end</code></pre>
-            <img src="../../images/pgp/endingsend.png"/><br><br>
+            <img src="../../images/pgp/endingsend.webp"/><br><br>
             <p>
                 The contact may also end PGP encryption at their end at any time.
             </p>
-            <img src="../../images/pgp/endingrecv.png"/><br><br>
+            <img src="../../images/pgp/endingrecv.webp"/><br><br>
         </section>
         <section>
             <a name="ui-opts"></a>
@@ -117,25 +117,25 @@ <h3>User Interface options</h3>
             <p>
                 By default, an indicator is displayed in the titlebar when no encryption is being used (including <a href="otr.html">OTR</a> and <a href="omemo.html">OMEMO</a>).
             </p>
-            <img src="../../images/pgp/encwarn.png"/><br><br>
+            <img src="../../images/pgp/encwarn.webp"/><br><br>
             <p>
                 This indicator can be removed using the <a href="reference.html#encwarn"><code>/encwarn</code></a> command.
             </p>
             <pre><code>/encwarn off</code></pre>
-            <img src="../../images/pgp/encwarnoff.png"/><br><br>
+            <img src="../../images/pgp/encwarnoff.webp"/><br><br>
             <p>
                 Both incoming and outgoing plaintext messages are always preceded by the '<code>-</code>' character.
             </p>
-            <img src="../../images/pgp/plainchar.png"/><br><br>
+            <img src="../../images/pgp/plainchar.webp"/><br><br>
             <p>
                 By default PGP encrypted messages are preceded by the '<code>~</code>' character.
             </p>
-            <img src="../../images/pgp/pgpchar.png"/><br><br>
+            <img src="../../images/pgp/pgpchar.webp"/><br><br>
             <p>
                 This character can be changed using the <code>/pgp char</code> command.
             </p>
             <pre><code>/pgp char P</code></pre>
-            <img src="../../images/pgp/newchar.png"/><br><br>
+            <img src="../../images/pgp/newchar.webp"/><br><br>
         </section>
         <section>
             <a name="pgp-message-logging"></a>
diff --git a/guide/latest/rooms.html b/guide/latest/rooms.html
index 272c5fd..0079911 100644
--- a/guide/latest/rooms.html
+++ b/guide/latest/rooms.html
@@ -69,7 +69,7 @@ <h3>Creating a chat room</h3>
                     Room Configuration and Administration</a>.</p>
 
             <p>If you are using Google Talk, creating a new room is slightly different. See the <a
-                    href="faq.html#gtalkrooms">FAQ</a>.</p>
+                    href="../../../faq.html#will-profanity-work-with-google-talk">FAQ</a>.</p>
         </section>
         <section>
             <a name="changing-your-nickname"></a>
@@ -138,4 +138,4 @@ <h3>Bookmarking rooms</h3>
     </footer>
 </body>
 
-</html>
\ No newline at end of file
+</html>
diff --git a/index.md b/index.md
index add7e9e..8ef6d5c 100644
--- a/index.md
+++ b/index.md
@@ -12,10 +12,10 @@ Do you like Profanity?
 Consider [donating](donate.html)!  
 
 **Latest release:**
-**[profanity-${version}.tar.xz](tarballs/profanity-${version}.tar.xz id="download-tarball")**  
+**[profanity-${version}.tar.xz](tarballs/profanity-${version}.tar.xz)**  
 sha256:  <span class="hash">${tar_xz_sha256}</span>  
   
-**[profanity-${version}.zip](tarballs/profanity-${version}.zip id="download-zip")**  
+**[profanity-${version}.zip](tarballs/profanity-${version}.zip)**  
 sha256:  <span class="hash">${zip_sha256}</span>  
 
 **Documentation:**  
diff --git a/pagesource/faq.md b/pagesource/faq.md
index 41238c3..c906757 100644
--- a/pagesource/faq.md
+++ b/pagesource/faq.md
@@ -10,7 +10,7 @@ ${section_start}
 - [Why are my settings not persistent?](#why-are-my-settings-not-persistent)
 - [Where is the profrc file format described?](#where-is-the-profrc-file-format-described)
 - [Will Profanity run on &lt;some platform&gt;?](#will-profanity-run-on-some-platform)
-- [Will Profanity work with Google Talk?](#will-profanity-work-with-google-gtalk)
+- [Will Profanity work with Google Talk?](#will-profanity-work-with-google-talk)
 - [Will Profanity work with Facebook Chat?](#will-profanity-work-with-facebook-chat)
 - [Will Profanity work with Slack?](#will-profanity-work-with-slack)
 - [Will Profanity work with MSN/Yahoo/AIM/IRC etc?](#will-profanity-work-with-msnyahooirc-etc)
diff --git a/pagesource/helpout.md b/pagesource/helpout.md
index 6388d03..90434fc 100644
--- a/pagesource/helpout.md
+++ b/pagesource/helpout.md
@@ -5,22 +5,22 @@ ${section_start}
 
 ### Contents
 
-- [Use Profanity](use-profanity)
-- [Help with the website](website-help)
-- [Contribute code](contribute-code)
-- [Donate](donate)
+- [Use Profanity](#use-profanity)
+- [Help with the website](#help-with-the-website)
+- [Contribute code](#contribute-code)
+- [Donate](#donate)
 
 
 ${section_end}
 
 ${section_start}
 
-[](use-profanity)
+[](#use-profanity)
 ### Use Profanity
             
 The easiest way you can help out is just by using Profanity and sending any
 feedback you have to the
-[mailing list](https://lists.notraces.net/mailman/listinfo/profanity).
+[mailing list](https://lists.posteo.de/listinfo/profanity).
 Any feedback is welcome, although please keep it polite, and refrain from using
 profanity (pun intended).
 
@@ -31,7 +31,7 @@ ${section_end}
 
 ${section_start}
 
-[](website-help)
+[](#help-with-the-website)
 ### Help with the website
             
 The website often has small errors or omissions in documentation etc. The
@@ -46,7 +46,7 @@ ${section_end}
 
 ${section_start}
 
-[](contribute-code)
+[](#contribute-code)
 ### Contribute code
             
 Code contributions are always very welcome. From the small (spelling fixes) to
@@ -89,7 +89,7 @@ ${section_end}
 
 ${section_start}
 
-[](donate)
+[](#donate)
 ### Donate
 
 Yes, the rumors are true. Developers also have to eat. They also have limited
diff --git a/pagesource/plugins.md b/pagesource/plugins.md
index 409feef..ab53c25 100644
--- a/pagesource/plugins.md
+++ b/pagesource/plugins.md
@@ -7,7 +7,7 @@ ${section_start}
 
 - [Overview](#overview)
 - [Featured Plugins](#featured-plugins)
-- [Developing Plugins](developing-plugins)
+- [Developing Plugins](#developing-plugins)
 
      - [Python](#python),
      - [C](#c)

From 53859422d85aa9d6bf231afefe7b9a4e5e4c3ed4 Mon Sep 17 00:00:00 2001
From: Luca Matei Pintilie <luca@lucamatei.com>
Date: Mon, 27 Jul 2026 21:19:50 +0200
Subject: [PATCH 2/3] Update Slack compatibility status on FAQ page

---
 pagesource/faq.md | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/pagesource/faq.md b/pagesource/faq.md
index c906757..5127990 100644
--- a/pagesource/faq.md
+++ b/pagesource/faq.md
@@ -101,9 +101,8 @@ ${section_start}
 
 #### Will Profanity work with Slack?
 
-Provided the XMPP gateway has been enabled for your team, Profanity will work.
-See the
-[Slack page on gateways](https://slack.zendesk.com/hc/en-us/articles/201727913-Connecting-to-Slack-over-IRC-and-XMPP)
+No. [Slack has closed the XMPP gateway on May 15,
+2018](https://www.theregister.com/software/2018/03/09/slack-cuts-ties-to-irc-and-xmpp-cos-they-dont-speak-emoji/1048417)
 
 ##### [back to top](#top)
 

From b1ecd43a47c24176769a949b0290cd60331acf66 Mon Sep 17 00:00:00 2001
From: Luca Matei Pintilie <luca@lucamatei.com>
Date: Mon, 27 Jul 2026 21:20:04 +0200
Subject: [PATCH 3/3] Remove Bountysource from FAQ page

Bountysource's parent company has gone bankrupt and the site is no
longer available.
---
 pagesource/faq.md | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/pagesource/faq.md b/pagesource/faq.md
index 5127990..a939b2d 100644
--- a/pagesource/faq.md
+++ b/pagesource/faq.md
@@ -269,11 +269,6 @@ can ask for an IBAN via [email](mailto:jubalh@iodoru.org).
 We also got selected for GitHub Sponsors. You can find the link also on the
 *Sponsor* button on GitHub.
 
-There is also the possibility to set a bounty for certain issues via
-[Bountysource](https://www.bountysource.com/teams/profanity).
-So in case you want to see a certain feature implemented or bug fixed you can
-set a bounty there and the person doing the work gets the reward.
-
 ##### [back to top](#top)
 
 ${section_end}