The Vault:Terminal content policy

	For general help with wiki markup, see Help:How to edit a page.

 

Policies & guidelines Policies Administration Content Attribution of content Images and videos Terminal content policy Guidelines Article layout Character article layout Creature article layout Faction article layout Item article layout Location article layout Quest article layout Content organization Editing Referencing User conduct Other Skin selection

This page contains The Vault's terminal content policy. It describes how to format and arrange terminal data pulled from the files of Fallout games based on the Gamebryo and Creation engines.

Policies set general rules for the wiki's administration and its content. Any registered editor is free to edit this page to improve its readability as long as the essence of the article remains unchanged. If you would like to suggest content changes or propose a new policy or guideline, please use the wiki discussion forum. See the policies and guidelines page for an overview of this wiki's policies and guidelines.

Raw Data

• Raw data should be pulled directly from the game's files when practical and include the following information, where available: EditorID, FormID, contents, and any additional information pertinent for wiki use (such as model used).

Terminal pages layout

• All pages containing terminal transcripts should be distinguished by the terminals suffix (or terminal, in case there is only a single one on-location), appended to the location name for the relevant terminal.
  • If the location name is unavailable, such as with generic terminals, a name describing its function is used.
• Terminals are sorted according to relevancy. If relevance cannot be established clearly, alphabetic order is used.
• Terminals use descriptive names, derived from their owner, content, function, or editor ID, for ease of navigation.
  • The name as it appears in the game, editor ID, and form ID should be noted.
• Shared content should only be transcribed once per page and the contents linked to from relevant terminals.
• Terminals with generic content, such as turret control, safe, door terminals, are linked to under a separate head, rather than transcribed in full.
• If pages are difficult to navigate due to the amount of terminals, they should be divided into additional pages, distinguished by location (such as The Institute terminals (BioSciences) or H&H Tools Factory (upper floor)).

General guidelines

• Navigation and usability are key. If the page is cluttered and the table of contents cannot be understood at a glance, the page requires revision.
  • Existing terminals pages should be converted to include Template:Terminal header and Template:Terminal submenu to properly distinguish individual terminals.