Cyberpunk Wiki:Manual of Style/Quest guide

This is a quest layout which is encouraged to use for all quest articles on the wiki.

Lead section
The lead section is anything included before the table of contents and/or the article content. With the exception of the introductory text, they are optional, depending on the situation, and must follow this order:
 * 1) Disambiguation links if there is another article of the same name, or may be confused with another.
 * 2) Article maintenance tags Alternatively, the maintenance tags can be included within a specific section of the article, with the exception of "stub" which must always in the lead section.
 * 3) Infobox/transformer template. They are generally wrapped in   tags.
 * 4) Short introductory text, including the quest name in Bold followed by information about which game the quest appears in, which chapter of the game, any relevant information about the sequence of completing this quest in relation to other quests etc.
 * 5) Table of contents, which generally appears after the lead, provided there is more than four headings. If the page is long but does not have any table of contents, you may manually add it with.

Walkthrough
Walkthrough should list the objectives associated with the walkthrough in subheader text for easy access in the table of contents. Use discretion when copying the names of the objectives, if it is too long consider shortening the objective but keeping the same meaning for instance: "Use the interact button to discover the Location of the Door" shortened to "Locate the Door" Include all quest objectives if able. For quests with branching or optional objectives indicate as such.

Note: Sections should be formatted like this in italics

Journal Entry
This is where to put the complete journal entry for a quest/character. To do so, italicize each paragraph and make sure to indent using a colon in the source editor like below. Note that line breaks will look extra wide in edit mode, but will go back to normal in the final version. For quests that don't have journal entries, it's ok to put "This quest has no journal entry."
 * This is an example of a journal entry layout. Make sure to add a line break so paragraphs don't butt up against each other (unless it is so in the game format).


 * For choices, also indent and make bold (don't italicize)
 * then double indent the choice underneath (using :: ) to indicate it's only shown if the choice above is made. Keep adding : for more nesting choices.

Objectives
This area is for the quest's objectives and should be marked with bullet points. For some quests that have a lot of objectives, indenting (using ** in the script editor or simply hitting tab when on the bullet point) can help sort them. Note that for quests that don't appear in the journal, it is fine to say "This quest has no journal objectives."
 * this is an example objective
 * this is a nested objective

Trivia
Trivia should be listed using bullet points. This includes anything not related to the game (like easter egg examples would go here).
 * Anything that is not a note or bug goes here

Bugs
Bugs should be listed using bullet points. This includes examples that were not intentionally meant to be in the game. Additionally, you may include one link to a fan-made bug fix per bug. However, the link should be removed once it has been patched.
 * Anything that is not a note or trivia goes here

Videos
Only one quest walkthrough/playthrough is allowed per article and it should generally be free from advertising of an individual's youtube channel or in other ways support a particular person as this is contrary to the spirit of a wiki community. Other videos may explain particular parts of the quest: boss fights, loot locations, bugs etc.

Maps
Any map(s) relevant to the quest can be included here. This can include a map from the customized map tab or pictures of maps from the game. If putting up pictures, use  for uniform formatting.

Gallery
Use  to display the pictures in a table.

Navboxes
While not a heading onto itself, this is where any navboxes go, with a few exceptions (for example, a page that has no information other than a really long infobox, pushing all other content out of sight).