Question
I've been reading through the docs-editor codebase and I'm
trying to understand how abstracted the collaboration/CRDT layer
is from the document model itself.
Specifically: is it designed in a way that could support
non-linear document models — e.g. a slide-based structure where
each "node" is a slide rather than a paragraph?
I'm evaluating the feasibility of building a community-contributed
presentation editor (docs-slides) that reuses as much of the
existing architecture as possible — shared crypto, collab, and
@proton/components — while following the conventions in the
contributing guide.
Before investing time in a proof of concept, I wanted to check:
- Is the CRDT/collab layer abstracted enough to support this?
- Are there internal constraints or planned refactors I should
be aware of?
- Is this kind of external contribution something the team would
consider reviewing?
Question
I've been reading through the
docs-editorcodebase and I'mtrying to understand how abstracted the collaboration/CRDT layer
is from the document model itself.
Specifically: is it designed in a way that could support
non-linear document models — e.g. a slide-based structure where
each "node" is a slide rather than a paragraph?
I'm evaluating the feasibility of building a community-contributed
presentation editor (
docs-slides) that reuses as much of theexisting architecture as possible — shared crypto, collab, and
@proton/components— while following the conventions in thecontributing guide.
Before investing time in a proof of concept, I wanted to check:
be aware of?
consider reviewing?