4.6 KiB
DSH Desktop Documentation
This directory is the product and developer documentation index for DSH Desktop. The root README.en.md is the short product entry point; these pages explain why the project exists, how to use it, and how to build plugins for it. Want to contribute? See Contributing.
Read by goal
Ordinary users can start with the user guide and never need the developer documentation.
User documentation
| Document | Covers |
|---|---|
| User guide | Installation, profiles, modes, terminal, plugins, and updates |
| FAQ | Direct answers about platforms, bundled runtime, project status, data, plugins, and updates |
| Privacy Policy | Official updates, downloads, local data, third-party services, and user choices |
| Why Desktop | The boundary with upstream Harness and the case for plugins |
Developer and maintainer documentation
| Document | Covers |
|---|---|
| Plugin ecosystem manifesto | The vision of an open, composable, sustainable plugin ecosystem and its three principles |
| Plugin development | Ordinary DSH plugins, Desktop services, compatibility, and lifecycle |
| Community Fabric Draft | Community interoperability drafts spanning manifest/capability foundations, Runtime/Presentation, service composition, and provenance diagnostics |
| Fabric community-feedback disposition | Which Issue #23 proposals were adopted, split into focused RFCs, deferred, or kept out of portable core |
| Fabric framework and plugin-needs research | Mature Koishi, Chrome, and VS Code patterns plus requirements observed in real DSH plugins |
| VS Code extension-model research | Implemented declaration, Provider, UI, placement, and lifecycle patterns, with concrete constraints for the Fabric RFC |
| Community Market design | The proposed market shell, extensible catalog sources, user selection, install confirmation, and safety boundary |
| Market catalog provider contract | Schemas, query parameters, multi-source behavior, and adapter rules for the implementation team |
| Architecture | Electron, Host, the Web carrier, profiles, and packaging |
| Desktop service reference | Stable desktopProfiles and desktopPnpm contracts with TypeScript examples |
| Package reference | Detailed build, runtime, release, and limitation notes |
How the README files are organized
The outer repository has two formal product READMEs plus one legacy compatibility entry:
README.md: the Chinese product entry point.README.en.md: the English product entry point with the same product scope.README.zh.md: a legacy Chinese-path compatibility page with no independent content.
README.i18n.yaml records the bilingual blob hashes for those two formal entry points; it is not a user guide. dsh-plugin-desktop/README.md and dsh-plugin-desktop/README.zh.md ship with the npm package and are the more technical package reference. dsh-plugin-desktop/docs/ contains stable API contracts rather than marketing copy. .agents/notes/implemented/ contains dated maintainer decision records and does not replace user documentation.
deepseek-harness/ is the pinned upstream submodule. Its README and docs/ belong to the upstream project, not to the Desktop product, and are excluded from the outer documentation inventory.
Status convention
These pages distinguish shipped behavior, platform limits, and roadmap items. Compatibility mode keeps the upstream default Web client below an independent Desktop frame; extended mode installs its own Desktop layout/sidebar registration and hosts official occupants in an inverted L; enhanced mode retains a separate root registration with compact internal captions. Desktop frames provide capability-gated native materials. The plugin marketplace now has a documentation scaffold in dsh-community-market, but no usable page or installer; mobile remote control and Channels also remain separate roadmap items and are not implied to be part of the current installer.