Conventions

In this book, you will find a number of styles of text 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: "The bower.json file is how Bower manages the project's dependencies."

A block of code is set as follows:

<div class="header">
  <ul class="nav nav-pills pull-right">
    <li ng-repeat="item in App.menu" 
      ng-class="{'active': App.location.path() === item.href}">
      <a ng-href = "#{{item.href}}"> {{item.title}} </a>
    </li>
  </ul>
  <h3 class="text-muted"> {{ App.sitetitle }} </h3>
</div>

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

require 'scripts/config'
LearningYeomanCh5 = window.LearningYeomanCh5 =  
  Ember.Application.create(
 LOG_VIEW_LOOKUPS: true
 LOG_ACTIVE_GENERATION: true
 LOG_BINDINGS: true
 config: window.Config
)

Any command-line input or output is written as follows:

$ npm install -g generator-webapp

New terms and important words are shown in bold. Words that you see on the screen, in menus or dialog boxes for example, appear in the text like this: "See for yourself; open Chrome Developer Tools and click on the Network tab."

Note

Warnings or important notes appear in a box like this.

Tip

Tips and tricks appear like this.