@fluid-app/fluid-cli-theme-dev 0.1.521 → 0.1.523
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 +33 -0
- package/dist/index.mjs +665 -61
- package/dist/index.mjs.map +1 -1
- package/dist/skills/themes-review/SKILL.md +1 -1
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -161,6 +161,39 @@ fluid theme pull --resolve remote # Auto-resolve conflicts to the server's
|
|
|
161
161
|
|
|
162
162
|
By default, conflicting edits (changed locally _and_ on the server since the last sync) are written with git-style conflict markers for you to resolve. For non-interactive use, `--resolve local` keeps your side of each conflicting hunk and `--resolve remote` takes the server's; before any auto-resolution overwrites local content, the pre-merge working tree is committed to the theme's shadow history (`.fluid-theme/repo`) so the discarded side stays restorable.
|
|
163
163
|
|
|
164
|
+
### `fluid theme widget`
|
|
165
|
+
|
|
166
|
+
Customize a Fluid native widget (`{% section 'fluid://native/widgets/<key>' %}`)
|
|
167
|
+
through the theme's own copy of it. The copy replaces the widget at every
|
|
168
|
+
placement in the theme, the same copy the visual builder makes when a widget is
|
|
169
|
+
dropped:
|
|
170
|
+
|
|
171
|
+
```bash
|
|
172
|
+
fluid theme widget copy acct # Make the copy and pull it into fluid_native_acct/ (asks first on the live theme)
|
|
173
|
+
fluid theme widget copy acct --yes # Same, without the live-theme confirmation
|
|
174
|
+
fluid theme widget reset acct # Delete the copy and its fluid_native_acct/ folder (asks first)
|
|
175
|
+
fluid theme widget reset acct --yes # Same, without the confirmation
|
|
176
|
+
```
|
|
177
|
+
|
|
178
|
+
A copy keeps the template type of Fluid's original, so it is pulled into
|
|
179
|
+
`sections/fluid_native_<key>/` for a widget that is still a section and into
|
|
180
|
+
`widgets/fluid_native_<key>/` for one stored as a widget. `reset` deletes the
|
|
181
|
+
theme's copy of either type and removes both folders.
|
|
182
|
+
|
|
183
|
+
Both commands act on the theme in `.fluid-theme.json` unless `--theme <id>` is
|
|
184
|
+
passed, then run an ordinary `fluid theme pull` of that theme so the sync
|
|
185
|
+
baseline matches the server. The pull also brings down any other changes made
|
|
186
|
+
to the theme since the last pull.
|
|
187
|
+
|
|
188
|
+
On the live (active) theme a copy or reset changes what members see as soon as
|
|
189
|
+
it is made, so `copy` asks before it makes the copy there and `reset` says the
|
|
190
|
+
theme is live in its confirmation. `--yes` skips both prompts.
|
|
191
|
+
|
|
192
|
+
Do not create `sections/fluid_native_<key>/` or `widgets/fluid_native_<key>/`
|
|
193
|
+
by hand: without a copy of that type, a push makes it a plain template that
|
|
194
|
+
replaces nothing, and every placement keeps rendering Fluid's original.
|
|
195
|
+
`fluid theme push` warns about such folders.
|
|
196
|
+
|
|
164
197
|
### `fluid theme init`
|
|
165
198
|
|
|
166
199
|
Scaffold a new theme from the base template:
|