Conventions
In this book, you will find a number of text styles that distinguish between different kinds of information. Here are some examples of these styles and an explanation of their meaning.
Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: "For instance, if a user is tagged with the vip tag, all their tickets will subsequently be tagged with the vip tag as well."
A block of code is set as follows:
curl -v -u {email_address}:{password} https://{subdomain}.zendesk.com/api/v2/users.json \
-H "Content-Type: application/json"
-X POST
-d '{"user": {"name": "FirstName LastName", "email": "user@example.org"}}' When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:
curl -v -u {email_address}:{password} https://{subdomain}.zendesk.com/api/v2/users.json \
-H "Content-Type: application/json"
-X POST
-d '{"user": {"name": "FirstName LastName", "email": "user@example.org"}}' Any command-line input or output is written as follows:
gem install zendesk_apps_tools
New terms and important words are shown in bold. Words that you see on the screen, for example, in menus or dialog boxes, appear in the text like this: "Click on People located under MANAGE within the admin menu."
Note
Warnings or important notes appear in a box like this.
Tip
Tips and tricks appear like this.
