https://htmx.org logo
Powered by
# htmx-general
  • u
    Is tomorrow OK? (Im not near a PC now)
  • m
    Yep
  • m
    I'll play around w/ it locally too
  • s
    About "a forum": why not use GitHub discussions? It's free and Google can index the answers.
  • s
  • s
    I will buy the one who finds the first job opportunity containing htmx a family size pizza.
  • t
    this is not just about jobs
  • g
    What about “I’ll buy shares in the first company to post job opportunities in htmx…”
  • l
    ➕ for a forum. GitHub discussions have the nice bonus of making it easy to encourage folks to ask questions in the discussion instead of opening issues for things that aren't issues. (Personally I prefer Discourse, but that requires hosting and maintenance.)
  • g
    discourse apparently has free hosting for open source projects
  • g
  • l
    Ooh - thanks, I forgot about that. I recommend Discourse then 🙂 So much richer than GitHub discussions.
  • g
    Agreed
  • t
    ahem
  • t
    why not just use proper flarum
  • t
    instead of that rails bs
  • t
  • t
    it's from the same people who made fluxbb and esotalk
  • g
    i am in a community that uses flarum and it's not good
  • g
    discourse is much better
  • s
    Could you please elaborate why you prefer discourse?
  • g
    mostly UI reasons. discourse feels faster, flarum is client-heavy and has a few bugs
  • g
    for example if you use their split view, the list jumps back up when you click a topic
  • g
    There are so many. I’d recommend NOT having a dedicated Q/A forum. Nothing beats stack overflow.
  • g
    also information density is lower, flarum has a lot of excess whitespace (and i say this as someone who likes a lot of whitespace)
  • g
    this is more for things other than q/a
  • g
    feature suggestions, bikeshed discussions, project showcases, sharing blogposts and conference talks, microwaves, ...
  • l
    I ran into an issue yesterday with htmx divs not displaying in Safari (iPad and MacOS). I fixed by upgrading htmx from 1.3.2 to 1.4.1. Is there a general recommendation for how current to stay with htmx versions? Is there a way to just use the most recent all the time? Currently I'm including https://unpkg.com/htmx.org@1.4.1
  • a
    praise from my coworker when I showed him implementing a preview div using HTMX: "wow, htmx is really slick. This got me excited." Keep up the good work!
  • s
    Good question. Up to now I manage my backend dependencies with pip (python). From time to time I copy htmx minified into my git repo. Not perfect, but works. AFAIK this is called "vendoring"
1...324325326...1146Latest