You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Five host-side gaps that keep non-developers out of the plugin ecosystem
#11955
Five things block a non-developer (accountant, lawyer, HR, procurement) from using the plugin ecosystem today. All five are host-side; the plugin side is already prepared (index, packaging standard, quickstarts). Details and evidence: https://github.com/PerryLink/dsh-plugins/blob/main/docs/UPSTREAM-REQUESTS.md
Make the plugin market visible by default and ship an official index source. Today Discover needs an experimental bundle and a hand-pasted index URL; docs/user/guide/plugin-market.md says DSH ships no index source, so a new user sees an empty tab.
Do not require choosing a disk workspace before the first message. It is the first thing a non-developer cannot answer; a default sandbox would make "open and use" zero steps.
A declarative UI schema for plugins (form / action / wizard / result described as JSON). Today a plugin that wants a form must ship React, so business plugins only have a chat box.
Office write-back. Dropped .docx/.xlsx are previewed read-only; our dsh-docx-redline produces an edited document that the user cannot retrieve.
Human-readable permission tiers.sandbox / danger-full-access / per-call approval are developer words; plugins already declare read/write/network/external in four lines, and the UI could show exactly that at install time.
Happy to turn any of these into a PR with a small reproducible example if that helps.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Five things block a non-developer (accountant, lawyer, HR, procurement) from using the plugin ecosystem today. All five are host-side; the plugin side is already prepared (index, packaging standard, quickstarts). Details and evidence: https://github.com/PerryLink/dsh-plugins/blob/main/docs/UPSTREAM-REQUESTS.md
docs/user/guide/plugin-market.mdsays DSH ships no index source, so a new user sees an empty tab.dsh-docx-redlineproduces an edited document that the user cannot retrieve.sandbox/danger-full-access/ per-call approval are developer words; plugins already declare read/write/network/external in four lines, and the UI could show exactly that at install time.Happy to turn any of these into a PR with a small reproducible example if that helps.
All reactions