I've started writing up a coding guide for hypermedia-driven application architectures. #htmx
It's very much a work in progress. Some bits not started yet. But I'm quite happy with some of it...
https://hda.daz.is/architecture/why-hypermedia-driven-architecture/
More to come some!
#React is an obsolete tech and hopefully my guide, when done, will help people who want to switch to #HDA architecture from #spa
Hopefully the #Rust won't put people off.
The Fulcrum 🏴☠️ ⛓️💥 🛠️
boosted
From the archive! A Look At HTMX With PHP
In this article we will look at how to get HTMX working with a vanilla PHP backend. With a few examples of the two systems working together.
https://www.hashbangcode.com/article/look-htmx-php
This ties into a package just released that shows a lot of different examples of HTMX working with a PHP backend.
From the archive! A Look At HTMX With PHP
In this article we will look at how to get HTMX working with a vanilla PHP backend. With a few examples of the two systems working together.
https://www.hashbangcode.com/article/look-htmx-php
This ties into a package just released that shows a lot of different examples of HTMX working with a PHP backend.
@smallcircles To follow up on the discussion from yesterday, @evan has created a proposal for another kind of “event stream” that is not necessarily associated with *any* AP collection type (see Example 1). This is more aligned with my mental model of an event feed/stream, where a timeline^1 is the history of the feed after optional filtering and content materialization. (^1 However, the terms are often used interchangeably in the Fedi.)
Oh, that is very interesting. I will queue this up for inclusion in the delightful fediverse development curated list.
#Datastar may be a great library to check out here, and goes further in #hypermedia approach, where #HTMX considers itself feature-complete. Datastar uses #SSE to keep the connection to the client open. The client-side JS lib that is needed is super small. In datastar apps most of the business logic lives in the backend, and it lends itself very well for #EventSourcing. The original author/co-maintainer uses it with #NATS which also serves as the event store.