diff --git a/handbook/troggle/trog2030.html b/handbook/troggle/trog2030.html
index 6ddc099a8..c00dea85c 100644
--- a/handbook/troggle/trog2030.html
+++ b/handbook/troggle/trog2030.html
@@ -188,19 +188,19 @@ asynchronously (this used to be called <a href=""https://en.wikipedia.org/wiki/A
 
     
 <p>We have been waiting for more than a decade and a half for <a href="trogspeculate.html">the JavaScript Framework mess</a> to sort itself out. We want to see where we could sensibly move to a front-end+back-end architecture, instead of redrawing every screen of data on the server (see above "<a href="#frontends">Things that could be a bit sticky 2 - front-end code</a>").
-  
+ <div class="onright">
+<figure  >
+<a href="https://blog.jetbrains.com/pycharm/2025/10/the-state-of-django-2025/">
+<img width=350 src="django-htmx.png"></a>
+<br><figcaption>HTMX becoming mainstream in Django</figcaption>
+</figure>
+</div> 
   <p>In 2024 it now looks as if we may be able to stretch the current architecture into a <a href="trogspeculate.html#frontends">post-Javascript</a> era entirely because Webassembly <a href="https://thenewstack.io/webassembly-4-predictions-for-2024/">continues to develop rapidly</a>. Or maybe future versions of HTML (see HTMX below) will do what we need.
     
     <p>HTMX now looks like it may evolve into replacing large chunks of what is now done with JavaScript packages (Angular, React, Vue.. and jQuery before them). See <a href="https://testdriven.io/blog/drf-vue-vs-django-htmx/">Django/HTMX</a>  article. For Django users particularly, HTMX seems to be <a href="https://blog.jetbrains.com/pycharm/2025/10/the-state-of-django-2025/">a very good fit</a> [2025].
 
         
-<div class="onright">
-<figure  >
-<a href="https://blog.jetbrains.com/pycharm/2025/10/the-state-of-django-2025/">
-<img width=350 src="django-htmx.png"></a>
-<br><figcaption>HTMX becoming mainstream</figcaption>
-</figure>
-</div>
+
      
 <p>Hotwire and <a href="https://turbo.hotwired.dev/">Turbo</a> now also look interesting as ways to gain responsiveness yet not tie us into a heavyweight JavaScript framework (Jan. 2025).