Idea for another Package

[amirsaam]

I really love the Swift-ish syntax of Elementary and Elementary-HTMX, in my research for the best stack to be used along side Vapor, I found that since HTMX is mostly for talking with server in HTML, but many things do not need this interaction but still many divs need to become reactive and JS-devs made a good solution for it as you may encounter it too, the AlpineJS, it may be big request but it may help the ecosystem to make Vapor+Elementary (with HTMX & AlpineJS) to become more reactive and dynamic web stack.

[amirsaam]

This way I do think we can utilise UI libraries like Pines that are based on Alpine and Tailwind and do not need server-side JS rendering like React libraries.

[sliemeobn]

my intention with elementary was to create the bare-bones package that can then be extended or built upon in other packages (ie: build your own component library on top)

it would be fantastic to see people experimenting how to create nice, bundled up libraries with batteries-included components!

[amirsaam]

Surely, we don't need to have recreate Pines in Swift (I think?), only if we have AlpineJS package just like HTMX of what you did, Pines is an import and use library with div classes but it needs Alpine tags to run.

[sliemeobn]

I totally agree and I am on the same mission!
alpine is a great little tool to throw in the mix for light-weight client-side interactivity.

what I am looking into for my own project is using web component libraries, and shoelace looks really nice.
I think rendering out the "big page" with server-side swift, using HTMX for laser-focused server interactions, and shoelace (or web components in general) can get you all the way for a lot of web apps.

also, I have it on my list to tinker with an elementary-based reactive DOM package that runs as WASM in the browser, but that is no small task...

[amirsaam]

TBH it's my first time hearing about Shoelace, and doesn't it a React library (based on what I've read on their website)? Are you take apart your front and back containers and creating each on their own isolated container?
If yes my proposal was to have Vapor as backend the frontend on same container with this stack cuz looks like they can be on same container cuz of no server-side JS rendering unlike React frameworks.

[sliemeobn]

shoelace has nothing to do with React, it's pre-packaged components that in any HTML page (using web components).
a bit like if you took a snippet of Pines and packaged it up in a nice custom HTML tag.

[amirsaam]

Oh, the "Framework" section draw my attention that's why I thought it's a React thing, interesting.
Me myself am a more Radix appreciator that's why I like Pine more.

[amirsaam]

VATHe Stack: Vapor+Alpine+Tailwind+HTMX (fenced area, in which the small cattle is herded together for the night (lol))
or
HATHe Stack: Hummingbird+Alpine+Tailwind+HTMX (third-person singular simple present indicative of [have])

(the lowercase "e" stands for "Elementary")

[sliemeobn]

I'm more of a hummingbird guy myself, but sure ; )

[amirsaam]

haha, it could be any first word ;)

[amirsaam]

No AlpineElementary?

[sliemeobn]

not yet, I use it in a project with elementary, but polishing up the API to make sense as a releasable package requires a bit of thinking.

also, I have been thinking about setting up a github org for elementary to collect all the packages under one umbrella. this could make the addition of community packages easier. but I am a bit short on playtime at the moment : /

[amirsaam]

I'm looking forward towards it no matter how long it does take <3

For the github org, it makes sense absolutely!

[erikbdev]

not yet, I use it in a project with elementary, but polishing up the API to make sense as a releasable package requires a bit of thinking.

@sliemeobn Are there any updates for Elementary + AlpineJS integration?

PS: Elementary is awesome :D

[sliemeobn]

sorry, at least none from my side.

I am a bit short on play time at the moment, but I am happy to collaborate if somebody wants to give it a go.