https://htmx.org logo
Powered by
# htmx-general
  • h
    and how would htmx fit into EG a web flow /squrespace/wix
  • t
    Actually htmx would be pretty easy to use with any flat-file cms I think. That's the world where non-devs typically actually make pages, with their WYSIWYG editors and such. All you'd have to make is pages that use an "empty" layout to be used as partials
  • h
    I agree I think it would actually be pretty easy once you got used to it
  • h
    you wouldn't even have to use an empty layout, just hx-select
  • h
    empty would be better probably
  • h
    I think there might be a good case for a reorg to the examples tab
  • h
    to say like " this is the simplest example -> these are the most complex"
  • h
    so people have a good one to start at
  • t
    @salmon-rain-71933 Sorry if I scared you off, that was definitely not my intention. Maybe if you have a general idea of the kind of thing you'd like to be able to do, we can go over if and how htmx would help you.
  • s
    Lmao I've learned my lesson 😬🤐 I'll get my hands dirty and make the series myself 😈
  • s
    I appreciate your explanations, Gone. You've given me a lot of topics to research
  • p
    If I use 
    hx-get
    instead of 
    href
    on an anchor tag, I assume that's going be bad for SEO, right? Is the recommended solution to add both attributes to every anchor tag that needs to do an HTMX request?
  • h
    I would suggest boosting an anchor tag
  • h
    what do you need that tag to do above and beyond boosting/normal transition?
  • p
    I was hoping not to use boost so I can check headers on the server side to see if this is a (non-boosted) htmx request. My goal is to serve 
    /docs/intro.html
    wrapped in a layout if it's a direct request and the same doc NOT wrapped in a layout if it's an htmx request.
  • m
    if you do head down this road and want a channel here dedicated to it for collaboration, let me know
  • p
    While we're on the topic of channels... I noticed there's no #express-htmx or even #node-htmx -- am I the only one? 🥺
  • w
    Apparently I'm blind and I can't find this on the GitHub: what's the current version of HTMX? Edit: oh, just checked the CHANGELOG
  • b
    1.7.1? I think the 
    unpkg@latest
    link will redirect to that at least
  • w
  • b
  • b
    Off by 0.0.1 error
  • t
    Wouldn't the headers work the same whether it's a boosted href or an hx-get?
  • b
    WRT a potential future tutorial, I think finding a way to start with just html would be a win. Skip the framework setup dance and just start sending html. Not sure what the best thing for that would be though. Maybe use Caddy (https://caddyserver.com)? I think that only starts to fall down when you want to return fragments or not based on the headers.
  • p
    Yeah but then there's no way to distinguish the request. For example, if the link to 
    /docs
    is in the main navbar, that will need to be wrapped in my layout. If you're already in the docs section and click the menu item link to 
    /docs/tutorial
    , that should not be wrapped in a layout. If boosted, then both requests will send the same headers so there's no way for me to know which is a full page request and which is an ajax-ey fragment request.
  • b
    Check the 
    hx-trigger
    header: https://htmx.org/docs/#request-headers
  • p
    Hmmm... not sure I'd be able to devise a generic enough system around this. What I'd really love is if I could just do something like this: 
    <a href="/docs/tutorial" hx-replace="#content" />
    ...and in my fantasy world, this will be the equivalent of: 
    <a href="/docs/tutorial" hx-get="/docs/tutorial" hx-target="#content" hx-select="#content" hx-swap="outerHTML">
  • b
    If you’ve boosted the link then you don’t need the 
    hx-get
    at least.
  • p
    Oh! Maybe I'm approaching this all wrong. I can actually get exactly what I want above with just a little more markup...
    Copy code
    <menu
  hx-boost="true"
  hx-target="#article"
  hx-select="#article"
  hx-swap="outerHTML"
>
  <a href="/docs/intro">Intro</a>
  <a href="/docs/tutorial">Tutorial</a>
</menu>
    This is great!!
  • p
    ...then there's no server-side parsing of headers magic required at all
1...655656657...1146Latest