diff --git a/_posts/2021-02-15-boxes-v2.0.0-released.md b/_posts/2021-02-15-boxes-v2.0.0-released.md
new file mode 100644
index 0000000..4f06e3b
--- /dev/null
+++ b/_posts/2021-02-15-boxes-v2.0.0-released.md
@@ -0,0 +1,32 @@
+---
+layout: post
+title: "New release: boxes v2.0.0"
+date: 2021-02-15 22:00:00 +0100
+comments: false
+---
+
+**Version 2.0.0 is out**.
+A major update which brings Unicode support for input text and PCRE2 regular expressions.:
+
+- We finally have Unicode support for input and output text as per [#1](https://github.com/{{ site.github }}/issues/1).
+ In fact, most character sets on your system should now be supported. *Boxes* picks up your system encoding, but you
+ can override that by using `-n`, e.g. `-n UTF-8`.
+- We adopted [Semantic Versioning](https://semver.org). This is a new major release.
+- ANSI escape sequences are now supported in the input text. This means you can pipe your text through
+ [lolcat](https://github.com/busyloop/lolcat) and still get correct boxes around it.
+ Thanks to [residualmind](https://github.com/residualmind)!
+- The regular expression engine was upgraded to state-of-the-art [PCRE2](http://www.pcre.org/current/doc/html/).
+ This means you have more powerful regular expression syntax at your disposal. It also means that any backreferences
+ in your config file are now `$1` instead of `\1`.
+- Some deprecated box designs were dropped (*netdata*, *tjc*, *c-cmt3*, and *ccel*). If you miss them, you can get
+ them back from an [old
+ version](https://raw.githubusercontent.com/ascii-boxes/boxes/363e0266e083475b19f7539fd6beae699ade1890/boxes-config)
+ of the config file.
+
+- New box design 'jstone' by [Ed Schaller](https://github.com/schallee)
+- [Mike Meyer](https://github.com/meyer)'s 'unicornthink' box design now allows smaller speech bubbles
+- New box design 'bear'
+
+The detailed changes can be seen in the [commit history](https://github.com/{{ site.github }}/commits/master).
+
+[[Release History]({{ site.baseurl}}/docs/releases.html)]
diff --git a/docs/releases.html b/docs/releases.html
index fb352f9..0f8a3ea 100644
--- a/docs/releases.html
+++ b/docs/releases.html
@@ -17,73 +17,71 @@ So far, there were these stable releases:
| Src |
Binaries |
Bin |
+ Remark |
+
+ | 2.0.0 |
+ February 15, 2021 |
+ link |
+ link |
+ major update |
+
| 1.3 |
February 21, 2019 |
link |
link |
+ minor update |
| 1.2 |
March 16, 2017 |
link |
link |
+ |
| 1.1.2 |
January 16, 2015 |
link |
link |
+ |
| 1.1.1 |
October 19, 2012 |
link |
link |
+ |
| 1.1 |
July 23, 2006 |
link |
link |
+ new features |
| 1.0.1 |
March 18, 2000 |
link |
link |
+ important maintenance |
| 1.0 |
August 22, 1999 |
link |
link |
+ |
Sources and binaries for these releases are available from the above table.
-## When to upgrade
-
-Boxes has been around a long time, and it has been very stable. Sometimes, new releases are still
-required to ensure that *boxes* continues to compile smoothly on a large number of platforms.
-Whether or not you should upgrade to a new version depends on what you've got, and what you want
-to do:
-
-- **Building from Source:** If you want to [build from source]({{ site.baseurl}}/build.html), you
- should always use the latest sources from the above table. You may also clone the repo and build
- the bleeding edge. Since we have a stable master branch, this will also get you a good build, but
- it will be a snapshot version.
-
-- **Using a binary:** The last major functional enhancements were in version 1.1 (of 2006). So if
- you've got a working 1.1 binary on your system, you're good and you don't really need to upgrade.
- Staying on the even older 1.0.1 will mean that you're missing features (such as better tab
- handling and the 'mend' option). Anything prior to 1.0.1 should definitely be upgraded.
-
Note that you can always copy the [latest box designs](https://github.com/{{ site.github }}/blob/master/boxes-config)
from GitHub to replace your older *boxes-config* (Unix) or *boxes.cfg* (Windows) - the designs
are backwards compatible.