This part four of our blog post series on building a real-time, multi-user Kanban board with CouchDB and Svelte. As mentioned in the [previous post](/blog/2024/12/18/manual-conflict-resolution-with-couchdb-and-svelte), UI or resource locking is one of the most promising mechanisms for avoiding conflicts in the first place: if a card is locked the moment Alice starts editing it, then Bob won’t be able to do anything with it, and therefore won’t be able to introduce a conflict. Sounds like ...
