Editing
Geometry Dash Expanded Wiki
:
Policy
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
The Geometry Dash Expanded Wiki enforces several policies governing behaviour and the use of site features, extending across all local namespaces. <tabber> Blocking= {{BlockingPolicy}} |-| Article creation= The nature of the Geometry Dash series in conjunction with its historic update schedule informs a precedent of two wildly differing frequencies between developer releases and community content additions. To better understand the Geometry Dash Expanded Wiki's article creation policy, it benefits to understand how wikis are typically organised. {{Togglebox |header = Geek mode lesson in wiki category structures |body = <nowiki /> A well-structured wiki helps viewers find and navigate to articles of similar subjects of likely interest by organising these articles into ''categories''. Every article on a wiki should be categorised.<br>After reading to the end of an article's page, present is its category module displaying links to category pages (which on the Geometry Dash Expanded Wiki displays just a single link). These are ''not'' tags/hashtags (the way which other wikis might incorrectly use them, implying that these links have been ''added to'' the article). Rather, a link in the category module shows that an article is ''included in'' that category. A category functions to group categorically-related articles (hence the name), convenient for a viewer to easily browse. Additionally, this organisation of articles then informs the sidebar's navigation links, and parts of the main page. }} The Geometry Dash Expanded Wiki recognises two classes of categories as follows. '''Class A: Base content''' - these categories include the wiki's primary articles, pertaining to base content of the Geometry Dash series whose subjects originate from the developer's contributions via historically infrequent game updates. Yet, these 'official' subjects remain of high interest to all players, particularly those new to the series. These categories are appended with '(base content)', highlighting their significance. *Base content articles are actively monitored and maintained by wiki staff, and in turn, they are upheld to a higher quality standard. Additionally, they are carefully organised into a most fitting category, and are directly linked on the main page's primary article site map. *It is at staff's discretion how subjects pertaining to base content are included on the wiki, for example, whether or not an article(s) is created for something new added in an update, or whether this is instead organised into an existing article(s). For staff reference regarding making updates to site structural listings of Class A categories and/or their articles, instances around the wiki include: *[[MediaWiki:Sidebar]] *[[MediaWiki:Common.js]] *[[MediaWiki:Gadgets/headerTags--base-content]] *[[Geometry Dash Expanded Wiki/nav--base-content]] *[[Meta:Community Portal]] '''Class B: Community content''' - these categories include the wiki's secondary articles, pertaining to significant user levels, prominent players, and in broad reference, various other community activities, events and phenomena. ''The scope of community-derived content relating to Geometry Dash is vast and of varying degrees of significance, relevance and interest to a wider audience.'' This underpins the article creation policy where it is most applicable to those who seek to create articles on the wiki. *A rated User level, having been officially recognised by the developer, will always be eligible for article creation. *An unrated User level may be eligible for article creation if it: **Is published, to recognisably wide public awareness, with some kind of standout significance which will maintain ongoing relevance over the long term, and the drafted article is developed comprehensively to high presentable standard, essentially 'complete'. **Was de-rated for any reason. *A deleted User level may be eligible for article creation if: **A surviving copy of the level is present in some form, whether through a re-upload or third party tools such as [https://history.geometrydash.eu/ GDHistory]. **It has garnered recognisabe public awareness, with some kind of standout significance which will maintain ongoing relevance over the long term, and the drafted article is developed comprehensively to high presentable standard, essentially 'complete'. *A [[:Category:Players|player]] - who might 'specialise' as an influential community figure, a popular content creator, a top-performing player, or a renowned level creator (but not an in-game moderator with no other credentials)—may be eligible for article creation if they: **Are widely recognised for their specialty, reflected by engagement of others, which can include a noteworthy number of social media followers across platforms, views and commenting on content created by them (including displays of that content produced by third-parties), and a noteworthy number of downloads of their levels. **Have been significantly and historically influential in the origination or propagation of a trend that is widely recognised as impacting the wider community culture, including in areas of level creation, as well as general content creation for video and social media, and the drafted article is developed to a majorly presentable standard. *An [[:Category:Community activities|activity, event, or group of people]] may be eligible for article creation if it: **Has been directed by, prominently participated in, or emphatically endorsed/promoted by the developer. **Has been a longstanding influential resource that is widely recognised as impacting the wider community culture. For staff reference regarding making updates to site structural listings of Class B categories and/or their articles, instances around the wiki include: *[[MediaWiki:Sidebar]] *[[MediaWiki:Gadgets/headerTags--community-content]] *[[Geometry Dash Expanded Wiki/nav--community-content]] ''The process of creating a new article benefits from formally [[Meta:Propose new articles|proposing it]].'' |-| Deletion= Staff may conduct page deletions suddenly and without warning. Pages may be marked for deletion by having [[Template:Delete]] included on them by editors. When reading the [https://geometrydash.wiki.gg/index.php?title=Special:Log&type=delete Deletion Log], the following reasons are likely mentioned: *'''Unnecessary/insignificant:''' A page either completely unrelated or partially related but of low significance and not requiring a full article. *'''Relocation/substitution:''' A page with content either being directly moved elsewhere or with similar information already so. *'''Vandalism/spam:''' A page created solely out of misconduct. *'''Redirect removal:''' Redirects are not used and are deleted where they occur. *'''Other reason:''' Any other reason a page is deleted at staff's discretion. Existing pages that are vandalised are not deleted, but rather, their edits are reverted to the last proper version. Staff need only make a single click to accomplish this, comparatively less effort than would-be vandalisers go to. ''If you believe that a page has been deleted without good reason, you may make an enquiry to a [[Meta:Staff|staff member]].'' |-| Protection= Staff have the ability to protect (lock) pages, preventing certain user groups from editing them. Page titles can also be protected, meaning that uncreated pages will not be able to be created under the protected title. Generally, protection is not favoured to be used, so to allow a broader aggregate of editors to contribute towards the wiki's development. However, there are various circumstances which prompt page protection. When reading the [https://geometrydash.wiki.gg/index.php?title=Special:Log&type=protect Protection Log], the following reasons are likely mentioned: *'''Complex page:''' Applied to pages containing complex code or technical information. *'''High traffic page:''' Applied to pages subject to frequent editing by many users who may inadvertently cause mismanagement and inconsistency. *'''Target of malicious edits:''' Applied to pages subject to frequent vandalism. *'''Resolved article:''' Applied to articles not only essentially wholly complete at a quality standard but also whose subject will not expand without in-game updates or developer commentary. *'''Heavily transcluded template:''' Applied to templates which experience widespread transclusion. *'''Other reason:''' Any other reason a page is protected at staff's discretion. There are three levels of protection: ''all users'', ''emailconfirmed'', and ''administrator''. Second-level protection prevents users without a registered email address from making an edit, while third-level protection prevents users without special user rights from making an edit. Note that even when a page is protected, edits can still be submitted for review. See ''[[Meta:Submit edits for review]]''. ''If you believe that a page has been protected without good reason, you may make an enquiry to a [[Meta:Staff|staff member]].'' |-| Files= Files include various types of media, organised under either [[:Category:Images]], [[:Category:Videos]], [[:Category:Audio]] or [[:Category:PDFs]]. All uploads made to the wiki are therefore expected to contribute towards article development. Uploads made for any other purpose (including use on user pages) will be deleted immediately. Note that replacing files with versions of lesser relevance or quality may be regarded as vandalism. When reading the [https://geometrydash.meta.gg/index.php?title=Special:Log&type=delete Deletion Log], the following reasons are likely mentioned: *'''Unused/insignificant:''' A file which is related but of low significance and lacking intended placement. *'''Duplicated/superseded:''' A file duplicated or of lower quality to another file which is effectively able to replace it. *'''Unrelated/inappropriate:''' A file either completely unrelated or one which constitutes unacceptable conduct. *'''False/unverified:''' A file implied to be official or relevant but is unable to be verified or determined to be false. *'''Corrupted/missing:''' A file that fails to function or display correctly. *'''Illegal/copyright violation:''' A file that contains decisively illegal material or violates a distinctive copyright. *'''Other reason:''' Any other reason a page is deleted at staff's discretion. ''If you believe that a file has been deleted without good reason or by mistake, you may make an enquiry to a [[Meta:Staff|staff member]].'' |-| Documentation of real-life individuals= The wiki includes articles in [[:Category:Players]]. It is important to recognise that players are real people, which prompts additional care being taken in documenting them as a subject on the wiki. Four factors are highlighted: *'''Accuracy of information:''' Player articles will be subject to heightened moderation to counter misinformation and disinformation, and to ensure accuracy of information, aided by citations. *'''Individuals' privacy:''' Personal identifying information that has not been publicly disclosed or confirmed by the individual, unless consent is provided privately, will be removed. Additionally, the offending page revision in question will be deleted to afford the affected individual further protection. *'''Slander/misrepresentation:''' Information—including that which is not explicitly misinformation/disinformation—that is deliberate targeting of an individual with function to smear their reputation, will be removed. *'''Subject relevance:''' Wiki documentation encompasses that which is related to Geometry Dash; the documentation of incidents or controversies that an individual might be embroiled in does not relate to actual engagement in Geometry Dash-related activities, and as such is not regarded as relevant (i.e., to the wiki's subject, nor its purpose in being a ''Geometry Dash'' resource) and will be removed. ''If you believe that an article is experiencing issues in relation to any of the above highlighted factors, please make an enquiry to a [[Meta:Staff|staff member]]. If you are a player who has a page written about them, please contact staff privately to confirm your identity. Note that being the subject of an article does not permit unfiltered control over how your page is run; this right is only waived in the event of controversies.'' |-| Manual of Style= {{WIP}} Namespaces designate the design and intention of page content. Each serves unique purposes, with specific structures and differing permissions. This Manual of Style explains these aspects to inform editors how to achieve a logical, high-quality interface that is consistent and understandable across the site. ===Articles=== Formally titled the ''(Main)'' namespace, articles are the primary medium that content relating to the wiki's subject is presented for viewers, and constitute where most normal editing occurs. ;Layout Except for articles in the Games and Updates categories, only specific h2 headings should be used, which may include the following, based on the article's subject: #Description #Levels #Gameplay #Secret coins #Trivia #Gallery ;General syntax *Canadian English should be applied. *Articles should be written in third person. *The 'player' should not be referenced when instructions are being provided on how to conduct a series of actions. *Dates should be ordered: ''date'', full-word ''month'', ''year''. There should be no commas between ''date'' and ''month'', and only one positioned after ''year''. Example: ''1 January 1990'' is correct formatting; ''January 1, 1990'', ''1st of January, 1990'', and ''1/1/90'' are examples of incorrect formatting. *No heading should be provided for the lead introduction section. *The first instance of an article's title should be formatted in bold only. *Game names do not require additional formatting, except being capitalised, and linked in their first instance. *Page titles should be linked once only. If the same page title appears further down the page, it should not be linked. Links appearing in infoboxes and tables are excluded from this count and may be repeated, including the same links within a table. If a tabber is being used to divide page content, the same links in different tabber sections may be repeated, granted that the links did not occur ''before'' the tabber. If they happened after the tabber, then they may be repeated only once. *Headings which use consecutive equals signs '=' should not be separated on either side from the contained phrase by a space. A line break should precede headings. All level headings should use a capital letter for the first word only, excluding proper nouns. Floated elements, including various thumbnails and infoboxes, should be positioned from the first line after a heading and before any text. *The asterisk '*' or hash '#' used for unordered and ordered lists, respectively, should not be separated with a space from their text, nor from each consecutive line by a line break. *Gallery captions should not end with a period '.', unless multiple sentences are included. *Tables composed of wikitext should begin and end with '{|' and '|}' respectively at the start of their lines. Cells which may use either of '|', '!', '|-' or '|+' should be separated by one space from the start of their lines. Style specifications for specific cells should be separated by spaces on either side from the initial pipe and the second pipe beginning the content input. Only <code>class="wikitable"</code> should be included within the first line of a table to enable design styling and formatting. The exception is if a table is contained within a tabber, where <code>style="width:100%;"</code> should be included after the class specification, and additional code is used before and after the table to adjust its margin to align with the edges of the tabber, as follows. <pre> _tabber> Table filling tabber body= <div style="margin:-1.5rem -1rem;"> {| class="wikitable" style="width:100%;" !Header !Header |- |Body |Body |} </div> _-| Table within tabber body with preceding text= Text before table. <div style="margin:0 -1rem -1.5rem;"> {| class="wikitable" style="width:100%;" !Header !Header |- |Body |Body |} </div> _/tabber> </pre> *Line break tags <code><nowiki><br></nowiki></code> and <code><nowiki><br clear="both"></nowiki></code>, which are self-closing, do not require the end slash '/' to be included. They should precede the immediately preceding content character, where needed. *Any HTML that is specifically needed should be condensed, with no spaces between characters unless the syntax requires it. *Avoid using comments <code><nowiki><!-- --></nowiki></code> as a permanent fixture except in irregular cases, such as where the common positioning of an element differs or where unusual code may be necessary and benefits editors from explanation. *Language links should be at the bottom of the article content, below categories, each on its own line, ordered alphabetically. ;Examples <pre><nowiki> '''Nocturne''' is the umpteenth level of [[Geometry Dash]] and the first level with a Psycho difficulty. It introduces ''Bob the Cube'' to the Geometry Dash universe. ==Main heading== [[File:FILENAME.png|thumb]] [[File:FILENAME.png|thumb]] Text. {| class="wikitable" |+Main heading |- !Header1 !Header2 |- |Cell | style="color:yellow;" |Formatted cell |} ===Subheading=== <div style="display:grid;grid-template-columns:1fr 1fr;gap:12px;"> <div> *Bulleted *Bulleted **Bulleted *Bulleted **Bulleted </div> <div> #Numbered #Numbered #Numbered </div> </nowiki></pre> ===Talk pages=== Talk pages are a traditional method of discussing page content on wikis. They may be cleared or deleted upon the resolution of any matters that are raised against them. Signatures may be used to quickly imprint a user's username, which should not include any files, template transclusions or tags. ===User pages=== User pages are a user's personal editing space, with no restrictions on subject, as long as site policy is complied with. Additionally, the following should be noted. *Using internal links is not permitted, as these are recorded in maintenance reports, so external links should be used instead, including to link to other pages on the wiki. *Templates that are not intended for use on user pages—such as those used on the main page—are not permitted. *Specific tags or other complex elements may be removed. *Prominent visual obstruction produced by overly creative page styling may be removed. Only staff members may edit the user pages of other users (typically to remove files, templates, and tags once the user is deemed inactive). Consent must be given by the owner for other users to edit the owner's user page. ====User page extensions==== User page extensions (sub-pages of the User namespace) are not encouraged as they are often found to be redundant and consequently may have any content relocated back to the respective user pages and then be deleted, but may be allowed upon request to staff on the condition that they are found to provide a distinct purpose, for example, storing a large amount of advanced code for relevant preservation or testing purposes that would otherwise significantly disrupt the flow of the requesting user's user page. Approved user page extensions will be reviewed after one month of inactivity to determine whether they are still necessary to maintain. ===Meta pages=== Meta pages designate site articles that pertain to wiki-related subjects but are not specific to Geometry Dash itself. They are usually editable only by staff. Where editing is permitted for non-staff, edits should align with the intended function of the page; otherwise, editors may incur penalties. ===Files=== Files are non-textual components of articles providing visual and auditory content. They should abide by the site policy. No content other than a category and, in some instances, a licence template should be present on any file page. '''Article syntax:''' All file names should be capitalised as is consistent with their titles. ====Images==== Images should be in the .png image file format, where possible, as this typically yields superior digital quality compared to other supported image file formats. Ideally, the resolution should be as high as possible, although this should be consistent among any one image series as determined by a common category. Images may be replaced in this regard, as the entire series is updated to maintain consistency. '''Article syntax:''' In all instances, captions should be used sparingly and not to state obvious visible details or context. 1) Inline image files should be thumbnailed, right-aligned (default for thumbnails, not requiring specification) and configured to 270px on their own lines, individual from one another. 2) Configuration can be ignored when they are used in galleries (although galleries should use the 'packed' mode) or 3) when used in infobox image fields. 4) Icon images used in vertical infobox fields should be configured to 35px but not thumbnailed. 5) Icon images used in tables should be configured to 24px but not thumbnailed. <pre><nowiki> 1. [[File:FILENAME.png|thumb|270px]] 2. <gallery mode="packed"> FILENAME.png </gallery> 3. |image = FILENAME.png 4. |FIELD = [[File:FILENAME.png|35px]] 5. |[[File:FILENAME.png|24px]] </nowiki></pre> Typically, galleries containing predominantly in-game screenshots should use the default setting with three images per row, while galleries containing icons/sprites should use eight images per row, enabled by including <code>class="icon-gallery"</code> within the gallery tag. ====Videos==== Videos can be displayed on the wiki either as uploaded files or directly from YouTube via the embedded media player, if the option is available. '''Article syntax:''' Embedded videos use a special parser function. However, [[Template:VC]] should instead be used in all instances *<code><nowiki>{{#ev:HOST|ID||center}}</nowiki></code> ====Audio==== Audio files include those in the .mp3 and .ogg file formats, the former typically used for music, and the latter typically used for sound effects. '''Article syntax:''' Audio files should be thumbnailed, right-aligned (default for thumbnails, not requiring specification) and configured to 270px on their own lines, individual from one another. Such a configuration is not required for positioning in tables or infoboxes. *<code><nowiki>[[File:FILENAME.ogg|thumb|270px]]</nowiki></code> *<code><nowiki>[[File:FILENAME.ogg]]</nowiki></code> ====PDFs==== PDFs complement articles with third-party information. They should be positioned under their own heading so that they are easily locatable. '''Article syntax:''' PDF file pages should be bypassed, and the documents themselves should be directly linked to using the 'Media:' prefix. The link should be bold and assigned a relevant title. *<code><nowiki>'''[[Media:FILENAME.pdf|Title]]'''</nowiki></code> ===MediaWiki=== MediaWiki pages are system pages that affect the design and functionality of the site. They are editable only by interface administrators. ===Templates=== Templates work by having content that exists on a template page being 'transcluded' onto another page, where it is then displayed identically as it is on that template source page. This feature serves either to prevent clutter by substituting a template for the addition of complex syntax on a page, or to allow frequently occurring content on multiple pages to be modified instantaneously from a centralised point. Information about producing documentation for template pages can be viewed on [[:Category:Templates]]. '''Article syntax:''' Template names should be capitalised as is consistent with their titles, but do not require prefixing. Parameters beginning with pipes '|' should be separated by one space from the start of their lines. Equals signs '=' should be separated on both sides by a space, unless more than two parameters are present, where all equals signs should be vertically aligned starting from the equals sign closest to the longest word on its left side, still separated by a space. *Notices should be included on their own line at the top of articles. *Infoboxes should be included on their own line at the top of articles, below any notices. <pre><nowiki> {{TEMPLATENAME |parameter1 = field1 |parameter2 = field2 |parameterXYZ = fieldXYZ }} </nowiki></pre> ===Categories=== The category system works by including pages within categories so that pages of a similar subject are organised together and can be navigated to through a [[Special:CategoryTree|tree]] structure. Note that categories are not ''tags'' and are not to be treated as broad characteristics that a viewer may consider a relevant search term. An article, project, file, template or category page should be included in only one category so that it can be reached in linear sequence from [[:Category:Geometry Dash Expanded Wiki]]. Temporary exceptions include the use of [[:Category:Article stubs]] for marking undeveloped articles and [[:Category:Candidates for deletion]] for marking unnecessary content through the related templates, which automatically include the aforementioned categories. Pages from all other namespaces should not be included within a category. Category pages of articles or files do not require any content to be included on them. Other category pages may consist of concise descriptions. New categories should only be created under the direction of staff. '''Article syntax:''' Categories should be included on their own line at the bottom of articles, not separated by a line break from the final line of content. Only template series that use letter prefixes in their titles should have a differentiating letter included as a parameter in the category link, which enables the page titles to have more intuitive alphabetic indexing on category pages. *<code><nowiki>[[Category:CATEGORYNAME|&]]</nowiki></code> </tabber> [[Category:Site articles]]
Summary:
Please note that all contributions to Geometry Dash Expanded Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Geometry Dash Expanded Wiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Pages included on this page:
Template:BlockingPolicy
(
edit
)
Template:Notice
(
view source
) (fully protected)
Template:Togglebox
(
edit
)
Template:WIP
(
edit
)
This page is a member of a hidden category:
Category:Pages using Tabber parser tag
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
associated-pages
Project page
Discussion
English
Views
Read
Edit source
View history
More
Search
Navigation
Main page
Recent changes
New files
Random page
New here? Get started
>> Site policy
>> Staff
Help using MediaWiki
GD Base Content
Games
Main levels
Gameplay
Rewards
Rooms (vaults etc.)
Level editing
Account features
Updates
GD Community Content
Demon List levels
Gauntlet levels
Map Pack levels
Classic levels
Platformer levels
Players
Community activities
Wiki Resources
Propose new articles
Submit edits for review
Admin Dashboard
Images
Videos
Audio
PDFs
Templates
Sandbox
Discuss the wiki
Guestbook
Tools
What links here
Related changes
Page information