3 files changed, 32 insertions, 11 deletions
diff --git a/site/cleopatra.org b/site/cleopatra.org
index 0831621..c926c5a 100644
--- a/site/cleopatra.org
+++ b/site/cleopatra.org
@@ -1,4 +1,4 @@
-#+TITLE: A Series on Generating this Static Website
+#+TITLE: An Unfinished Series on How This Static Website Used to be Generating
 
 #+SERIES: ./meta.html
 #+SERIES_PREV: ./posts/Thanks.html
@@ -10,11 +10,12 @@ become out-dated. This is reminescent of documenting any software
 project, and I was aware at that time of a dedicated paradigm to
 prevent these kind of issues: [[http://www.literateprogramming.com/][literate programming]].
 
-I spent quite some time turning my custom toolchain into a literate program, so
-that its actual code source would actually be the write-ups I wanted to add to
-my website. This was an interesting challenge, since it meant *~cleopatra~*
-would have to generate itself before it could build my website. In other words,
-*~cleopatra~* achieves the bootstsrapping challenge!
+I spent quite some time turning my custom toolchain into a literate
+program, so that its actual code source would actually be the
+write-ups I wanted to add to my website. This was an interesting
+challenge, since it meant *~cleopatra~* would have to generate itself
+before it could build my website. In other words, *~cleopatra~*
+achieves the bootstsrapping challenge!
 
 I really enjoyed this first experiment with literate programming, and
 I started using *~cleopatra~* for other projects of mine where
@@ -28,9 +29,17 @@ bootstrap jump.”]. But the so-called generation processes I had
 written for *~cleopatra~* the first basically “just worked” with
 *~cleopatra~* the second.
 
-So, coming back to this series, it is just the very reason why I started using
-*~cleopatra~* in the first place: the generation processes used by this website,
-written as literate programs.
+Now, I don’t use *~cleopatra~* anymore. Literate programming is a fun
+paradigm, but I never took the time to actually document in depth most
+of the bits on how this website is built. So I took the various
+scripts extracted by *~cleopatra~*, and recreated a straightforward
+~makefile~ file on top of it. The nice thing is, it now takes way less
+time to build!
+
+Anyway, coming back to this series, it is just the very reason why I
+started using *~cleopatra~* in the first place: the generation
+processes I was using to generate this website, written as literate
+programs. If you are curious, you can have a look.
 
 - [[./cleopatra/dependencies.org][Installing Dependencies]] ::
 
diff --git a/site/meta.org b/site/meta.org
index d5ce4b4..318a6b7 100644
--- a/site/meta.org
+++ b/site/meta.org
@@ -15,9 +15,11 @@ pages you read.
   desire is at least to try keeping up-to-date a curated description
   of the most significant ones.
 
-- [[./cleopatra.org][A Series on Generating this Website]] ::
+- [[./cleopatra.org][An Unfinished Series on How This Static Website Used to be Generating]] ::
   At some point, I felt like the whole process of generating this
   website was interesting enough so that it would deserve a write-up
   of its own.  As a result, I spent quite some time turning my custom
   toolchain into a literate program, so that its actual code source
-  would actually be the write-ups I wanted to add to my website.
+  would actually be the write-ups I wanted to add to my website. I
+  don’t use said toolchain anymore, but the article remains, though
+  they are doomed to become more and more outdated.
diff --git a/site/news/index.html b/site/news/index.html
index 3e8842c..e21c51f 100644
--- a/site/news/index.html
+++ b/site/news/index.html
@@ -1,5 +1,15 @@
 <h1>News</h1>
 
+<h2>2022</h2>
+
+<ul>
+  <li>
+    On <strong>August 13, 2022</strong>, after more than two years of good services,
+    <a href="https://cleopatra.soap.coffee"><strong><code>cleopatra</code></strong></a>
+    is no longer used to build this website.
+  </li>
+</ul>
+
 <h2>2021</h2>
 
 <ul>