Wiley.com

Using the Wiley SD Template

Using the Wiley SD2007 Template
All books in Wiley Professional Technology group use the SD template. Having the right template attached and styles applied is critical to a successful project. If you are using Office 2007, this page will get you up and running in no time. If you are using Office 2003, please download that cheet sheet as indicated in the first sentence on this page.

Retrieving the Template
Please download the appropriate zip file on this page. In fact, you'll find plenty of useful information on this page, including a video tutorial on applying styles. Please download the TechTool.

Please feel free to download this cheat sheet in PDF form.
You can also download a version of this cheat sheet for Office 2003.

Installing and Attaching the Template
To install the SD template and related files:
  1. Unzip all files to a convenient folder on your system.
  2. Open the file Install.doc and enable macros when prompted.
  3. Follow instructions to install.
Creating a new document in WileySD
Open Word 2007. From the Home tab on the blank document, click the Attach button (shown in Figure 1) in the left-most pane (WileySD).



Figure 1: The Attach button
Alternatively, you can click the Office button and choose New > My Templates. Locate and select WileySD2007.dotm and click OK.

Attaching the template to an existing file
Open an existing document in Word 2007. From the Home tab, click the Attach button in the left-most pane (WileySD).

Adding the Tech Toolbar
We have created a special toolbar to provide quick access to most of the tools and styles you will need. To access the toolbar, you will need Word's Template button, which is not readily available in the 2007 interface. Perform this one-time-only setup:
  1. Select the down arrow at the end of the Quick Access toolbar (the narrow toolbar at the very top of your interface, shown in Figure 2), and select More Commands from the dropdown.


  2. Figure 2: Click this arrow to begin setup.

  3. From the Choose commands from: dropdown, select Developer Tab, then select Templates from the list and click Add, then click OK. The Templates button should now be available on your Quick Access Toolbar.
Now you can access the TechTool as an Add-in whenever you need it:
  1. Click the Templates icon from the Quick Access Toolbar, and select Document Template.
  2. Click Add and then navigate to the folder where you saved the TechTool2007.dotm file. Select the file and click OK. (After you perform this step, the file will remain on the Add-ins list and you can skip this step in the future.)
  3. In the Templates and Add-ins dialog, make sure the TechTool is checked and click OK.

  4. You should now see a new tab, SD Tech, to the left of the Home tab. Click that tab to access the styles menus and TechChecks tool, shown in Figure 3.


Figure 3: The TechChecks button

NOTE: This page should give you all the information you need to attach the template and get things going. However, if you should require more detail and find yourself needing to troubleshoot, please download Detailed Template Instructions.

Checking Page Count
The page count as determined by Microsoft Word is NOT an accurate estimate. To get an accurate estimate:
  • From the SD Tech tab, click the TechChecks button on the left end of the ribbon. Under the heading for the appropriate series (Wrox, Bible, or Wiley Red), click Page Count Estimate Only (see Figure 4). The macro will run through the document and provide a page count estimate (this estimate does not include any figures, even if they have been inserted). You can run this macro on your document at any time, but be sure to check the final page count.


Figure 4: Use the TechChecks tool macros to check page count (and code length).

Chapter Opening Items
  • Place chapter number and title on one line, separated by colon (Chapter 9: Web Browsing). Style as ChapterTitle.
  • For books in the Bible and Wrox series, add list of Intro bullets headed by "In this chapter" and styled as ChapterFeaturingList before the chapter title.
Basic Text Styles
Use the following styles for regular text (styles for Features and Code are indicated in the relevant sections).
NOTE: Access detailed instructions on applying styles.
  • For normal body text, use the Para style.
  • For bullet lists, use the ListBulleted style. This style will automatically insert a bullet before the paragraph. For bullets that contain more than one paragraph, use the ListPara style for the second and successive paragraphs to avoid placing a bullet in front.
  • For numbered lists, use the ListNumbered style. For each item in the list, type the number, followed by a period and a tab, then begin the text. For bullets that contain more than one paragraph, use the ListPara style for the second and successive paragraphs to avoid placing a bullet in front.
  • For sublists, use the ListBulletedSub style or ListNumberedSub style (for numbered sublists).
Features
Use the Features styles for sidebars, notes and tips, cautions, Try It Outs (Wrox Beginning series only), etc. Use only styles from the Feature category or the SD Features tab for text, lists, or code within the feature.
  • To start a feature, use the Features category on the SD Tech tab. Click the arrow next to your series, and select the type of feature you want to create from the dropdown. An XML line will be inserted in your document to denote the beginning of the feature.
  • Use the FeaturePara style for body text within a feature.
  • For code lines within features, use the FeatureCodeSnippet, FeatureCodeScreen, etc. styles, unless the code line is inside a list (see following).
  • For lists within a feature, use the FeatureListBullet, FeatureListNumber, etc. styles. For code lines within a FeatureList, use the FeatureCodeSnippetSub style (this indents the code line to align with the bullets.
Code
Do NOT use tabs or hanging indents in code; they will not work as intended in our automated systems. Instead, use the correct number of spaces to indent as needed.

Code styles
Code styles are included in the Code category of the SD Tech ribbon, or from the SD Code tab.
  • Use CodeSnippet as the default style for code blocks. (The PjE will apply Code80 if needed.)
  • For code within features, use the FeatureCodeSnippet, etc. styles.
  • For full code listings with headings, use the CodeListing style (and CodeTitle for the heading).
Code within other text (InlineCode and variants)
Inline code styles are included in the Inline Code category of the SD Tech ribbon, or from the SD Code tab.
  • Do NOT apply your own Courier or other fonts within the document to create monofont text. Such styles will not work as intended in our automated systems. Instead, use the following styles for inline code terms:
  • To have monofont (code font) used for a term within a line of regular text, a bullet, or other style, highlight the relevant text and apply InlineCode style (from the Inline menu in the Tech Toolbar).
  • For placeholder variables, use the InlineCodeVariable style (this will appear as monofont plus italics).
  • For code terms that the user is to type into an interface, use the UserInput style (this will appear as monofont plus bold).
Checking code line lengths and breaking wrapped code lines
  • All wrapped code lines must be broken with hard returns (using the Enter or Return key).
  • To check whether any of your code wraps, click the TechChecks button after you are sure you have styled all code appropriately. Under the appropriate series (Wrox, Bible, or Wiley Red), click Check Code Length Only. The macro will go through the document and highlight any wrapped code lines in pink. After that, click the Find Long Code button to locate the first instance of wrapped code. Break the wrap by manually adding a hard return. Click the button again to find the next wrapped line. When you think you have no more wraps, run the macro once more to check.
Special Symbols
If a symbol appears on your keyboard, you may use it as a regular character. Click the SD Symbols tab to see other available symbols. If the symbol is not on that menu, leave a note for your editor describing the symbol you want.

Figures
You must supply each figure as a separate file. Please refer to the Working with Figures document in the online author kit for details on creating and naming figure files.
  • Include a text reference to each figure in the text preceding the figure ("Figure 6-1 illustrates...")
  • Use the Slug style (from the Misc. category) for the figure number and caption line (note: captions should not be used in Wrox books).
  • You do not need to insert the figures into the document. If you prefer to do so, use the Insert menu to place the figure on a separate line preceding the Slug line.
Tables
WileySD manuscripts should only contain simple-grid tables: one para per cell, styled TableHead (for column headings) or TableEntry (for table text), no merged or split cells. More complex tables must be submitted as separate files, outside of the manuscript. Do not use hard returns within a table. You may use soft returns (Shift + Enter).

Creating a New Table
  1. From the SD Figs and Tables tab, click Insert Table.
  2. Select the number of columns and rows, and type a title. Click OK.
  3. Begin typing data.
You can add more rows by clicking the tab key from the last table cell.

Converting Text to a Table
  1. Type one tab between the text for each individual cell.
  2. Highlight all text to be converted.
  3. From the SD Figs and Tables tab, click Convert Text to Table.
Important Items to Note
  • Do not add blank lines in the document to create extra space around figures, tables, code blocks, etc. The extra space will be added automatically during our layout process.
  • WileySD does not reflect your final book layout. Do not modify styles in the WileySD template. Do not override the font styles in the template, or change the font sizes.
  • If you are not sure how to style an element, or think you need a style that is not included in the template, leave a note (styled as QueryPara, from the Paras category of the ribbon) or discuss it with your editor.
  • To get a report on your document that tells you the estimated page length, whether there are any wrapped code lines, and whether you have used any invalid styles, click the TechChecks button, and then click Generate Chapter Report under the appropriate series. The macro will run through the document and provide the information in a separate document.