@numericoach/gskills-admin-cli 0.1.30 → 0.1.31

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -57,6 +57,22 @@ gskills-admin pages update <pageId> --data-file ./page-fields.json --yes --outpu
57
57
 
58
58
  Use the listed `cache.scopes` with `gskills-admin cache invalidate` after create, update, or delete when the end-user view must reflect the change immediately. Delete flows should archive content first; after a real delete, re-read the row and verify `archived: true` when the resource supports it.
59
59
 
60
+ Workflow authoring has a guided CLI surface. Use it before raw `workflows` and `workflow-actions` CRUD:
61
+
62
+ ```bash
63
+ gskills-admin workflows schema --output json
64
+ gskills-admin workflows schema --trigger LEARNING_PATH_NOT_STARTED --output json
65
+ gskills-admin workflows example --trigger LEARNING_PATH_NOT_STARTED --output json
66
+ gskills-admin workflows preview-email --data-file ./workflow.json --fake --language fr --output json
67
+ gskills-admin workflows preview-email --data-file ./workflow.json --user user@example.com --language fr --output json
68
+ gskills-admin workflows create-configured --instance global --data-file ./workflow.json --inactive --dry-run --output json
69
+ gskills-admin workflows create-configured --instance global --data-file ./workflow.json --active --yes --output json
70
+ ```
71
+
72
+ `workflows schema` lists every supported trigger and action, the trigger config schema, trigger payload schema, email variables, button placeholders and examples. `create-configured` creates the workflow and all actions in one operation. It requires an activation decision. Ask whether to enable the workflow now, then pass `--active` or `--inactive`. Prefer `--inactive` until the preview email, target ids, recipients and translations are approved.
73
+
74
+ Email actions use `config.templates`, a map of language code to `{ subject, body }`. Keep variables such as `{{userName}}`, `{{userEmail}}`, `{{instanceName}}` and trigger-specific variables unchanged across translations. `preview-email` renders the exact subject and body without sending anything. Use `--fake` for sample trigger data, or `--user` / `--email` to preview with a real user.
75
+
60
76
  For page body edits, prefer the granular block helpers when a stable block id exists. Dry-run first, then write:
61
77
 
62
78
  ```bash