4 ms·
We are building an enterprise application that manages (create, update data) and interacts with (read, display, enable user to browse via linked entities) a lar
by DLA 2y ago
We are building an enterprise application that manages (create, update data) and interacts with (read, display, enable user to browse via linked entities) a large-scale knowledge graph. In some views we have live updates from the server with SSEs (alerts, logs, etc.). Everything is rendered server side with Go + stdlib templates, Material Design Bootstrap for CSS, and HTMX for all the in interactive bits like fetching and rendering an entity's properties panel, enabling add/edit for entity or edge properties, and so on. Search updates results with HTMX. Entity/property edits are done with HTMX "panels".
The entire experience using Go + Fiber (gofiber.io) + templates + HTMX (htmx.org) is fantastic. This approach has allowed us to create a beautiful modern application that's highly performant, interactive in all the places you'd expect, and simple code, deps, devops, etc.
- jack_riminton 2y agoSounds great thanks
- synergy20 2y agodo you use alpinejs for better client side reactivity?
- DLA 2y agoWe use the alpinejs for when we choose not to round trip the server (like data validators, for example) and for cases when we need to do some client side JSON work. Mostly htmx handles what we need. You could also consider it’s client-side template rendering extension, as needed.