dDocs

At a Glance:

ddocs.new is an on-chain, privacy-first collaborative document editor offering peer-to-peer, end-to-end encrypted, and decentralized note-taking as an alternative to centralized solutions, and it supports Markdown, LaTeX, offline editing, and an AI writer.

Overview:

Ddoc Editor is an open-source, self-sovereign document editor designed for secure, real-time and asynchronous collaboration. It operates on a peer-to-peer, decentralized architecture with end-to-end encryption, positioning itself as a privacy-first alternative to conventional cloud-based document tools. The editor is provided as a React component package, enabling developers to embed its functionalities. It targets users and developers seeking a collaborative writing environment that does not rely on central servers, incorporating features like offline support via IndexedDB, wallet-based authentication, and an integrated AI writer.

Key Decision Points:

• Deployment is self-sovereign and P2P: The editor operates on a decentralized, peer-to-peer basis. Users do not depend on a central server, which is a core architectural decision for data sovereignty.

• Integration is component-based: The project delivers its core functionality as a React component (/package), meaning it is intended for integration by developers into other applications, not just as a standalone web app.

• Authentication model is wallet or username-based: The editor's props detail connection via a crypto wallet or a direct username, indicating a user identity model built on Web3 principles, which is separate from traditional email/password systems.

• Collaboration is a toggleable feature: Real-time collaboration can be explicitly enabled via a prop, requiring a unique collaboration ID, which gives developers control over whether a document is collaborative or single-user.

• Content extensibility is propped: The tool supports an AI writer, Markdown/LaTeX, and IPFS-based image handling, but these are exposed as configurable callback props, leaving the implementation of the underlying services to the integrating developer.

Core Features:

• Real-time Collaboration: An enableCollaboration prop activates peer-to-peer, real-time co-editing features when a collaborationId is provided.

• Offline Editing and Sync: Uses an enableIndexeddbSync prop to leverage IndexedDB for local data persistence and offline support, synced via a specific document ID (ddocId).

• End-to-End Encryption: The architecture is described as end-to-end encrypted, ensuring that content is only readable by the participating peers.

• AI Writer Integration: The editor accepts properties like activeModel and maxTokens to enable an AI agent for text generation directly within the document.

• IPFS Image Handling: Dedicated callback props (ipfsImageUploadFn, ipfsImageFetchFn) allow developers to wire up secure file storage and retrieval via the InterPlanetary File System.

• Export and Presentation Tools: Includes built-in capabilities for Markdown and PDF export, and a presentation mode with shareable slide links and customizable document styling.

Use Cases:

• Developers integrating a private rich-text editor: The React component package is ideal for embedding a collaborative, end-to-end encrypted text editor into a Web3 or privacy-focused application.

• Users requiring sovereign collaboration: Individuals or groups who want to co-author documents without storing data on third-party cloud servers can use an application built with this editor for peer-to-peer collaboration.

• Environments needing offline-first document editing: The IndexedDB sync capability makes it suitable for workflows where network connectivity is intermittent, allowing users to continue editing and sync changes later.

Open-Source Alternative Value:

This project offers an open-source alternative for document collaboration by making its component source code available for inspection and integration. Its value lies in a decentralized, peer-to-peer architecture that contrasts with centralized cloud services, giving developers a way to build applications where data is not stored on a single provider's infrastructure. The structured React component allows for adoption based on explicit collaboration, authentication, and storage props, rather than a rigid, all-in-one service.