If you're using Alpine, give the Alpine morph extension a try?

are there any crud-generators for htmx? similar to the scaffold in rails? is this a stupid idea (or maybe just stupid)?

I like the idea of this. I’ve used stuff like cookiecutter for this. But the CRUD part depends on the backend, which could vary significantly (express, PHP, ASP, Java, Python, etc) which is different from rails where it is the backend and knows about the database etc

you are right, yes. I was thinking of some crud-generator that targeted HTMX as part of the stack.

anyway, I think I will give it a try

Would you start with the assumption there’s a CRUD backend in place, and this would be the HTMX part for a general CRUD backend? Or would there be different ones for different stacks?

Hmm, my first thinking is to start with a specific stack that includes a specific backend... then I will see what I could generalize... But I am open to suggestions! 🙂

my vague idea is that various back ends will create generators or template projects w/ htmx integrated. this is, unfortunately, one of the bad aspects of being back-end agnostic, when compared with something like hotwire+rails

missing.backend ?

oof

maybe I should rename this to missing.ts https://github.com/dz4k/deno-htmx-starter/

speaking of, taking a bit of liberty here in #725789747212976259 to tell folks that @gorgeous-airport-54386 has released #941815579440992337 1.0: the idea of https://missing.style is: - To style vanilla HTML reasonably well, like classes-CSS libraries do - To provide a small, 80/20 set of utilities for building common UI patterns - To use ARIA attributes (rather than classes) where appropriate to drive styling (e.g. tabs) so that doing the right thing from an accessibility standpoint is encouraged - To provide a rich set of CSS variables so you can customize the look and feel programmatically You can include it on a site with this:

html
<link rel="stylesheet" href="https://the.missing.style/v1.0.0/missing.min.css">

missing.css is obviously, by design, bare bones when compared w/ something like bootstrap, and, by itself, is for small, internal or utility sites, but it can also be used as a base for a more elaborate, application-specific style sheet we have plans to use it as the basis for an upcoming commercial application we are working on. congrats @gorgeous-airport-54386 ! 🔥 🔥 🔥

needs a

v

in the URL

taken from https://missing.style/

fixed

@rich-autumn-98740 as a follow up, check out https://github.com/bigskysoftware/htmx/pull/1116

Hi, new to htmx so trying to get a high level view and how it could be used in company techstack. Is there an eCommerce implementation done by anyone? Also was interested in the sponsor support from ButterCMS. Does that mean their CMS works/integrates with htmx?

I don't have anything to show you, but anything "works" with htmx so long as it can return html. At a high level, you replace client-side templates with server-side templates. Instead of sending json data to the client and building the html with javascript, you build the html on the server and then the client just puts it where you want it to be.

e-commerce should be something htmx is extremely well suited for. I"m not sure how butter is using htmx, I will ask!

Is it wise to always gracefully degrade if Javascript is disabled so the HTML UI is at least functional when HTMX can't be used? Attached is a screen shot of simple tasks that can be completed or uncompleted. At the moment, they are checkbox tags (not wrapped in a form which could make an HTTP PATCH request). So if JavaScript (HTMX) is disabled, the HTTP PATCH request won't be made. Doing so would be a lot more forms embedded within the HTML document but maybe that's a good approach? Curious what the seams are -- where you draw the line -- in terms of DOM design in this regard when using HMTX as an architecture and supporting graceful degradation?

(opps, here's the sceenshot)

Fully featured graceful degradation is a question of requirements. Only you can decide, based on your app capabilities and expected user base, whether it's feasible to provide a fallback for all (or most of) interactions on the page

Answering specific question about checkboxes, you can't provide fallback, as patch requests are not supported as per HTML standard

you would have to do it through POST

furthermore, checkboxes can't trigger form submission without JS

as always, "it depends"(c)

Thanks, that makes sense. Are there any design guidelines that are documented anywhere on the site. I don't think graceful degradation is mentioned in the essays (https://htmx.org/essays). Maybe that's not the most appropriate place to look. Just curious if there are other sources to read up on this that might apply to this space. Ha, yeah, I'm using Rails as my framework so when I say PATCH/PUT I mean wrapped within an POST request. 😅 ...but, your right, HTTP doesn't support those methods directly.

oh, yeah, I heard that rails has a lot of cool stuff like that, but never worked with it myself