The Jak and Daxter Wiki's guideline is used to document good practice, as established through community consensus.

Definition of consensusEdit

Consensus occurs when editors reach an agreement through discussion, upon which decisive action is taken. Consensus is not achieved via popular vote, but instead by the cogency of the presented arguments, and is formally established by article edits ensuant on concession and good faith.

After consensus is reached, it should then be documented, consulted, and enforced as necessary. Thorough but concise accounts of important decisions should be documented on this page, a relevant help page, or on the community forum for accessibility purposes, though the conversation that led to the consensus should remain in tact if possible.

Checklist for inclusionEdit

As the Jak and Daxter Wiki is, by nature of being a wiki, subject to contribution from any given individual, the community uses a checklist to determine what is kept or removed, or declined being added to begin with.

  • Articles — An article's subject has to be notable, unique or specific to the Jak and Daxter universe, in order to be kept or approved, so as to ensure it is of practical and encyclopedic value to the reader. The subject has to "stand on its own two feet", so to speak.
  • Information
    • All content must be cross-verifiable. Contentious or non-truistic claims should be supported by footnotes to reliable sources (extraordinary claims require extraordinary evidence, simple claims require simple evidence), in order to ensure the integrity and reliability of the website.
    • Footnotes should reference game scripts, mission names, data pages (like character statistics), official websites, page numbers (for strategy guides or other books), or timestamps for videos. Any references requiring greater generality are usually unnecessary.
  • Categories, files, and templates — Put simply, these must have unique and practical value. Ensure they are not duplicates and that they will be used appropriately, and that they are consistent with established conventions.

Style manualEdit

In order to establish cohesion across the project, the Jak and Daxter Wiki uses the following style manual as a general guideline. However, for English practice, proper formatting, and editing style, see Wikipedia's Manual of Style. For help with introductory wiki formatting, see Help:Contributing.

  • Capitalization — As in-game capitalization is inconsistent and often unjustified, use proper English capitalization instead: Only proper nouns should be capitalized while common nouns should not.
  • Puncutation
    • Logical punctuation is preferred over standard punctuation. See MOS:LQ for more details.
    • Place all footnotes within reasonable proximity of the relevant information, after all punctuation.
  • Locale — Because Naughty Dog is a US-based company, and the Jak and Daxter series is a US original property, the wiki is considered US-centric, and thus prefers American English and conventions.
  • Article titles and section headers — Article titles and section headers should use sentence case instead of title case (except when the subject name itself is a title, such as with game titles or scene names).
  • Title convention
    • Article titles should be determined by weighing all available sources for a subject's name, factoring both reliability and quantity. All notable alternative names should be included in the article's lead section, as well as given redirects. (See Forum:Nomenclature.)
    • For names from within a game, the article should be titled after its subject's most common name, with prefixes omitted (Veger instead of "Count Veger"), and surnames included (Samos Hagai instead of "Samos the Sage").
    • For characters with multiple names, their latest self-identity should be used (e.g. Errol instead of "Erol", or Mizo instead of "G.T. Blitz").
  • Main image — An article's main image should be of its subject's latest appearance (such as with Jak), except when it is significantly more represented otherwise (such as with Tess or Keira Hagai).
  • Writing styleConcision determines how information is conveyed, while encyclopedic value determines what and how much information is conveyed. Aim to be as comprehensive as possible while using no more words, and no more complex or unusual words, than necessary.
  • Scripts — Script pages are articles that contain the full verbal transcript of the game in question, and include any important on-screen text. They are not the original scripts but instead transcripts from the final product.
    • Because each game functions differently, customized guidelines and notes for how the script was organized during transcription should be included in the lead section of that page. Such notes supersede this guideline where there is conflict to ensure internal consistency—however, this guideline should otherwise be used and referenced for cross-article consistency.
    • Separate lines should be double spaced and indicated by the character's name in bold, followed by a non-bold colon.
    • Base transcripts on actual spoken diction (per English rules) as opposed to the subtitles, as they are sometimes incorrect, and the capitalization, punctuation, and emphasis are frequently incorrect.
    • Never embolden or capitalize emphasized words or phrases. Instead, italics should be used, but only sparingly.
    • In-game lines (as opposed to cutscene lines) should have their own sections, suffixed with (gameplay).
    • Descriptions of non-verbal actions should be omitted, though context-dependent lines should be indicated in parentheses.
      • Parenthetic context indications should be placed single-spaced above the relevant line, and double-spaced if there are more than one relevant lines. They should be sentence-formatted, using sentence case and periods within the parentheses.
    • Script page section headers should be named after their cutscene names (found in scene players), or their corresponding mission names (found in mission lists, level select, or in-game prompts).
    • Lines should be separated based on their execution. Just because consecutive lines are spoken by the same character does not mean they're part of the same line.
    • Enclose words in square brackets that may or may not be spoken depending on the variation of the line.
  • Article structure — Use the most appropriate article structure as determined by general consensus. Use existing articles, especially popular ones (or featured articles if applicable), as examples. In general, an article should always contain a lead (also called an intro or lede), and a body.
    • The lead should be a concise but comprehensive overview of the subject, omitting no uniquely identifying factors but not going into too much detail. In some cases, some or all sections can be merged into the lead depending on the length of the article and the necessity of split-up sections.

User conductEdit

To preserve a constructive, collaborative environment, all users are expected to adhere to a set of conduct guidelines:

See alsoEdit

Policies involving administrative or otherwise technical operations of the site are documented in the "Help" namespace. The most important are listed below, but all can be found at Category:Help pages.

Disjunct consensuses related to specific, individual cases are documented in the "Forum" namespace, and can be found at Forum:Wiki discussion.

Category-specific consensuses are documented on the category page itself. Template-specific consensuses are documented in the template's documentation.