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 [2025/03/08 18:29] – [Layout/Formatting Guidelines] hogwildstyle_guidelines [2025/03/09 15:31] (current) – [Layout/Formatting Guidelines] -Format-add spacing at end of page hogwild
Line 36: Line 36:
   * For screenshots of just one or few settings options under one section, use syntax: \\ ''"top level node name-bottom level node name-option name to option name-release.png"''  \\ \\ \\ Example: "advanced-wireless-roaming assistant to fragmentation threshold-2024.1" \\  \\    * For screenshots of just one or few settings options under one section, use syntax: \\ ''"top level node name-bottom level node name-option name to option name-release.png"''  \\ \\ \\ Example: "advanced-wireless-roaming assistant to fragmentation threshold-2024.1" \\  \\ 
   * Please save screenshots in .png format. Lossy formats are blurry, \\ and may reveal personal user data. \\ \\    * Please save screenshots in .png format. Lossy formats are blurry, \\ and may reveal personal user data. \\ \\ 
-  * Please wrap bulleted text at less than 50% frame width. \\ It makes things much easier to read/follow. Shorter bulleted portions \\ should be wrapped even earlier for reading ease. \\ \\+  * Please wrap bulleted text at less than 50% frame width. \\ It makes things much easier to read/follow. Shorter bulleted portions \\ should be wrapped even earlier for reading ease. \\ \\  
 +  * Screenshots in bitmap formats should be scaled/resized in even \\ multiples of their original size. Otherwise, they may appear blurry. \\ \\
  
-  * Screenshots in bitmap formats should be scaled/resized in even \\ multiples of their original size. Otherwise, they may appear blurry. +  * **Avoid quotation marks**. They should be used only: 
- +    When slang is used. 
-\\ +    When expressing something precise, separate from body text, such as a filesystem path. \\ \\
- +
-  * **Avoid quotation marks**. In the context of this wiki, they should be used only: +
-    When slang is used. +
-    When expressing something precise, separate from the text body, such as a filesystem path. \\ \\+
   * **Avoid underlining**. It's been obsolete since the 1980s and makes text harder to read. \\ \\    * **Avoid underlining**. It's been obsolete since the 1980s and makes text harder to read. \\ \\ 
   * **Avoid using the word “Note”**. Put notes in the Notes section that exists \\ at the bottom of most pages.\\ \\    * **Avoid using the word “Note”**. Put notes in the Notes section that exists \\ at the bottom of most pages.\\ \\ 
   * Except in a code window, **command strings should be set in the** ''monospace'' font, \\ or in a callout box.\\ \\    * Except in a code window, **command strings should be set in the** ''monospace'' font, \\ or in a callout box.\\ \\ 
-  * **Variables or process/module names should be italicized** to distinguish them from other text.+  * Avoid dividing lines. They're obsolete and make text hard to read. \\ Better spacing and modern formatting methods work better.
  
  \\  \\
  
-  * Avoid dividing lines. They're obsolete and make text hard to read. \\ Better spacing and modern formatting methods work better.//   //+ \\
  
  
style_guidelines.1741458546.txt.gz · Last modified: 2025/03/08 18:29 by hogwild