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 17:56] – [Text Content Guidelines] hogwildstyle_guidelines [2025/03/09 15:31] (current) – [Layout/Formatting Guidelines] -Format-add spacing at end of page hogwild
Line 7: Line 7:
 ===== Text Content Guidelines ===== ===== Text Content Guidelines =====
  
-  * Please **choose your words carefully**. Some wiki readers aren't fluent in English. +  * Please **choose your words carefully**. Some wiki readers aren't fluent in English. \\ \\  
- \\ +  * Unless explaining complex concepts, please keep things **brief and concise. **\\ We aim to make the documentation simple and easy to read, even for beginners.  \\ Most **content is not meant to read like a reference manual**. Extra "precision" \\ can overwhelm readers. \\ \\  
- +  * Add a **meaningful title** to every wiki page. Format it with the Heading1 format.  \\ \\ 
-  * Unless explaining complex concepts, please keep things **brief and concise. **\\ We aim to make the documentation simple and easy to read, even for beginners.  \\ Most **content is not meant to read like a reference manual**. Extra "precision" \\ can overwhelm readers. +  * **Avoid abbreviations not standard across the industry** or in common English.   \\ For example, anyone unfamiliar with Linux/Unix may not know that "wl" indicates \\ a Broadcom wireless interface. If it's not industry standard terminology, explain it. \\ However, using "LAN", is fine. It's common industry terminology. \\ \\  
- \\ +  * **Avoid **using **the word: "Note"**.  It's overused, and doesn't add meaning. \\ If the content isn't a critical warning, consider putting it in the\\ "Notes and Troubleshooting" section at the bottom of the page. \\ Otherwise, try bolding just a few of the most important words. \\ \\  
- +  * **Avoid underlining**. It's obsolete and makes things hard to read. \\ \\ 
-  * Add a **meaningful title** to every wiki page. Format it with the Heading1 format.  \\ +
- \\ +
- +
-  * **Avoid abbreviations not standard across the industry** or in common English.   \\ For example, anyone unfamiliar with Linux/Unix may not know that "wl" indicates \\ a Broadcom wireless interface. If it's not industry standard terminology, explain it. \\ However, using "LAN", is fine. It's common industry terminology. +
- +
- \\ +
- +
-  * **Avoid **using **the word: "Note"**.  It's overused, and doesn't add meaning. \\ If the content isn't a critical warning, consider putting it in the\\ "Notes and Troubleshooting" section at the bottom of the page. \\ Otherwise, try bolding just a few of the most important words. +
- \\ +
- +
-  * **Avoid underlining**. It's obsolete and makes things hard to read. +
-\\ +
   * Check other pages to see which kinds of text content are capitalized \\ and which are written in lower case. \\ \\    * Check other pages to see which kinds of text content are capitalized \\ and which are written in lower case. \\ \\ 
   * Check spelling with your browser's spell checker. \\ \\    * Check spelling with your browser's spell checker. \\ \\ 
Line 38: Line 25:
 ===== Layout/Formatting Guidelines ===== ===== Layout/Formatting Guidelines =====
  
-Following style guidelines makes content easier to read, and easier to understand. \\ It also reduces stress on the brain and eyes while reading. +Following style guidelines makes content easier to read, and easier to understand. \\ It also reduces stress on the brain and eyes while reading. \\ \\
- +
- \\+
  
 The wiki uses [[https://www.dokuwiki.org/dokuwiki|dokuwiki]] as its underlying software. The wiki uses [[https://www.dokuwiki.org/dokuwiki|dokuwiki]] as its underlying software.
  
-It uses [[https://prosemirror.net/|ProseMirror]] as its editor. +It uses [[https://prosemirror.net/|ProseMirror]] as its editor.  \\ \\
- +
- \\ +
- +
-  * **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 features also affect how formatting appears (such as line breaks). +
- +
- \\ +
- +
-  * **Subheadings use the Heading2** format, and subheadings below that, Heading3.\\ +
- +
-\\+
  
 +  * **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 features also affect how formatting appears (such as line breaks). \\ \\ 
 +  * **Subheadings use the Heading2** format, and subheadings below that, Heading3.\\ \\ 
   * **When taking screenshots**, always use the "Tomato" theme (set in [[admin-access|Admin Access]]).\\  \\ {{:pasted:20210921-184547.png?497|A screenshot in the Standard Tomato theme}}  \\   \\  \\ In general, please use this syntax for naming screenshots files for upload:\\ ''"top level node name-bottom level node name-section name-release.png'' \\ \\ \\ For example, a screenshot of the Options section in the //Basic///DHCP Reservation menu \\ should be named "basic-dhcp reservation-options-2024.1". \\ \\    * **When taking screenshots**, always use the "Tomato" theme (set in [[admin-access|Admin Access]]).\\  \\ {{:pasted:20210921-184547.png?497|A screenshot in the Standard Tomato theme}}  \\   \\  \\ In general, please use this syntax for naming screenshots files for upload:\\ ''"top level node name-bottom level node name-section name-release.png'' \\ \\ \\ For example, a screenshot of the Options section in the //Basic///DHCP Reservation menu \\ should be named "basic-dhcp reservation-options-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" \\  \\    * 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. \\ \\  
 +  * Screenshots in bitmap formats should be scaled/resized in even \\ multiples of their original size. Otherwise, they may appear blurry. \\ \\
  
-  * Please wrap bulleted text at no more than about 40% frame width.It makes things much easier to read/follow. Shorter bulleted portions should be wrapped even earlier for reading ease. +  * **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. \\ \\
- +
-  * Screenshots in bitmap formats should be scaled/resized in even \\ multiples of their original size. Otherwise, they may appear blurry. +
- +
-\\ +
- +
-  * **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.1741456578.txt.gz · Last modified: 2025/03/08 17:56 by hogwild