This is not a situation where you'll have thousands of people editing the same document, that'd be insane with Django for sure - but at general collaboration tooling with <100 (random number I made up) editing, Django is unlikely gonna be the bottleneck
What part of your document editor needs to be backed by a relational database?
Why use an MVT system if you don't need the Model part of it?
I see, in your broad and experienced mind, document editors don't have users, permissions, and the whole document management itself, comments on lines/threads, reactions on comments
Seriously, theyre all as cookie cutter perfect usecase for Django as you can get, but I guess you haven't actually thought about the domain and just wanted to take a dumb on other devs with intern-to-junior level insights