Jump to content

Help:Adding Regulations: Difference between revisions

From CVEO Wiki
Anthony (talk | contribs)
Created page with "__NOTOC__ = Help: Adding Regulations = This page outlines the standard formatting for adding new Title 49 regulations to the CVEO Wiki. All regulations must use the <nowiki>{{Violation}}</nowiki> template to ensure they appear correctly on the Master Dashboard and the Printer-Friendly Cheat Sheet. == 1. Page Architecture == All regulations should be consolidated into their top-level section (e.g., <code>391.11</code> or <code>393.9</code>). Do not create new pages for..."
 
Anthony (talk | contribs)
No edit summary
Line 19: Line 19:
|TypicalAction = Out of Service / Citation
|TypicalAction = Out of Service / Citation
|StateNotes =  
|StateNotes =  
|ReferenceLinks = https://www.searchenginejournal.com/link-title-attribute/335415/
|ReferenceLinks = [https://www.searchenginejournal.com/link-title-attribute/335415/ page title]
}}
}}
</pre>
</pre>
Line 31: Line 31:
* '''TypicalAction:''' Standard enforcement action (e.g., Warning, Citation, OOS).
* '''TypicalAction:''' Standard enforcement action (e.g., Warning, Citation, OOS).
* '''StateNotes:''' Enforcement context specific to Illinois.
* '''StateNotes:''' Enforcement context specific to Illinois.
* '''ReferenceLinks:''' Use the format: <code>https://www.searchenginejournal.com/link-title-attribute/335415/</code>. (Note: Links are configured to automatically open in new tabs).
* '''ReferenceLinks:''' Use the format: <code>[https://www.searchenginejournal.com/link-title-attribute/335415/ page title]</code>. page title would be what to call the page. (Note: Links are configured to automatically open in new tabs).


== 3. Regulatory Guidance & Memos ==
== 3. Regulatory Guidance & Memos ==

Revision as of 14:32, 23 May 2026

Help: Adding Regulations

This page outlines the standard formatting for adding new Title 49 regulations to the CVEO Wiki. All regulations must use the {{Violation}} template to ensure they appear correctly on the Master Dashboard and the Printer-Friendly Cheat Sheet.

1. Page Architecture

All regulations should be consolidated into their top-level section (e.g., 391.11 or 393.9). Do not create new pages for sub-paragraphs; use the <tabber> architecture instead.

2. The Violation Template

Every subsection must be wrapped in a {{Violation}} template. Copy the block below and paste it into the appropriate tab.

{{Violation
|Section = 
|Description = 
|OOS = 1
|ViolationCategory = Driver
|InspectionLevel = Level 3, Level 2, Level 1
|TypicalAction = Out of Service / Citation
|StateNotes = 
|ReferenceLinks = [https://www.searchenginejournal.com/link-title-attribute/335415/ page title]
}}

Field Guide:

  • Section: The exact regulation code (e.g., 391.11(b)(2)).
  • Description: A concise explanation of the violation.
  • OOS: Enter 1 for Yes (triggers red alert), 0 for No.
  • ViolationCategory: Use either Driver or Vehicle.
  • InspectionLevel: (e.g., Level 3, Level 2, Level 1).
  • TypicalAction: Standard enforcement action (e.g., Warning, Citation, OOS).
  • StateNotes: Enforcement context specific to Illinois.
  • ReferenceLinks: Use the format: page title. page title would be what to call the page. (Note: Links are configured to automatically open in new tabs).

3. Regulatory Guidance & Memos

If you have a PDF memo, upload the file first, then anchor it at the bottom of the page using this tag:

<span id="Guidance"></span>
== Regulatory Guidance & Memos ==
<pdf width="1000" height="600">File:Your_Filename_Here.pdf</pdf>

4. Navigation

Always include the "Quick Jump" navigation bar at the top of the page so field units can instantly reach the guidance:

<div style="background: #f8f9fa; padding: 10px; border: 1px solid #c8ccd1; margin-bottom: 15px;">
'''Quick Jump:''' [[#Guidance | Regulatory Guidance]] | [[#top | Return to Top]]
</div>