How to use dsh-plugin
Co-author documents in GEML plain text, readable by people and addressable by machines with versioned sidecar history.
This article is auto-derived from indexed fields (wiki / faq / compatibility_json), not freshly AI-generated.
This article is derived from the plugin's already-indexed fields (wiki / faq / compatibility_json / readme), not freshly generated by AI. Source field is noted at the end of each section.
Quick start
Co-author documents in GEML plain text, readable by people and addressable by machines with versioned sidecar history.
— source: plugins.ai_summary
Install & verify
dsh plugin --profile web add @geml/dsh-plugin
Run the command above in your DSH Web Profile. Then enable the plugin in the plugin list.
— source: plugins.install
Key points
- JSON / XML (serialized for machines): full of wrapper syntax and structural noise — blocking natural human reading, while quietly eating expensive tokens in long contexts.
- Self-hosting —
GEML-spec.gemlis the specification written in GEML, required to parse clean on every test run. - A conformance suite is what holds separate implementations compatible.
- On the wire. Extension
.geml(version sidecar.gemlhistory), media typetext/geml, ortext/vnd.gemlwhere a registered type is required —text/gemlis not registered with IANA yet. - A fragment identifier on a
.gemlURL names the block bearing that id (§0.6) — which is not what#tagmeans on an HTML page.
— source: plugin_wiki.readme_en (fallback readme_raw)
Compatibility
- DSH: 未声明
- Node: 未声明
- Platforms: 跨平台
— source: plugin_wiki.compatibility_json
Pitfalls
Review the upstream repo before installing. This guide is auto-derived from indexed fields and may lag the latest release. If anything contradicts the official docs, treat the upstream source as authoritative.
— source: general rule