After many browsers added their own developer tools this doc-bot command seems somewhat deprecated.
May I suggest to add a new command .inspect instead:
.inspect – Tells the user to inspect code using developer tools of his browser
Text to show up after bot command: Please use the built-in Developer Tools of your browser to fix problems with your website. Right click your page and pick "Inspect Element" (Cr, FF, Op) or press F12-button (IE) to track down CSS problems. Use the console to see JavaScript bugs.
This doc-bot command covers third party plugins and themes, especially with code not being publicly accessible, hence making it impossible to help.
As an inversion of that argument, some users seem to expect answers to their themes or plugins as granted, when the plugin or theme was downloaded from wordpress.org ("But it isn't proprietary, so you *must* support me."). For such cases, I would suggest following new doc-bot command:
Tells the user not to expect support for each and every plugin or theme available at WordPress.org
Text to show up after bot command: We try our best, yet from a great variety of existing themes and plugins it is nearly impossible to know all. Your best chance is to contact the developer for support.
As a non-native speaker I would appreciate any improvement on the wording.
Pixolin, May 17th 2013
Nkuttler 10:51, 10 September 2010 (UTC)
In /query, allow !list or !help (or something to that effect) to respond with a list of the existing one-word commands. (Saves referencing the Codex or other source when adding a new command.)