You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/slides.md
+20-2Lines changed: 20 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,8 +44,6 @@ marp: true
44
44
45
45
# Using HTMX To Make Interactive Elements In Drupal
46
46
47
-
#### DrupalCamp England 2026
48
-
49
47
<!-- Speaker notes will appear here. -->
50
48
51
49
---
@@ -130,6 +128,23 @@ The state of the application is in the HTML, rather than kept external to it.
130
128
131
129
---
132
130
131
+
# HTMX Sucks?
132
+
133
+
- Crap code.
134
+
- No build tools.
135
+
- No Typescript.
136
+
- No components.
137
+
- etc. etc...
138
+
- Reference: https://htmx.org/essays/htmx-sucks/
139
+
140
+
<!--
141
+
- To address the elephant in the room.
142
+
- Ok, so HTMX doesn't solve all the problems, but what framework would?
143
+
- As a pragmatist, I like HTMX as it solves a problem and means we can move away from another proprietary JSON standard that is highly complex and poorly documented.
144
+
- Drupal is GOOD at producing HTML output.
145
+
-->
146
+
---
147
+
133
148
## Installing HTMX
134
149
135
150
Download and include the single JavaScript file.
@@ -215,6 +230,9 @@ class Htmx {
215
230
}
216
231
}
217
232
```
233
+
<!--
234
+
- Generally, you shouldn't need to detect that the request is a HTMX request, but Drupal makes use of it quite a bit.
0 commit comments