@wix/himalaya-cli 0.1009.0 → 0.1011.0
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.
|
Binary file
|
package/guides/headless-loop.md
CHANGED
|
@@ -71,6 +71,30 @@ can discover and scaffold it. Any himi app can become a template this way.
|
|
|
71
71
|
typed submit/persist/recovery paths, and an explicit compact/phone/expanded-width decision. A
|
|
72
72
|
template that only validates is a reference build, not yet a customer-ready starting point.
|
|
73
73
|
|
|
74
|
+
## 2b. Show the owner what you are building
|
|
75
|
+
|
|
76
|
+
The customer entry skill asks for a picture at every milestone (**Keep the owner watching**). This
|
|
77
|
+
loop already makes the pictures — send them, and journal each one:
|
|
78
|
+
|
|
79
|
+
```sh
|
|
80
|
+
himi render home --png shots/home.png --device iphone # the first picture, right after init
|
|
81
|
+
himi studio # the build board: opens once, keeps itself current
|
|
82
|
+
himi progress "Starting from branded-lite" --step implement --image shots/home.png
|
|
83
|
+
himi render home --png shots/home-dark.png --device iphone --scheme dark
|
|
84
|
+
himi progress "Your brand, light and dark" --step brand --image shots/home.png --image shots/home-dark.png
|
|
85
|
+
himi progress # the journal: current step, elapsed, every postcard
|
|
86
|
+
```
|
|
87
|
+
|
|
88
|
+
`himi studio` writes `.himi/studio/index.html` and opens it; from then on every render, test,
|
|
89
|
+
validate, push and progress entry refreshes it, and the page picks that up by itself — no server,
|
|
90
|
+
nothing to re-run (`--no-open` prints its path instead, for SSH). `himi test` writes one PNG per
|
|
91
|
+
screen to `.himi/shots/` on every run, so take the new screens from there instead of rendering each
|
|
92
|
+
one again; a bare `--png` on `himi render` writes `.himi/shots/<id>.png`. `himi progress` copies each image into `.himi/history/`
|
|
93
|
+
as it was when you journaled it, so a later render cannot change what the record says the owner saw;
|
|
94
|
+
`--step` takes the journey step's number or name, and `--notify` also raises a desktop
|
|
95
|
+
notification for an owner who stepped away. Nothing here is sent anywhere, and `.himi/` and a
|
|
96
|
+
root-level `shots/` are never archived by `himi push`.
|
|
97
|
+
|
|
74
98
|
## 3. Build + lint (fast, local, no push, no sim)
|
|
75
99
|
|
|
76
100
|
```sh
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@wix/himalaya-cli",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.1011.0",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"description": "himi — the Himalaya authoring CLI. Build a Tier-5 content package on your own machine, push it to the production serve as a draft, preview it on web + Himi Player, and read worker logs back — the remote dev loop. Wraps @himalaya/serve-cli for transport.",
|
|
6
6
|
"keywords": [
|
|
@@ -65,5 +65,5 @@
|
|
|
65
65
|
"artifactId": "himalaya-cli"
|
|
66
66
|
}
|
|
67
67
|
},
|
|
68
|
-
"falconPackageHash": "
|
|
68
|
+
"falconPackageHash": "404a726404c7060db8a63a60c1d013e2ec2c545148d0b9b19b865a5a"
|
|
69
69
|
}
|