diff --git a/test/index.html b/test/index.html
index ea49d60f0..9abe5fa64 100644
--- a/test/index.html
+++ b/test/index.html
@@ -14,6 +14,7 @@
 <body style="padding:20px;font-family: sans-serif">
 
 <h1 style="margin-top: 40px">htmx.js test suite</h1>
+<p id="version-number">Version:&nbsp;</p>
 
 <h2>Scratch Page</h2>
 <ul>
@@ -40,6 +41,9 @@ <h2>Mocha Test Suite</h2>
   if (navigator.webdriver) {
     htmx.logAll = function () { }
   }
+
+  // Add the version number to the top
+  document.getElementById('version-number').innerText += htmx.version
 </script>
 
 <script class="mocha-init">
diff --git a/www/content/essays/_index.md b/www/content/essays/_index.md
index 6e1e371a7..7fa7b556d 100644
--- a/www/content/essays/_index.md
+++ b/www/content/essays/_index.md
@@ -15,6 +15,7 @@ page_template = "essay.html"
 * [Rescuing REST From the API Winter](https://intercoolerjs.org/2016/01/18/rescuing-rest.html)
 * [Taking HTML Seriously](https://intercoolerjs.org/2020/01/14/taking-html-seriously)
 * [REST Copypasta](@/essays/rest-copypasta.md)
+* [The #ViewSource Affordance](@/essays/right-click-view-source.md)
 
 ### Why Hypermedia? Why Multi-Page Applications?
 * [Hypermedia On Whatever you'd Like (HOWL)](@/essays/hypermedia-on-whatever-youd-like.md)
@@ -25,6 +26,7 @@ page_template = "essay.html"
 
 ### Building Hypermedia Applications
 * [A Real World React to htmx Port](@/essays/a-real-world-react-to-htmx-port.md)
+* [Another Real World React to htmx Port](@/essays/another-real-world-react-to-htmx-port.md)
 * [Hypermedia-Driven Applications (HDAs)](@/essays/hypermedia-driven-applications.md)
 * [Hypermedia Friendly Scripting](@/essays/hypermedia-friendly-scripting.md)
 * [10 Tips For Building SSR/HDA applications](@/essays/10-tips-for-SSR-HDA-apps.md)
diff --git a/www/content/essays/another-real-world-react-to-htmx-port.md b/www/content/essays/another-real-world-react-to-htmx-port.md
new file mode 100644
index 000000000..0646c14b4
--- /dev/null
+++ b/www/content/essays/another-real-world-react-to-htmx-port.md
@@ -0,0 +1,54 @@
++++
+title = "Another Real World React -> htmx Port"
+date = 2023-09-20
+updated = 2023-09-20
+[taxonomies]
+author = ["Carson Gross"]
+tag = ["posts"]
++++
+
+The [Mother of All htmx Demos](@/essays/a-real-world-react-to-htmx-port.md) you can see the real world results of a
+port from a React-based front end to an htmx-powered front end.  The results are very good, although we qualify the
+experience with the following:
+
+> These are eye-popping numbers, and they reflect the fact that the Contexte application is extremely amenable to
+hypermedia: it is a content-focused application that shows lots of text and images.  We would not expect every
+web application to see these sorts of numbers.
+> 
+> However, we _would_ expect _many_ applications to see dramatic improvements by adopting the hypermedia/htmx approach, at
+least for part of their system.
+
+As luck would have it, we have another application (again, based on Django on the server side) that has been ported from
+a React front end to an htmx front end: [OpenUnited](https://openunited.com/).
+
+Here is a graphic from the [original LinkedIn post](https://www.linkedin.com/feed/update/urn:li:activity:7109116330770878464/) 
+by Adrian McPhee, showing the total Lines of Code in the code base before and after the port:
+
+![Open United Before & After](/img/open_united_before_after_htmx.png)
+
+### Before/After Source Code
+
+A very nice aspect of this port is that, because OpenUnited is open source, in contrast with Contexte, the before and 
+after code is available to examine:
+
+Before: <https://github.com/OpenUnited/old-codebase>
+
+After: <https://github.com/OpenUnited/platform>
+
+## Executive Summary
+
+Here is a high-level summary of the port
+
+* They reduced the **code base size** by **61%** (31237 LOC to 12044 LOC)
+* They reduced the **total number of files** by **72%** (588 files to 163 files)
+* They reduced the **total number of file types** by **38%** (18 file types to 11 file types)
+* Subjectively, development velocity felt at least **5X** faster
+* Rather than prototyping in Figma and then porting to HTML, UX development was done directly in HTML
+
+## Analysis
+
+Once again we have some eye-popping results.  This is because the OpenUnited application is extremely 
+amenable to hypermedia: like Contexte, it is a content-focused application that shows lots of text and images.  
+
+This experience again demonstrates that, for at least a certain class of web applications, htmx and the hypermedia 
+architecture can be an excellent choice.
diff --git a/www/content/essays/right-click-view-source.md b/www/content/essays/right-click-view-source.md
new file mode 100644
index 000000000..89537cc0c
--- /dev/null
+++ b/www/content/essays/right-click-view-source.md
@@ -0,0 +1,182 @@
++++
+title = "The #ViewSource Affordance"
+date = 2023-09-21
+updated = 2023-09-21
+[taxonomies]
+author = ["Carson Gross"]
++++
+
+> Not for nothing, Hypercard presaged the web's critical "#ViewSource" affordance, which allowed people to copy,
+> modify, customize and improve on the things that they found delightful or useful.  This affordance was later adapted 
+> by other human-centered projects like #Scratch, and is a powerful tonic against #enshittification.
+> 
+> \-\-[Cory Doctorow @pluralistic@mamot.fr](https://twitter.com/doctorow/status/1701934612686196872)
+
+## Open Culture & The Web
+
+When people talk about open source software, that conversation is often dominated by
+[the Free Software Foundation's notion of free software](https://www.gnu.org/philosophy/free-sw.html):
+
+> “Free software” means software that respects users' freedom and community. Roughly, it means that the users have the 
+> freedom to run, copy, distribute, study, change and improve the software."
+
+This definition of free software has been a useful one and, through advocating for it, the FSF has gifted the world a 
+lot of wonderful open source software.
+
+Web applications, however, have always been an uncomfortable fit for this definition of free.  This is mainly
+for technical reasons: web applications involve a web browser interacting with a web server that is, typically, running
+on a remote system.
+
+At a fundamental level, the REST-ful architecture of the web was built around _hypermedia representations_ of remote
+resources:  browsers deal only with hypermedia representations provided by the server and, thus, have no visibility into
+the actual source of the code executing on the server side.
+
+Now, the web has certainly _leveraged_ free and open source software in its growth: browsers are typically (at least mostly)
+open source, server software is often open source, and so on.  And there are, of course, open source web applications
+that users may run for things like forums and so forth.
+
+However, from the standpoint of typical web application users, web applications are not free in the FSF sense of that
+term: the users are unable to see and modify the source of the server code that is being executed as they interact with
+the application via the browser.
+
+### Right-Click-View-Source As Culture
+
+Despite the fact that the web has a somewhat uncomfortable relationship with the notion of free software, the early web 
+none-the-less had a radically open _developer culture_. 
+
+In fact, in some important and practical ways, the early web had a _more_ open developer culture than what was achieved 
+by the free software movement.
+
+The [#ViewSource](https://en.wikipedia.org/wiki/View-source_URI_scheme) affordance available in browsers allowed people 
+to understand and "own", at least in an informal way, the web in a way that even most FSF-conforming applications could 
+not: you had direct access to the "source", or at least _part_ of the source, of the application available from 
+_within_ the application itself.  
+
+You could copy-and-paste (or save) the "source" (HTML, JavaScript & CSS) and start modifying it, without a complicated
+build tool chain or, indeed, without any tool chain at all.
+
+This radical openness of the web allowed many people, often not formally trained computer programmers, to learn how to 
+create web pages and applications in an ad hoc and informal way.  
+
+In strict free software terms, this was, of course, a compromise: as a user of a web application, you had no visibility 
+into how a server was constructing a given hypermedia response.
+
+But you could see _what_ the server was responding with: you could download and tweak it, poke and prod at it.  You could,
+if you were an advanced user, use browser tools to modify the application in place.  
+
+And, most importantly, you could _learn from it_, even if you couldn't see how the HTML was being produced.
+
+This radical openness of the client and network protocol, and the culture it produced, was a big part of the success
+of the early web.
+
+## Digital Enclosure vs. Technical Enclosure
+
+The [Enclosure Movement](https://en.wikipedia.org/wiki/Enclosure) was a period in English history when what were 
+previously [commons](https://en.wikipedia.org/wiki/Commons) were privatized.
+
+This was a traumatic event in English history, as evidenced by this poem by an 18th century anon:
+
+> The law locks up the man or woman
+> 
+> Who steals the goose from off the common,
+> 
+> But lets the greater felon loose
+> 
+> Who steals the common from the goose.
+>
+> --18th century anon
+
+In the last decade, the web has gone through a period of "Digital Enclosure", where ["Walled Gardens"](https://en.wikipedia.org/wiki/Closed_platform),
+such as Facebook & Twitter, have replaced the earlier, more open and more chaotic blogs and internet forums.
+
+### Technical Enclosure
+
+Many (most?) web developers have decried this trend.  
+
+However, despite recognizing the danger of an increasingly closed internet, many web developers don't consider their own
+technical decisions and how those decisions can also contribute to the disappearance of web's _culture_ of openness.
+
+Inadvertently (for the most part) technical trends and decisions in web development in the last two decades have lead
+to what we term a "Technical Enclosure" of the web, a processes whereby technical decisions chip away at the #ViewSource
+affordance that Cory Doctrow discusses in the opening quote of this article, an affordance that existed as a commons
+for early web developers.
+
+To see a stark example of the decline of the [#ViewSource](https://en.wikipedia.org/wiki/View-source_URI_scheme) affordance
+in web development and Technical Enclosure in action, we can look at what is perhaps the most popular web page on the 
+internet, [The Google Homepage](https://google.com).
+
+Here is the nearly complete source of that page from the year 2000, taken from 
+[the wayback machine](http://web.archive.org/web/20000229040250/http://www.google.com/):
+
+### Google in 2000
+<img src="/img/google-2000.png" alt="Google Source Code in 2000" style="border-radius: 12px; margin: 12px">
+
+In contrast, here is a random snapshot of roughly 1/100th of the current source code for the website:
+
+### Google in 2023
+<img src="/img/google-2023.png" alt="Google Source Code in 2023" style="border-radius: 12px; margin: 12px">
+
+These two screenshots dramatically demonstrate the decline in the effectiveness of the [#ViewSource](https://en.wikipedia.org/wiki/View-source_URI_scheme) affordance over time:
+yes, you can still right-click the page and view its underlying source, but making sense of the latter code would be
+challenging for even the most seasoned web developer.
+
+A new web developer would have almost no chance of deriving any value from doing so.
+
+Now, this is not to criticize the google engineer's technical decisions that lead to this situation _as technical 
+decisions_: obviously, despite similar appearances, the google homepage of 2023 is far more sophisticated than the one 
+available in 2000.
+
+The 2023 google homepage is going to be a lot more complicated than the 2000 page and, given the zeitgeist, it is going to 
+involve a lot of JavaScript.
+
+However, this is to point out that something deeply important about the early web has been lost, almost certainly 
+unintentionally, along the way: the ability to view the source of the page, make sense of what it is doing and, most 
+importantly, to learn from it.
+
+## Right-Click-View-Source Extremism
+
+Both [htmx](/) and [hyperscript](https://hyperscript.org) adhere to the [Locality of Behavior](@/essays/locality-of-behaviour.md)
+design principle.
+
+This principle states that:
+
+> The behaviour of a unit of code should be as obvious as possible by looking only at that unit of code
+
+The main technical advantage of Locality of Behavior is ease of maintenance, as outlined in the essay above.
+
+However, there is an important cultural benefit to the Locality of Behavior of htmx and hyperscript as well: **it restores
+the power of the [#ViewSource](https://en.wikipedia.org/wiki/View-source_URI_scheme) affordance on the web**.
+
+Consider [Hyperwordle](https://arhamjain.com/hyperwordle/), a hyperscript-based clone of the popular 
+[Wordle](https://www.nytimes.com/games/wordle/index.html) game, now owned by the New York Times.
+
+You can visit Hyperwordle, right click and view the source of it, and you will be presented with some HTML and hyperscript,
+all of which is, with a bit of effort, understandable.
+
+The  [#ViewSource](https://en.wikipedia.org/wiki/View-source_URI_scheme) affordance is effective in this case.
+
+Contrast this with the view-source experience of the Wordle implementation at the New York Times.
+
+Now, this is of course a bit unfair: the NYTimes version has a lot more functionality and is heavily optimized. Hyperwordle
+is a proof of concept and not being hammered by millions of users every day.
+
+Despite that qualification, Hyperwordle demonstrates a potential future for the web, a future where a culture of openness,
+of [#ViewSource](https://en.wikipedia.org/wiki/View-source_URI_scheme) politeness, is once again a touchstone of the
+culture of the web.
+
+## Prioritizing [#ViewSource](https://en.wikipedia.org/wiki/View-source_URI_scheme)
+
+Engineers who care about the open culture of the web should recognize that the threats to that culture come not only from
+Digital Enclosure by large, private companies of the most important pieces of the web.  
+
+They should also recognize the risks of Technical Enclosure, and the _non-technical_ value of the 
+[#ViewSource](https://en.wikipedia.org/wiki/View-source_URI_scheme) affordance in perpetuating the open culture of
+web development.  They should start thinking about making this affordance a priority in their technical decisions.  As
+with all priorities, this may involve trading off against other technical and even functional priorities during 
+application development.
+
+But if we don't stand up for [#ViewSource](https://en.wikipedia.org/wiki/View-source_URI_scheme), no one else will.
+
+<br/>
+
+<img src="/img/memes/viewsource.png" alt="Right Click View Source Guy" style="border-radius: 12px; margin: 12px">
\ No newline at end of file
diff --git a/www/content/webring.md b/www/content/webring.md
index 9580a6da9..5ac54eb15 100644
--- a/www/content/webring.md
+++ b/www/content/webring.md
@@ -105,6 +105,7 @@ title = "htmx webring"
   <tr><td><a rel="nofollow" target="_blank" href="https://vanillaweather.com/">Vanilla Weather</a></td><td>No ads. No tracking. Just the weather.</td></tr>
   <tr><td><a rel="nofollow" target="_blank" href="https://turboscribe.ai/">TurboScribe</a></td><td>TurboScribe’s mission is to deliver world-class AI transcription at an unbeatable price.</td></tr>
   <tr><td><a rel="nofollow" target="_blank" href="https://xrss.infogulch.com">XRSS</a></td><td>A simple RSS reader inspired by Google Reader</td></tr>
+  <tr><td><a rel="nofollow" target="_blank" href="https://openunited.com/">OpenUnited</a></td><td>A Digital Talent match-making platform</td></tr>
 </tbody>
 </table>
 </div>
diff --git a/www/static/img/google-2000.png b/www/static/img/google-2000.png
new file mode 100644
index 000000000..5af6013a1
Binary files /dev/null and b/www/static/img/google-2000.png differ
diff --git a/www/static/img/google-2023.png b/www/static/img/google-2023.png
new file mode 100644
index 000000000..e7cb97cba
Binary files /dev/null and b/www/static/img/google-2023.png differ
diff --git a/www/static/img/memes/viewsource.png b/www/static/img/memes/viewsource.png
index c59a0e6cd..eaabd7b6d 100644
Binary files a/www/static/img/memes/viewsource.png and b/www/static/img/memes/viewsource.png differ
diff --git a/www/static/img/open_united_before_after_htmx.png b/www/static/img/open_united_before_after_htmx.png
new file mode 100644
index 000000000..55a93a4f6
Binary files /dev/null and b/www/static/img/open_united_before_after_htmx.png differ
diff --git a/www/static/test/index.html b/www/static/test/index.html
index 42d5487e1..24c10ac58 100644
--- a/www/static/test/index.html
+++ b/www/static/test/index.html
@@ -14,6 +14,7 @@
 <body style="padding:20px;font-family: sans-serif">
 
 <h1 style="margin-top: 40px">htmx.js test suite</h1>
+<p id="version-number">Version:&nbsp;</p>
 
 <h2>Scratch Page</h2>
 <ul>
@@ -40,6 +41,9 @@ <h2>Mocha Test Suite</h2>
   if (navigator.webdriver) {
     htmx.logAll = function () { }
   }
+
+  // Add the version number to the top
+  document.getElementById('version-number').innerText += htmx.version
 </script>
 
 <script class="mocha-init">
diff --git a/www/themes/htmx-theme/static/css/site.css b/www/themes/htmx-theme/static/css/site.css
index d76bbc736..ee5b979b8 100644
--- a/www/themes/htmx-theme/static/css/site.css
+++ b/www/themes/htmx-theme/static/css/site.css
@@ -480,12 +480,10 @@ pre[class|="language"] {
   color: lightgray;
 }
 .zola-anchor {
-  font-size: 80%;
-  margin-left: -.75rem;
-  margin-right: .75rem;
-  color: var(--midBlue);
-
+  margin-left: -1.3rem;
+  margin-right: .3rem;
+  opacity: 40%;
 }
 .zola-anchor:hover {
-  color: var(--lightBlue);
+    opacity: 95%;
 }
diff --git a/www/themes/htmx-theme/templates/anchor-link.html b/www/themes/htmx-theme/templates/anchor-link.html
new file mode 100644
index 000000000..b67c4641f
--- /dev/null
+++ b/www/themes/htmx-theme/templates/anchor-link.html
@@ -0,0 +1 @@
+<a class="zola-anchor" href="#{{ id }}" aria-label="Anchor link for: {{ id }}">#</a>
\ No newline at end of file
