Shared editing sessions

Collaboration

Treat collaboration as a composable document service, not an editor-specific afterthought.

Explore source
Parent systemProEdit
StatusPreview
Modules4
RepositoryProEdit/ProEdit.Collaboration

Protocol, transport, server, editor, and UI modules for synchronizing document operations, presence, and collaborative editing workflows.

  1. 01

    Operation-based synchronization

  2. 02

    Presence and participant state

  3. 03

    Transport-neutral sessions

  4. 04

    Server and UI packages

From intent
to working system.

01

Operation

Document changes are represented as explicit collaboration messages.

02

Session

Participants, presence, versions, and local state are coordinated.

03

Transport

Connections move protocol messages without owning editor logic.

04

Experience

Editor and UI packages surface remote changes and presence.

Adopt this
capability.

Start with the primary module, then add the related packages only when the application needs those layers. Replace VERSION with the current NuGet version.

01 · Install
Terminal
dotnet add package ProEdit.Collaboration --prerelease
02 · Use · csharp
QuickStart.cs
var session = await collaboration.ConnectAsync(
documentId: "proposal-42",
user: currentUser,
cancellationToken);
editor.AttachCollaboration(session);

Use one layer.
Compose the rest.

Read the module beside the complete system.

The implementation, samples, issues, and release notes stay in the parent repository so module details remain connected to the product architecture.

ProEdit

Search everything.

Loading the index…

move open esc close

Preparing metadata and full-text search…