Style+Guide

Style guide....

Some suggestions:

code Some suggestions....
 * **DESIGN •** The Finishing Touches page also offers a number of suggestions for improving the design of pages.
 * **STYLES •** To keep styles consistent, and to get the most out of what the current iteration of Wikispaces can do, it's imperative to learn how to use both the Visual Editor as well as the WikiText Editor.
 * For simple text entry, placement of images & widgets, and inserting links, the Visual Editor works just fine.
 * For adding references, detailed page layout and formatting, and table creation/adjustment, the WikiText Editor is invaluable. Here is a page which shows the coding needed to accomplish special formatting.
 * **NO CSS •** Currently, Wikispaces does **not** allow style sheets at the basic (free) level. Advanced levels, which must be purchased, provide CSS capabilities. Until those are acquired, the use of Wikispace's codes are necessary to achieve consistent formatting across pages.
 * **HEADINGS •** The formatting used for the headings on this site are coded as follows; the easiest method of doing this is just to copy the code from one page to another or to use the default template when creating a new page. (**Note**: returns have been inserted into the code example below to make it easier to read. They should __**not**__ be used in the actual code.)

code

>> **This:** code
 * **TEXT QUOTES •** To create a quotation formatted as below with horizontal rules bounding the quotation, the following codes should be used before and after the text.

> Everyone thinks. [1]

code >> **Gives this:**

> Everyone thinks. [1]

>> **This:** code  "I've got happy feet!" code >> **Gives this:** "I've got happy feet!" **Steve Martin** > The following examples shows the progression for having equal columns.
 * **OTHER QUOTES •** Occasionally, quotes are used to break up the page and to provide additional commentary. These are quotes that are attributed to specific people (possibly geniuses) and not explanatory material from the text. Coding for those is as follows. Again, returns have been used to make this easier to read. To get the actual coding, use the WikiText Editor.
 * Steve Martin**
 * **TABLES •** Table cells in Wikispaces do not accept proportional spacing. This makes it difficult to make a row, or a table, centered on the page or to get columns to be equal widths. The problem can be solved by:
 * creating a special row and formatting it as a header row which will remove the cell boundary lines;
 * putting an equal series of n-dashes (or other characters: the = sign works well) into those top cells;
 * setting the text color of those series to white;
 * using a 2 rows x 1 column format is useful for centering a widget or graphic if it won't center otherwise.


 * **Example 1** ||  ||
 * A typical table. || The cells expand to the length of the text in each. ||
 * A typical table. || The cells expand to the length of the text in each. ||


 * **Example 2** ||  ||
 * Just under 60 n-dashes (opt-hyphen on a Mac keyboard) have been inserted into each column. This allows the text to wrap... || ...even when the amount of text in each column varies. ||
 * Just under 60 n-dashes (opt-hyphen on a Mac keyboard) have been inserted into each column. This allows the text to wrap... || ...even when the amount of text in each column varies. ||


 * **Example 3** ||  ||
 * The last step is to make those dashes white (hex: #ffffff) which makes them "disappear" from the page. || This is also useful for making photos line up properly, although it also helps if the photos' dimensions are sized similarly. ||
 * The last step is to make those dashes white (hex: #ffffff) which makes them "disappear" from the page. || This is also useful for making photos line up properly, although it also helps if the photos' dimensions are sized similarly. ||