summaryrefslogtreecommitdiffstatshomepage
path: root/www/content/essays/is-htmx-another-javascript-framework.md
diff options
context:
space:
mode:
authorChristian Clauss <cclauss@me.com>2024-01-24 16:10:37 +0100
committerGitHub <noreply@github.com>2024-01-24 10:10:37 -0500
commit0b6769a257ac1bf50f3f7228f8a5be5964970f7e (patch)
tree228201ab928e8527e73b56a0c4afbc14bdae19a1 /www/content/essays/is-htmx-another-javascript-framework.md
parent22c8c345e4f90eae4ed12bf5bfe47b4154d1bbb8 (diff)
downloadhtmx-0b6769a257ac1bf50f3f7228f8a5be5964970f7e.tar.gz
htmx-0b6769a257ac1bf50f3f7228f8a5be5964970f7e.zip
Fix typos in markdown files (#2177)
Diffstat (limited to 'www/content/essays/is-htmx-another-javascript-framework.md')
-rw-r--r--www/content/essays/is-htmx-another-javascript-framework.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/www/content/essays/is-htmx-another-javascript-framework.md b/www/content/essays/is-htmx-another-javascript-framework.md
index 8060ccc6..d5917d61 100644
--- a/www/content/essays/is-htmx-another-javascript-framework.md
+++ b/www/content/essays/is-htmx-another-javascript-framework.md
@@ -66,7 +66,7 @@ Pushing the user to define the behavior of their application primarily in HTML,
No matter when you wrote your htmx application, however, the behavior of an htmx form has always been defined in largely the same way a regular HTML form is: with `<form>`. With htmx adding additional network functionality, you can finally use `PUT` requests and control where the response goes, but in all other respects—validation, inputs, labels, autocomplete—you have default `<form>` element behavior.
-Finally, because htmx simply extends HTML in a very narrow domain (network requests and DOM replacements), most of the "htmx" you write is just plain old HTML. When you have access to complex state management mechanisms, it's incredibly easy to implement a custom collapsable div; when you don't, you might stop long enough to search up the [`<details>`](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/details) element. Whenever a problem can be solved by native HTML elements, the longevity of the code improves tremendously as a result. This is a much less alienating way to learn web development, because the bulk of your knowledge will remain relevant as long as HTML does.
+Finally, because htmx simply extends HTML in a very narrow domain (network requests and DOM replacements), most of the "htmx" you write is just plain old HTML. When you have access to complex state management mechanisms, it's incredibly easy to implement a custom collapsible div; when you don't, you might stop long enough to search up the [`<details>`](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/details) element. Whenever a problem can be solved by native HTML elements, the longevity of the code improves tremendously as a result. This is a much less alienating way to learn web development, because the bulk of your knowledge will remain relevant as long as HTML does.
In this respect, htmx is much more like JQuery than React (htmx's predecessor, [intercooler.js](https://intercoolerjs.org/), was a JQuery extension), but it improves on JQuery by using a declarative, HTML-based interface: where JQuery made you go to the `<script>` tag to specify AJAX behavior, htmx requires only a simple `hx-post` attribute.