Mention Versioning Issues in Hypermedia Applications that use Fragments

[fabb]

I'm opening this PR to start a discussion of versioning issues that can happen in hypermedia applications and when using htmx for fetching fragments. I feel this issue is neglected in the documentation and should be represented in a balanced way, ideally with examples on how to mitigate the issues.

Examples on when an inconsistent state could happen aways assume that the client browser loaded a full htmx page, then a server application update is deployed, and then the client executes some action that loads a fragment into the dom somewhere:

• Example 1: a loaded fragment references html elements outside of the fragment that have been added in an application update on the server, but are not yet contained in the browser dom.
• Example 2: a loaded fragment references css classes that have been updated or added in an application update on the server
• Example 3: an endpoint for fetching a fragment might have been removed in an application update on the server, but is still referenced in htmx element attributes in the browser dom.

Even if these cases are rare (depends on the number of users and deployment frequency), it would be great to give devs heads-up on potential issues.

[netlify[bot]]

✅ Deploy Preview for hypermedia-systems ready!

Name	Link
🔨 Latest commit	8624e0d6c6b1cf2d54d8d95abd5382a78e9a4c51
🔍 Latest deploy log	https://app.netlify.com/sites/hypermedia-systems/deploys/65ca2ccdc3e6fe0008d12ba8
😎 Deploy Preview	https://deploy-preview-130--hypermedia-systems.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[1cg]

Hello @fabb I agree it's an issue to consider discussing. We are closing down this repo and moving to a new one w/ a better typesetting tool. I will let you know when the new repo is publicly available.