D 2018-07-04T19:30:46.518
L other-fields
N text/x-markdown
P d20ae1301b4fa125424634195396d3cbaf2e085448ec87c3012b3bae212e6e71
U mario
W 1328
#### Other fields

Some examples of other `key:` names one could use.

| **References**|
| `url:` | `http://fossil.example.org/wiki/plugin` <br> Usually just used for the main script, as project homepage link. |
| `doc:` | `http://doc.example.org/` <br> link to manual |
| `src:` | `http://stackoverflow.com/questions/*` <br> Code origin reference |
| `documentation:` | `http://ietf.org/rfc…` <br> External reference |

| **Menu / Icons** |
| `icon:` | `fire.png` <br> Could  be relative file reference, or some application-level fixed icons/ dir. |
| `png:` | `iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAY…` <br> base64 embedded icon (as used in streamtuner2) |
| `img:` | Either embedded or file reference / just an alias |
| `hidden:` | e.g. hide plugin entry from main menu |
| `keycode:` | `Alt+F4` <br> Keycombinations for GUI apps |
| `key:` | `cp│copy` <br> Regex aliases for CLI interfaces |

| **Plugin management** |
| `sort:` | `-100` <br> Ordering for plugin loading, if they're instantiated on startup but some are pre-dependencies. |
| `priority:` | `core` <br> How essentional is this plugin (`core`, `default`, `optional`, `contrib`, `obsolete`). Can be utiized for grouping plugins in admin UI. |
| `support:` | `none` <br> Indicate if plugin is actively supported, or unmainted contrib/ |

Z 0355f8d7f9e55244e4b7b02b83f960cd