[openstreetmap/openstreetmap-website] Use turbo for pagination (PR #4646)

[David Tsiklauri]

With the current solution, back-end side still renders a whole page including header and other elements, that won't be updated (see screenshot). For example, generating a header requires ~1s extra time and when user uses pagination, in some cases, ignoring everything that won't be rendered in the `turbo-frame` may give us 2-10x faster calls. In addition to this, people who use application from mobile phones, spend more data than it is needed. Turbo Streams are great tool for solving this, or we can use API endpoints that render only partial which should be rendered in the `turbo-frame` element (but both ways may need a small amount of JS code). I have the same problem in https://github.com/openstreetmap/openstreetmap-website/pull/5057. I think it will be great if we have one standard about using `turbo-frames`.

Screenshot:

![image](https://github.com/user-attachments/assets/cc8af9dd-11a0-4c7f-9b69-9ec35b4315bf)


-- 
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/4646#issuecomment-2283373826
You are receiving this because you are subscribed to this thread.

Message ID: <openstreetmap/openstreetmap-website/pull/4646/c2283373826 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20240812/9a6f4a8c/attachment-0001.htm>