It’s possible that not every enhancement for AI can be structured in a way that supports all of the web’s shared layers, but we should strive to do so first before reaching for solutions that only benefit AI and not the humans the web is supposed to serve.

cross-posted from: https://programming.dev/post/54211132

Hi people. I'm creating a system using HTMX
It's a server using clj-kit, which renders "components" using hiccup and HTMX based on the requests.
A component generator basically. But it also has some JSON APIs which return pure data.

The details don't matter. It just exposes REST APIs, user calls REST API with their own custom params and get their custom component.

The goal is so this can be used for progressive rewrite and enhancement of legacy systems, and the components to be usable in multiple systems, reducing work.
In order for the user of the system to be able to use these components, they should also add HTMX to their client, and call the service. for example

<div hx-get="https://component.service/componentx?data-url=https%3A%2F%2Fdata.source%2Fdata" hx-trigger="load">

This is the architecture I thought of. Is this ok? This HTMX article on security says it's not ok to call HTMX with external sources. So what is the best way you suggest to create such system?

I'm halfway through it already, but I would like to hear what others have to say and your suggestions. Maybe HTMX isn't the right choice at all? I felt like it is.

Thank you.

As of June 2026, the IETF has officially standardized the HTTP QUERY method (RFC 10008). It's the first new standard HTTP method since PATCH (2010).

TL;DR: Over two months, agents made roughly 268,000 tracked requests to our site. “AI traffic” turned out to be two very different clients that want opposite things: ChatGPT fetches rendered HTML and essentially never touches Markdown; Claude Code asks for Markdown 76% of the time and gets it through content negotiation. llms.txt, on the other hand, gets fetched almost entirely by bots that aren’t the AI assistants it’s meant for. And the one clever technique we recommended ourselves (the hidden hint for AI) got zero measurable hits.

source: https://jelly-ui.com/dist/jelly.js