Upwelling: Combining real-time collaboration with version control for writers.
Collaborative writing tools don’t work well for writers or editors. With Upwelling, we demonstrate a design that gives writers privacy while still offering editors transparency into how a document is changing.
Problems with existing collaboration tools Professional non-fiction writing often requires several people – authors, editors, and reviewers – to work together in order to produce a finished document. For example, several journalists and editors may contribute to a news article, a group of scientists may collaborate on a research paper, and in business or government the members of a team may jointly write a proposal, report, or documentation. In all of these cases, it is important for the contributors to ensure that the final document is of a high quality, correct, and consistent in both conten
Explore this link on the map →saved by
related reading
- Collaborative Workspacesgithubnext.com
- Peritext: A CRDT for Rich-Text Collaborationinkandswitch.com
- Introducing the collaborative editor built for teams and agentsmintlify.com
- Malleable software: Restoring user agency in a world of locked-down appsinkandswitch.com
- You don't need a CRDT to build a collaborative experience | Hacker Newsnews.ycombinator.com
- 22 UX improvements to the web editormintlify.com
- Software Is Made Between Commits — Zed's Blogzed.dev
- You don't need CRDTs for collaborative experiences — /dev/knillzknill.io
- CRDTs go brrrjosephg.com
- An adventure in realtime collaborative editing — Dov Alperindov.dev
- One Developer, Two Dozen Agents, Zero Alignmentmaggieappleton.com
- A simple way to build collaborative web apps | Hacker Newsnews.ycombinator.com