Site Tools


style_guidelines

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
style_guidelines [2023/05/22 19:19] – [Layout/Formatting Guidelines] hogwildstyle_guidelines [2023/07/16 18:10] (current) – [Layout/Formatting Guidelines] -add that variables should be italicized hogwild
Line 10: Line 10:
   * Some wiki readers are not fluent in English. Please, choose your words carefully. \\   \\    * Some wiki readers are not fluent in English. Please, choose your words carefully. \\   \\ 
   * Avoid abbreviations that aren't standard across the industry or in common English.   \\ For example, anyone unfamiliar with Linux/Unix will not know that "wl" indicates a wireless interface. If it's not standard across the industry, explain it. Using "LAN", for example, is okay. It's common terminology. \\ \\    * Avoid abbreviations that aren't standard across the industry or in common English.   \\ For example, anyone unfamiliar with Linux/Unix will not know that "wl" indicates a wireless interface. If it's not standard across the industry, explain it. Using "LAN", for example, is okay. It's common terminology. \\ \\ 
-  * Avoid the word "Note". It's overused and rarely appropriate. If the content isn't a critical warning, consider putting it in the <WikiPageName Notes> section at the bottom of the page. We are developing guidelines/standards for writing and formatting notes. \\ \\  +  * Avoid the word "Note". It's overused and rarely appropriate. If the content isn't a critical warning, consider putting it in the <WikiPageName Notes> section at the bottom of the page. \\ \\  
-  * Avoid underlining. It's obsolete and inappropriate. Research shows it also makes things harder to read. \\ \\ +  * Avoid underlining. It's obsolete and inappropriate. Research shows it makes things harder to read. \\ \\ 
   * Please view other pages to see which types of text are capitalized and which are written in lower case. \\ \\    * Please view other pages to see which types of text are capitalized and which are written in lower case. \\ \\ 
   * Please use a spell checker. Firefox's spellchecker works well for this. \\ \\    * Please use a spell checker. Firefox's spellchecker works well for this. \\ \\ 
   * When referring to FreshTomato menus, please indicate as: //Menu///Submenu// . //  For example: //"Administration///Admin access"// . //\\ \\    * When referring to FreshTomato menus, please indicate as: //Menu///Submenu// . //  For example: //"Administration///Admin access"// . //\\ \\ 
-  * Avoid using quotation marks. They're almost never appropriate. If you're unsure, don't use them. \\ \\ +  * Avoid using quotation marks, except around filenames. They're almost never appropriate. If you're unsure, don't use them. \\ \\   
 +  * Please surround filenames with double quotation marks. For example, "wg0.conf".  \\ \\ 
   * Please use rounded brackets () . Square brackets are generally not appropriate here. \\ \\   * Please use rounded brackets () . Square brackets are generally not appropriate here. \\ \\
  
Line 23: Line 24:
 Following style guidelines makes pages easier to understand, more pleasant to read, and easier on the brain and eyes. Following style guidelines makes pages easier to understand, more pleasant to read, and easier on the brain and eyes.
  
-Focus on content Not everyone will use the same size monitor or resolutionSome use a mobile device or laptop to access the wiki \\ Different browsers and accessibility also affect how formatting appears (such as line break).+The FreshTomato wiki uses [[https://www.dokuwiki.org/dokuwiki|dokuwiki]] as its underlying software. It uses [[https://prosemirror.net/|ProseMirror]] as its editor.
  
-  * Add a meaningful title for each wiki page, and format it with the Heading1 format. \\  +Focus on content.  Not everyone uses the same size monitor or resolution. Some people use a mobile device to access the wiki. \\ Different browsers and accessibility also affect how formatting appears (for example, with line breaks). 
-  * Subheadings use the Heading2 format. \\  + 
-  * Subheadings below that use the Heading3 format. \\  + \\ 
-  * Indicate web interface menu paths like this: "//Administration///Admin Access" (Use to separate menu nodes). \\  + 
-  * Always use the standard Tomato theme when taking screenshots. This is set in the [[admin-access|Admin Access]] menu.+  * Add a meaningful title to each wiki page. Format it with the Heading1 format. \\ \\  
 +  * Subheadings use the Heading2 format. \\ \\  
 +  * Subheadings below that use the Heading3 format. \\ \\  
 +  * Indicate web interface menu paths using the name of the menu, unless there is another menu with a similar name.  
 +    * For example, you can refer to the Admin Access menu. However... 
 +    * You should add a "/" and top node when referring to the ///Bandwidth///[[bwm-realtime|Real-Time]] menu.\\ This will help prevent it from being confused with the //IP Traffic///[[ipt-realtime|Real-Time]] menu.\\ \\ 
 +  * Always use the "Tomatotheme when taking screenshots. This is set in the [[admin-access|Admin Access]] menu.
  
 \\ {{:pasted:20210921-184547.png|A screenshot in the Standard Tomato theme}}  \\   \\ \\ {{:pasted:20210921-184547.png|A screenshot in the Standard Tomato theme}}  \\   \\
  
-  * Avoid quotation marks. They are rarely appropriateand should be used only when quoting someone/ something directly, or when slang is used. \\  +  * Avoid quotation marks. In the context of this wikithey should be used only
-  * Avoid underlining. It's been obsolete since the 1980s. It makes text harder to read. \\  +    * When slang is used. 
-  * Avoid using the word “NOTE”. There is a section titled: "<Menu name> Notes" at the bottom of most pages. Put notes there. \\  +    * When expressing, something precise separate from the text body, such as a filesystem path. \\ \\ 
-  * Unless they are in a code window, command strings should be set in the ''monospace'' font, or in a callout box. \\  +  * Avoid underlining. It's been obsolete since the 1980s. It makes text harder to read. \\ \\  
-  * Variables should be italicized. \\  +  * Avoid using the word “NOTE”. There is a section titled: "<Menu name> Notes" at the bottom of most pages for notes. \\ \\  
-  * Process/Module names should be italicized to distinguish them from the main text. \\  +  * Unless they are in a code window, command strings should be set in the ''monospace'' font, or in a callout box. \\ \\  
-  * Avoid using dividing lines. Better spacing, and other formatting methods work better. \\+  * Variables should be //italicized to distinguish them from the main text//\\ \\  
 +  * Process/Module names should be italicized to distinguish them from the main text. \\ \\  
 +  * Avoid using dividing lines. They are mostly obsolete. Better spacing, and modern formatting methods work better. \\ \\
  
  
style_guidelines.1684779562.txt.gz · Last modified: 2023/05/22 19:19 by hogwild