Turbo is just a JS library, not tied to rails. I use it with golang and I love it!
It offers a nice tradeoff between heavy custom HTML attributes and too much 'convention over configuration'. Also pairs nicely with alpine.js
> Several framework specific solutions have come to existence to give server-side templating more client side power, in particular:
> Ruby/Rails => TurboLinks/Hotwire
Hotwire is not framework specific. E.g. hotwired/turbo is just a JS library that allows for progressive enhancement in basically any web application that renders HTML.
I use it in Go and I love it!
Since you mentioned this could you please give some hints on how to enable external forwarding at all? Spent hours on the issue last month before finally giving up deciphering the maze of the legacy UI. Thanks in advance.
A very conservative estimation! And it's not only documentation of software but also the requirements and other parts of the whole lifecycle. It's incredible how many companies hold meetings after meetings to keep up the oral tradition only to run in circles. Instead of POs who churn out dozens of irrelevant tickets, we need people who can tell and write stories - real stories not "user stories". They offer insight, motivation, engagement and the right understanding to break down the work into reasonable and deliverable bits.