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
Copy file name to clipboardExpand all lines: README.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -151,6 +151,8 @@ The plugin will register these commands starting with `janitor:*` automatically
151
151
The button you create with the `field: janitor` in your blueprint can be configured to do various things. Checkout the [example default.yml blueprint](https://github.com/bnomei/kirby3-janitor/blob/master/tests/site/blueprints/pages/default.yml) to familiarize yourself with how to use it.
152
152
153
153
-`autosave`, if `true` then save before pressing the button
154
+
-`backgroundColor`, sets backgroundColor of button
155
+
-`color`, sets text color of button
154
156
-`command`, command like you would enter it in terminal, with [query language support](https://getkirby.com/docs/guide/blueprints/query-language) and page/file/user/site/data arguments
155
157
-`cooldown`, time in milliseconds the message is flashed on the button (default: 2000)
156
158
-`error`, set message to show on all **non-200**-status returns with query language support
@@ -166,7 +168,9 @@ The button you create with the `field: janitor` in your blueprint can be configu
166
168
167
169
In either the command or the callback you will be setting/returning data to the Janitor button via its api. Depending on what you return you can trigger various things to happen in the panel.
168
170
171
+
-`backgroundColor`, see `backgroundColor`-field option
0 commit comments