As MartinMond said, this is indeed an attempt to bring a GitHub style workflow to a field outside of software development.
The app is written in Clojure(Script), implementing OT for collaboration.
Happy to answer any questions!
That said, I'll probably end up using this for lyrics! (When I used to write for musical theater in college, our writing workshop would basically use Google Docs, using screenplay formatting and typesetting in all caps for singing. This would have revolutionized the workflow there, even without music-specific features. Individual songs have "beats" and evolving themes just like anything else!)
On the tech side, did you use something like https://github.com/jahfer/othello for OT, or roll your own? And do you think in hindsight that CLJS was the right language/toolset for the job? I've always been interested in its ability to treat immutable data as a first-class citizen, but I haven't had a chance to do it yet.
The OT is custom and clj/s was the perfect tool for the job. Highly recommended.
Not sure about your future plans, but there's a huge need for good collaborative writing/editing programs for traditional book publishing. Collaboration with developmental editors, copyeditors, agents, publishing staff, etc is both essential and extremely painful.
From the looks of it, the structure and output needs for book projects are less demanding than what you've already implemented, so it might be a worthwhile adjacency to explore.
Hope this helps.
Yes, we're definitely going to support formats other than Hollywood-style screenplays in the near future. Would be great to learn more about the needs for collaboration in book publishing.
Not an Electron hater here, I use VS Code (along with Emacs).
The idea of our app is to build on that notion and offer automatic versioning.