[yencabulator]

> For offline-first, the user would be alerted that someone changed the record(s) while you changed them as well and ask what to do.

There are few sync strategies worse than "you worked hard on this, but now you have to choose to either throw away your change or everyone else's changes". May any product doing that fail miserably.

[anonzzzies]

And your great solution? As others say; there are none. Talking about structured content in an offline first context. What is your strategy that won't break anything while doing a merge?