From 8d62de1f62b924a5bcec363db81d609ff291e548 Mon Sep 17 00:00:00 2001
From: Andros Fenollosa <hi@andros.dev>
Date: Sat, 27 Dec 2025 10:08:29 +0100
Subject: [PATCH] Fix table display by converting to bullet lists

- Convert benchmark comparison table to bullet list format
- Convert technology comparison table to bullet list with pipe separators
- Add comprehensive table styling in CSS (prepared for future use)
- one.el backend (one-ox) does not support Org mode tables or HTML export blocks
- Workaround: use bullet lists which render correctly and maintain readability
---
 assets/css/main.css | 27 +++++++++++++++++++++++++++
 one.org             | 22 ++++++++--------------
 2 files changed, 35 insertions(+), 14 deletions(-)

diff --git a/assets/css/main.css b/assets/css/main.css
index afa0f73..f3f47b7 100644
--- a/assets/css/main.css
+++ b/assets/css/main.css
@@ -51,6 +51,33 @@ b {
     font-weight: bold;
 }
 
+table {
+    width: 100%;
+    border-collapse: collapse;
+    margin: var(--gap-l) 0;
+    background-color: rgba(217, 217, 217, 0.05);
+}
+
+table thead {
+    background-color: var(--color-brown);
+    color: var(--color-black);
+}
+
+table th,
+table td {
+    padding: var(--gap-s) var(--gap-m);
+    text-align: left;
+    border: 1px solid rgba(210, 158, 121, 0.3);
+}
+
+table tbody tr:hover {
+    background-color: rgba(217, 217, 217, 0.1);
+}
+
+table th {
+    font-weight: bold;
+}
+
 /* Components */
 
 .container {
diff --git a/one.org b/one.org
index 294f8ac..ad865a5 100644
--- a/one.org
+++ b/one.org
@@ -90,30 +90,24 @@ That's it! No page reload, no API endpoints, no REST, no GraphQL, no frontend fr
 
 ** Why Django LiveView?
 
-*** Performance that speaks for itself
-
 [[https://github.com/tanrax/django-interactive-frameworks-benchmark][Benchmarks]] show Django LiveView delivers the fastest response times among Django interactive frameworks:
 
 #+ATTR_HTML: :class center-block image image--benchmark
 [[#/img/benchmark-response-time.webp][Response Time Comparison]]
 
-| Framework | Technology | Response Time | Data Transfer | Use Case |
-|-----------+------------+---------------+---------------|----------|
-| **LiveView** | WebSockets | **9.35ms** | 450 bytes | Real-time dashboards, collaborative apps |
-| HTMX | AJAX | 16.48ms | ~37 KB | Modern UX with minimal JavaScript |
-| Unicorn | AJAX | 26.76ms | ~71 KB | Complex forms with reactive state |
-| SSR | POST + redirect | 47.25ms | ~8.5 KB | SEO-critical pages, traditional CRUD |
+- **LiveView** (WebSockets): **9.35ms**, 450 bytes - Real-time dashboards, collaborative apps
+- HTMX (AJAX): 16.48ms, ~37 KB - Modern UX with minimal JavaScript
+- Unicorn (AJAX): 26.76ms, ~71 KB - Complex forms with reactive state
+- SSR (POST + redirect): 47.25ms, ~8.5 KB - SEO-critical pages, traditional CRUD
 
 Django LiveView is approximately **43% faster than HTMX** and **80% faster than traditional SSR** through persistent WebSocket connectivity.
 
 *** Technology Comparison
 
-| Feature | LiveView | SSR | HTMX | Unicorn |
-|---------+----------+-----+------+---------|
-| **Transport** | WebSocket | HTTP | AJAX | AJAX |
-| **Update Type** | Real-time | Full reload | Partial | Reactive |
-| **Multi-user** | ✅ Broadcast | ❌ | ❌ | ❌ |
-| **Infrastructure** | Redis + Channels | Django only | Django only | Django only |
+- **Transport**: LiveView (WebSocket) | SSR (HTTP) | HTMX (AJAX) | Unicorn (AJAX)
+- **Update Type**: LiveView (Real-time) | SSR (Full reload) | HTMX (Partial) | Unicorn (Reactive)
+- **Multi-user**: LiveView (✅ Broadcast) | SSR (❌) | HTMX (❌) | Unicorn (❌)
+- **Infrastructure**: LiveView (Redis + Channels) | SSR (Django only) | HTMX (Django only) | Unicorn (Django only)
 
 *** What makes it different?