Files
dbx/plugins/sdk/cli/templates/frontend/README.md
T

35 lines
1.5 KiB
Markdown

# {{PLUGIN_NAME}}
{{DESCRIPTION}}
Generated by `dbx-plugin create` with the **{{TEMPLATE_LABEL}}** template. This project has no native backend and produces one cross-platform `universal` package.
## Develop
Edit `ui/index.html` and run the browser development host with Node.js 22+:
```bash
dbx-plugin dev --path . --port 5190
```
No backend or DBX application is required. Open this plugin's workbench from the development shell; reload the page after edits. `.dbx-dev/` stores local development data and must not be committed or packaged. Use the real DBX host for final integration testing.
Then package the plugin:
```bash
dbx-plugin package .
```
The command stages `manifest.json`, `assets/`, and `ui/`, then writes an unsigned universal `.dbxp` candidate plus matching `.artifact.json` into `dist/`.
## Release
1. Publish a GitHub Release. The generated workflow builds an unsigned universal candidate.
2. Open a **Plugin submission Issue** in `t8y2/dbx-store` with the source tag and `release-candidates.json` URL.
3. After review, DBX Store signs the approved candidate with the official repository key and publishes the installable asset.
4. Open the final catalog PR against **`t8y2/dbx-store:main`** using the signed artifact metadata.
Source code and the unsigned candidate stay in this repository. DBX users install the DBX Store-signed asset exposed by the official catalog.
Do not submit ordinary plugin source to `t8y2/dbx`; that repository accepts plugin host, SDK, CLI, schema, documentation, and official-example changes.