Laserfiche WebLink
paper size, btandard 8;c,-bv-1;3-mch paper is most desirable <br />~.~ccausc it is simply thc most .wi&iv used attd recognized. Many <br />codes are printed ~n smaller baper'sizes used by many legaJ ' <br />publishers. With less text on,ach page, readeri must'turn more <br />pages to find informafon and find it awkward to photocopy. <br />Text printing should be i~ portrai~ ~text parallel to thc short <br />edge of thc pagc~ rather thanilandscapc (parallel to the long edge) <br />format. Avoid mixing them-~-it becomes clumsy. <br />Either a type style with serifs (letter extensions), such as the <br />type on this page, or a belvetjca sanserif style works well. They <br />ate widely used and easy to r~ad. Avoid stylized type. <br />£ont iefers to a type's stvlle, weight, a,~d height· ! <br />T)'pe sizes are measured m points. Twelve-point is <br />common, although I I - or e~en 1 ()-point type is easily ,~ <br />read. Smaller type alk)ws mo~'c information on each <br />page, which reduces page tu?r. ning and allows quicker <br />access to information. A mixiof 12-point type for text · <br />and I O-point t),pe for tables hnd charts works well. <br />Use larger type for major ~apter, division, and <br />section headings following a h.~ieratchv~' to denote their <br />relative importance. Assigning~bold attributes to major · <br />headings will further cnhancekeadabilirv. Type size and <br />attributes should bc consisten~throut~hout the code. <br />Use headers and footers. ~eader~s are printed at the <br />top of each page attd footers ~t the bottom. Both <br />contain information such as cities and page references <br />and are an indispensable nav~igational aid. The), also <br />contribute to the code's thematic look. Headers <br />should include the name of the chapter and its <br />number (e.g., Chapter 12: P4rking and Loading <br />Regulations), The first sectioln number that appears <br /> Sec.on numbers should <br />on each page is also useful. ~ ' <br />appear on the feeder's outsid{: edge where they are <br />most visible when turning pa~es. Section numbers are · <br />important because they are uged for cross-referencing <br />and are usually the most freqt~entl)' referenced <br />number. A dividing line should separate the bottom <br />of the header from the text b~ow. · <br /> · ~ <br />Footers should contain the't>age number and may <br />include the section name and {number. Man3' codes <br />contain a reference to the codei's adoption or amend- <br />ment date and ordinance number. Ifm~o or more <br />sections appear on a page, hovCever, this reference does <br />not help identify the section td which the reference <br />applies, it also tJreates needlessic}utter. <br />Where there is a choice between single- and double- · <br />column text, a single column is ~referable. A single <br />column eliminates a center matin. Double columns <br />make it difiqcuk to incorporate ckrtain tables and graphics. <br />Margins should be wide enough to allow for <br />binding and should not cram~ the text. Margins <br />should be proportional to the .}ype size. <br />Single spacing is preferable.~ However, double spacing <br />between number sections and }ubsections creates a clear text <br />delineation with a less crampe/~ look. <br />The use of indentations should work tn concert with chapter, <br />division, and ~ection headings.lEach similar level of subdivision <br />should follow the same indent{lion line, increased for the next <br />lower subdivision. Never inderJt just the first line and then <br />return to the standard margin ~n the following line. This is <br />standard legal format for man? zoning codes but is confusing to <br />most people. The position of the margin should visually tell the <br />reader whether the text is a sec!ion or subsection. <br /> <br /> Pay careful attention to page numbering. Sequential <br />numbering starting with page one is the easiest: most books arc <br />numbered this way. But this creates the need to add decimals to <br />the page numbers when new pages arc inserted. Unless the <br />entire code is renumbered following each amendment, this <br />system becomes increasingly difficult to usc. <br /> A more flexible method is to number pages sequentially <br />preceding each page number with a major division or chapter <br />number. Each major division or chapter should begin on page 1. <br />Thus, chapter 23 would begin with page 23-1 and follow with page <br /> <br /> Cross Referencing <br /> <br />Cross reference all provisions <br />that rely on or memion other <br />code provisions. <br />Avoid referencing ordinance <br />numbers, except at the end of <br />each section for historical <br />purposes only. <br />All references should include <br />the lowest section, division, <br />or chapter number possible. <br />Don't cite a chapter when a <br />section is more relevant. Page <br />references are excellent and <br />should be used depending on <br />how amendments affect page <br />numbering. <br />All references should include <br />a number and its full title, for <br />example, "Section ]2.34·· Site <br />standards, page 18-3. " <br />Consider italics for emphasis. <br />Highlight (bold or italic) all <br />references to make them <br />stand out from surrounding <br />text. <br /> <br />Minimize use of <br />"incorporated herein by <br />reference." include the <br />referenced laws, regulations, <br />or standards if they are <br />frequently used, such as <br />handicapped parking <br />standards. <br />Reference related codes, such <br />as the subdivision code, <br />traffic codes, and housing <br />codes, that ma;' affect zoning <br />regulations. <br /> <br />23-2, 23-3, etc. If chapter 23 is <br />amended by adding new pages, the <br />chapter can be reprinted without <br />affecting subsequent chapter numbering. <br /> Printing the code on both sides of <br />the paper makes locating information <br />quicker, saves paper, and may reduce <br />your printing cost. Be sure that headers <br />and footers are printed on the outside <br />edge of alternating pages, a simple task <br />for most word processing soft,,are. <br /> Finally, begin each major new <br />division or chapter on the right-hand <br />page. This will make the new division <br />or chapter easier to find. <br /> Cross Referencing. Proper cross <br />referencing is critical for easy readabil- <br />i~'. Cross referencing binds those parts <br />of the code that depend on one <br />another, thus avoiding redundant,. <br /> Many codes ignore cross referencing <br />altogether, cite only the section or <br />chapter numbers, or worse, reference <br />only an ordinance number: <br />"N'orwithstanding anythi,g in this <br />chapter, in Secrio, ].7.92.]00, or <br />ebewhere in this code so the contras.,, <br />design review decisions of the Cultural <br />Heritage Commission pursuant w <br />Chapter ] 7.52 shall be subject to appeal <br />and/or call for review as prescribed <br />hereunder for decisions of the JDes~ <br />Review Committee. "Most readers are <br />not aware of the distinction between <br />codes, chapters, and sections, a <br />problem made worse by the lack of <br />reference titles. <br /> The trend toward unified codes <br />underscores both the importance of <br />cross referencing and the value of <br />including, rather than referring to, <br /> <br />related regulations. (See "Zoning and Subdivision Codes, <br />Unite!", Planning, November 1993). <br /> Tables and Graphics. Man)' new codes are simplifying the way <br />zoning district uses and standards are presented. Most are <br />converting text into rabies and combining separate but similar <br />zoning districts into single tables. This substantially reduces the <br />number of pages and makes it easier to answer questions like, <br />"What zoning districts allow multifamily dwellings?" Tables also <br />make it easier to include information such as the type of permit <br />required for each use in each zoning district. Older codes tend to <br />have separate lists of permitted, conditional, and accessoO, uses <br />and development standards for each zoning district. <br /> <br />'/7 <br /> <br /> <br />