Jump to content
Toggle search
Toggle menu
  • 570 articles
  • 1.5K files
  • 136 users
  • 8.7K edits
Obby Wiki
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Obby Wiki Style Guide

From Obby Wiki
More actions

TL;DR

Do
Don't
  • Use US English.
  • Follow the style of existing pages.
  • Write neutral text.
  • Copy a subject's original casing; use sentence case when there is no subject.
  • Don't use capital letters excessively.
  • Don't use AI to write page content or generate images.
Need a clarification, or extra help? Ask other readers in the Discord server.

If something in an article doesn't follow any of these rules no matter its severity, you are encouraged to fix it.

This policy is still being worked on and is subject to change.

Related: Eligibility requirements, Rules & Guidelines, Terms of Use

1. General

  • Follow the Terms of Use, Rules & Guidelines, and be respectful at all times.

1.1. When these rules should apply

Different namespaces and types of pages have different rules apply or not apply. Refer to the scope key below in order to determine where a rule applies.

  • CContent pages: Mainspace articles and other content pages.
  • BBlogs: Blog posts.
  • TTalk & comments: Talk pages, comments, and other discussion.
  • DDocs: Project, help, and documentation pages.

1.2. The importance of these rules

Use the legend below to refer to the importance of each rule.

  • Required: You must follow this guideline.
  • Highly recommended: You are encouraged to follow this guideline or edit any pages that don't.
  • Nice to have: You should follow this if you can.
  • Unmarked/Preference: It is up to you.


2. Pages

2.1. Titles

Most pages are about a named thing. The title is that name.

Copy the subject's casing, or use sentence case if there isn't one
Content pagesMainspace articles and other content pages.
DocsProject, help, and documentation pages.
Highly recommended
You are encouraged to follow this guideline or edit any pages that don't.
If the page is an obby, person, studio, or another named subject, keep that name's original capitalization, including stylized all-caps or all-lowercase. If the title describes a topic instead of naming a thing, use sentence case and capitalize only the first letter, and any names inside it.
Do
Don't

Tower of Hell

Tower Of Hell

  • Tower of Hell
  • @lowercase_username
  • Guide to corner clips

Named subject: keep the original casing

  • Tower Of Hell
  • Guide To Corner Clips
  • Guide to Corner Clips

Don't convert a name into title case

Wiki and help pages use title case instead.

Helpful tips
  • MediaWiki cannot start a title with a lowercase letter. For an all-lowercase obby, type the name in {{ObbyGameInfobox}} and set {{DISPLAYTITLE:obby name}}.
  • Community pages already start with @, so lowercase usernames work as-is.
Use the full name instead of abbreviations
Content pagesMainspace articles and other content pages.
DocsProject, help, and documentation pages.
Highly recommended
You are encouraged to follow this guideline or edit any pages that don't.
When writing about a subject, use its full name instead of any abbreviation. You may want to make a redirect page for the abbreviation.
Use straight apostrophes and quotation marks
Content pagesMainspace articles and other content pages.
BlogsBlog posts.
Talk & commentsTalk pages, comments, and other discussion.
DocsProject, help, and documentation pages.
Required
You must follow this guideline.
Always use straight quotation marks and apostrophes, rather than curved or alternative ones.

2.2. Formatting

General page formatting rules.

Always include an excerpt or lead section at the top of the page
Content pagesMainspace articles and other content pages.
BlogsBlog posts.
Highly recommended
You are encouraged to follow this guideline or edit any pages that don't.
Place it above any header. It can be under a callout, like {{Stub}}, or an infobox, just not a header. This ensures that the page previews always work as intended. See more at § 2.3.1 Lead sections.

2.3. Sections and headings

Use headings to split up different sections of an article in order to make it more readable and accessible.

Markup
== Heading ==
=== Heading ===
==== Heading ====
===== Heading =====
====== Heading ======
= Heading =Never used

Spaces around the title are preferred for readability purposes. Don't skip a level.

Split articles into sections with headings
Content pagesMainspace articles and other content pages.
BlogsBlog posts.
DocsProject, help, and documentation pages.
Highly recommended
You are encouraged to follow this guideline or edit any pages that don't.
Separating articles into sections makes them easy to read and navigate.
Don't
  • Don't skip heading levels.
  • Don't wrap headings in other markup.
  • Don't use = Title = (shallow headings).
  • Don't reuse the same heading twice on one page, or its section link may point to the wrong place.

Not using = Title = applies retroactively and has not been applied to all pages yet.

Use title case for headings on content pages
Content pagesMainspace articles and other content pages.
BlogsBlog posts.
Highly recommended
You are encouraged to follow this guideline or edit any pages that don't.
Capitalize the first letter of each major word in a heading. This keeps headings consistent across the wiki's content pages. Minor words, such as a, of, and, and the, stay lowercase unless they start the heading.
Do
Don't

== Development Team ==

== Development team ==

  • Development Team
  • Promotional Codes
  • See Also

Capitalize the major words.

  • Development team
  • Promotional codes
  • See also

Sentence case is not used for content headings here.

Use consistent headings
Content pagesMainspace articles and other content pages.
BlogsBlog posts.
DocsProject, help, and documentation pages.
Highly recommended
You are encouraged to follow this guideline or edit any pages that don't.
Re-use headings that match your section as much as possible. If a similar page exists, it may be useful to re-use its headings. Many page types already have pre-determined headers for common sections.
Keep headings concise, unambiguous, and easy to read
Content pagesMainspace articles and other content pages.
BlogsBlog posts.
DocsProject, help, and documentation pages.
Nice to have
You should follow this if you can.
Keep headings short unless necessary to achieve clarity.
Do
Don't

== Gameplay ==

== What's the gameplay like? ==

  • Keep headings short, concise, and clear
  • Don't phrase a heading as a question
  • Don't include refer back to the subject
  • Don't be ambiguous
Don't number headings
Content pagesMainspace articles and other content pages.
BlogsBlog posts.
Nice to have
You should follow this if you can.
On content pages, don't number headings like '1. Title' or '2.3 Title', as it makes it harder to add new sections where they fit and isn't consistent with the rest of the wiki.
Don't use custom colors or fonts for headings
Content pagesMainspace articles and other content pages.
BlogsBlog posts.
Talk & commentsTalk pages, comments, and other discussion.
DocsProject, help, and documentation pages.
Required
You must follow this guideline.
Don't change the color of a heading or the font of it, as this may cause readability issues, especially on other themes and worse lighting conditions.
Do
Don't

== My Heading ==

== My Heading ==

Don't use additional markup
Content pagesMainspace articles and other content pages.
BlogsBlog posts.
Required
You must follow this guideline.
Except for the heading markup itself, don't use additional markup to style headings. Keep them as simple and readable as possible.
Don't
  • Don't put links inside a heading.
  • Don't place templates, images, or icons in a heading.
  • Don't add citations or references to a heading.

2.3.1. Lead sections

A lead section or excerpt is the first text at the top of an article, before any header. It should remain short (1-3 paragraphs at most) while describing the subject enough for a reader to understand what the article is about just from the excerpt. The first part of lead sections are also used for page previews, so keep it relevant and easy to read. A few tips:

  • The lead section acts as a summary of sorts. It should not be used for details that fit into other sections.
  • It should be no more than three paragraphs.
  • If the article has a subject, mention it early and bold it.

See a visual example below.

2.4. Layout

A simple article should have at least a lead. The Universal tab shows what the default order of elements should look like, but you can use the other tabs to see specific page types.

Layout
Always put the infobox at the top of the page.
Body
Lead
Lead1-3 short paragraphs saying what the page is about. Bold the subject in the first sentence.
Images (if there is no infobox)
Images (if there is no infobox)Only use images here when the page has no infobox, otherwise use the Media section.
optional
Content== Content ==
ContentAny regular page headings should go above any other supplementary sections.
Trivia== Trivia ==
TriviaShort facts that do not fit in any other section. Keep it to a few bullet points.
Media== Media ==
MediaImages and videos of the subject, split into sub-sections when applicable.
See Also== See Also ==
See AlsoA few closely related pages on this wiki.
Notes== Notes ==
NotesFootnotes that explain something without citing a source.
References== References ==
ReferencesEven if no references are on the page, still include this header with under it.
{{Infobox}}
InfoboxA card of key facts about the subject. It always goes first, above the lead.
Bottom matter
{{Navplate}}
NavplateA box of links that ties this page to related ones.
Maintenance templates
Maintenance templatesNotices asking other editors to fix or finish something on the page. Only applies to pages that need it.
{{Stub}}Stub notice
StubMarks a page that is still too short and needs more content.
{{Related}}Related articles
RelatedA short list of pages a reader may want to open next. Optional. Consider using the Related Articles parser function instead.
Parser functions
Parser functionsMagic words that change how the page is titled, indexed, or how it behaves. They are invisible but may interfere with other elements if placed before content.
{{SHORTDESC}}{{DISPLAYTITLE}}
Categories
CategoriesCategories group this page with similar ones. They appear in the page footer.
CategoryCategory
Always put the infobox at the top of the page.
Lead
Lead1-3 short paragraphs saying what the page is about. Bold the subject in the first sentence.
Gameplay== Gameplay ==
GameplayHow the obby actually plays: stages, mechanics, and difficulty.
Design== Design ==
Trivia== Trivia ==
TriviaShort facts that do not fit in any other section. Keep it to a few bullet points.
Development Team== Development Team ==
Development TeamWho made the obby. Credit people under the sub-sections below.
Core Developers=== Core Developers ===
Contributors=== Contributors ===
Media== Media ==
MediaImages and videos of the subject, split into sub-sections when applicable.
Thumbnails=== Thumbnails ===
Icons=== Icons ===
Trailers=== Trailers ===
Community Videos=== Community Videos ===
Promotional Codes== Promotional Codes ==
FAQ== FAQ ==
Monetization== Monetization ==
MonetizationAnything players can buy, such as passes and products.
Passes=== Passes ===
Badges== Badges ==
References== References ==
ReferencesEven if no references are on the page, still include this header with under it.
{{ObbyGameInfobox}}
ObbyGameInfoboxA card of key facts about the subject. It always goes first, above the lead.
Bottom matter
{{AlsoBy}}Navplate
AlsoByA box of links that ties this page to related ones.
{{Stub}}Stub notice
StubMarks a page that is still too short and needs more content.
Categories
CategoriesCategories group this page with similar ones. They appear in the page footer.
CategoryCategory
Always put the infobox at the top of the page.
Lead
Lead1-3 short paragraphs saying what the page is about. Bold the subject in the first sentence.
Obbies== Obbies ==
References== References ==
ReferencesEven if no references are on the page, still include this header with under it.
{{PlayerInfobox}}
PlayerInfoboxA card of key facts about the subject. It always goes first, above the lead.
Bottom matter
{{AlsoBy}}Navplate
AlsoByA box of links that ties this page to related ones.
{{Stub}}Stub notice
StubMarks a page that is still too short and needs more content.
Parser functions
Parser functionsMagic words that change how the page is titled, indexed, or how it behaves. They are invisible but may interfere with other elements if placed before content.
{{DEFAULTSORT}}
Categories
CategoriesCategories group this page with similar ones. They appear in the page footer.
CategoryCategory
Always put the infobox at the top of the page.
Lead
Lead1-3 short paragraphs saying what the page is about. Bold the subject in the first sentence.
References== References ==
ReferencesEven if no references are on the page, still include this header with under it.
{{GroupInfobox}}
GroupInfoboxA card of key facts about the subject. It always goes first, above the lead.
Bottom matter
{{AlsoBy}}Navplate
AlsoByA box of links that ties this page to related ones.
Parser functions
Parser functionsMagic words that change how the page is titled, indexed, or how it behaves. They are invisible but may interfere with other elements if placed before content.
{{DISPLAYTITLE}}{{SHORTDESC}}
Categories
CategoriesCategories group this page with similar ones. They appear in the page footer.
CategoryCategory
Always put the infobox at the top of the page.
Lead
Lead1-3 short paragraphs saying what the page is about. Bold the subject in the first sentence.
What It Covers== What It Covers ==
Staff== Staff ==
External Links== External Links ==
{{WikiInfobox}}
WikiInfoboxA card of key facts about the subject. It always goes first, above the lead.
Bottom matter
{{WikiNavplate}}Navplate
WikiNavplateA box of links that ties this page to related ones.
Categories
CategoriesCategories group this page with similar ones. They appear in the page footer.
CategoryCategory
Lead
Lead1-3 short paragraphs saying what the page is about. Bold the subject in the first sentence.
Section== Section ==optional
References== References ==
ReferencesEven if no references are on the page, still include this header with under it.
optional
Bottom matter
Categories
CategoriesCategories group this page with similar ones. They appear in the page footer.
CategoryCategory

Layouts are subject to change.

2.5. Disambiguation

When two or more subjects share the exact same name, a title alone cannot tell them apart. This is when disambiguation pages come in.

Give the obby the plain title, disambiguate the rest
Content pagesMainspace articles and other content pages.
Highly recommended
You are encouraged to follow this guideline or edit any pages that don't.
On this wiki the obby always takes priority, so it keeps the plain title with no parentheses. Any other subject that shares the name, such as a studio or person, adds a distinguishing detail in parentheses, in lowercase.
Do
Don't
  • Obby Name
  • Obby Name (studio)

An obby is always entitled to the bare name, any other subject must take a lowercase detail.

  • Obby Name (obby)
  • Obby Name (Studio)

Don't add parentheses to the obby, or capitalize the detail.

Helpful tips
  • Give each disambiguated page a hatnote or notice so readers can jump to the other meaning.

3. Prose and other text

Rules that apply to links on content pages.

Internal links are links to pages that are on the Obby Wiki.

Link to relevant pages
Content pagesMainspace articles and other content pages.
Nice to have
You should follow this if you can.
Do
Don't
  • Link to important pages, like sub-genres such as Difficulty Chart Obby when they are naturally mentioned in text.
  • Link to non-existent pages that are relevant. This marks a page as wanted. For example, for an obby created by @MissingDeveloper, you should link to that missing page.
  • Link to every single page, including real pages that aren't relevant.

External links are links to URLs outside the Obby Wiki.

Before using an external link, please make sure it is necessary and consult the following criteria:

  • Don't repeat links already in an infobox or another template.
  • If the link is relevant to the topic or an item showcased (e.g., a link to a badge).
  • If you have been granted explicit permission, or if another documentation page grants you implicit permission for another purpose.

This does not apply within comments or talk pages.

3.2 Writing style

Rules that apply when you are writing wikitext.

Use US English for consistency
Content pagesMainspace articles and other content pages.
BlogsBlog posts.
Talk & commentsTalk pages, comments, and other discussion.
DocsProject, help, and documentation pages.
Highly recommended
You are encouraged to follow this guideline or edit any pages that don't.
Always use US English when writing text on pages. This rule is mostly for spelling and grammar, rather than vocabulary.
Do
Don't

The color of my favorite difficulty is gray, because it looks centered and balanced, rather than something burned like maroon.

The colour of my favourite difficulty is grey, because it looks centred and balanced, rather than something burnt like maroon.

  • US Spelling: color, initialize, favorite, center, grey, burned

Remember spelling rules like -or, -er, -ize

  • English International: colour, initialise, favourite, centre, gray, burnt

Remember spelling rules like -our, -re, -ise

We understand using US English consistently may be difficult for some people, so don't worry this rule too much.

Notes
  • On some occasions, such as quoting text, it may be appropriate to prioritize the source's spelling.
Helpful tips
  • When in doubt, match the spelling already used on similar pages.
Don't use capital letters excessively
Content pagesMainspace articles and other content pages.
BlogsBlog posts.
Talk & commentsTalk pages, comments, and other discussion.
DocsProject, help, and documentation pages.
Required
You must follow this guideline.
Use text formatting for emphasis or clarity.
Do
Don't

Use text formatting for emphasis or clarity.

Use BIG LETTERS to EMPHASIZE text.

Sentence case. Bold and italics carry the stress.

All-caps is messier and harder to read than text formatting.

Don't use colloquial language
Content pagesMainspace articles and other content pages.
BlogsBlog posts.
Required
You must follow this guideline.
Don't use niche or colloquial language that the majority of readers would likely not understand.
Do
Don't

That is an Ibis bird.

That is a bin chicken.

Easily understandable for a global audience.

Readers outside the region where this nickname is popular might not understand it.

Maintain a neutral point of view
Content pagesMainspace articles and other content pages.
BlogsBlog posts.
Required
You must follow this guideline.
Don't put in your opinions and state facts in a plain setting without bias.
Do
Don't
  • Use third-person writing.
  • Avoid using opinions.
  • Use neutral and factual information, without cherry-picking it.
  • Use gender-neutral language.
  • Use judgemental or aggressive language.
  • State unverified or disputed claims as fact.
Don't use contractions on content pages
Content pagesMainspace articles and other content pages.
Highly recommended
You are encouraged to follow this guideline or edit any pages that don't.
While allowed on some documentation and help pages, actual content pages must not use contractions in order to maintain a professional (and neutral) tone.
Do
Don't

That does not work.

That doesn't work.

3.3 References

Back up facts that a reader might question with a source. A reference goes right after the claim it supports, using a <ref> tag, and every page collects them under its References heading.

Reference
Tower of Hell has been played over 20 billion times.<ref>"Tower of Hell". Roblox. Retrieved 2026-01-01.</ref>

== References ==
<references />
Renders as:

Tower of Hell has been played over 20 billion times.[1]

  1. "Tower of Hell". Roblox. Retrieved 2026-01-01.
Cite a source for facts that can be checked
Content pagesMainspace articles and other content pages.
BlogsBlog posts.
Highly recommended
You are encouraged to follow this guideline or edit any pages that don't.
Put a <ref>...</ref> right after the claim it supports, then let the References heading collect them. Prefer official or primary sources, such as the obby's game page or its creator.
Do
Don't
  • Cite visit counts, dates, and other numbers that change.
  • Cite claims that a reader might reasonably doubt.
  • Cite common knowledge or something already obvious from the page.
  • Bury the source in prose instead of a reference.
Helpful tips
  • Add the References heading with <references /> under it even when the page has no references yet.

4. Eligibility

Every new article must adhere to the Obby Wiki Eligibility Requirements, which you can read separately here.


Retrieved from "https://obby.wiki/index.php?title=Obby_Wiki:Style_guide&oldid=8528"