Guide:Wiki Maintenance: Difference between revisions

From Step Mods | Change The Game
mNo edit summary
mNo edit summary
Line 40: Line 40:
</p>
</p>
</syntaxhighlight>
</syntaxhighlight>
<p class="mpcode"><syntaxhighlight lang="HTML"><p class="mpcode">My mult-iline
code
snippet
</p></syntaxhighlight>
</p>


== User Namespace ==
== User Namespace ==

Revision as of 14:12, July 1, 2021

Delta c.png

Step Wiki User Guide

Standards and tips for editing the Step wiki

by: Step Modifications  | Forum Topic

Definition of a wiki:

"...a website or database developed collaboratively that allows users to add, delete, or revise content by using a web browser."

The Step Modifications wiki is intended to be a community-driven project; although, most contributions to date have originated from only a handful of contributors. Our goal is to make it easy for all community members to contribute by helping us maintain existing content and developing new content. We created this reference to help our userbase get more comfortable working within a wiki environment.

Step Wiki Maintenance[edit | edit source]


[edit]
  • The search bar is located at the right side of the navigation bar and can be useful for finding pages.
  • From the navigation bar at top, click on [Navigation] and click [Recent Changes]. This gives a list of the most recent edits on the Wiki. This is often the most convenient way to find a project of interest (and to see who may be fiddling around).
  • Editing and other general preferences can be set by user ... click on the icon in the navigation bar and click [Preferences].
[edit]
  • To style text, DO NOT use inline styling like:
    <span style="color: #ff0"></span>
    
    Instead use Bootstrap and custom CSS classes (see the site color pallet for the available classes):
    <span class="orangetx"></span>
    
  • Please don't use header tags ( <h2></h2> ) to make text bigger or bolder.
    • Instead use wiki markup and/or the Fs template. Header tags are for...headers.
  • When editing a page, remember to fill in the summary box below the editor with what changes that were made before saving. This summary will be logged on the Recent Changes page and helps everyone to know what exactly was added/changed with a given edit.
  • Discussions of major changes to content should occur on the page's 'Discussion' forum (if linked) or 'Talk' page. It's also appropriate to contact the page's creator/editor and/or a staff member and point them to the discussion when proposing content or stylistic changes.
    • Simple corrections to grammar do not require any special notification or mentions on the forum or Talk page.
[edit]

Edits to mod pages default to the Page Forms editor, but the wiki editor can also be accessed under the ellipse to the right of the edit asterisk on mod pages. The wiki editor should only be used by those who understand the format expected by Template:Mod.

Info-Logo.png

NOTE

Mod page 'Recommendations' are transcluded into ModGroup tables of mod-build guides, so special conventions apply to markup and HTML syntax used on these pages.

When adding/editing Mod Recommendations ...

  • Keep it basic and limit ALL markup code to only what is necessary.
  • DO NOT use wiki or HTML headings, as they will contribute to guide ToC, which is horrific. Instead use:
    <div class="mpheading">headingText</div>
    
  • DO NOT use Template calls other than Template:Fomod. They contribute drastically to the wiki transclusion limit of guide pages.
  • DO NOT use <pre> tags to show multi-line code examples. Wiki and PHP do not play nicely together when transcuding this syntax, resulting in an error on the guide. Instead use:
<p class="mpcode">My mult-iline
code
snippet
</p>

User Namespace[edit | edit source]

The simplest way to get started on the Wiki is to begin by playing around under the User namespace: ../wiki/User:Username

This is the user's "main page" or "entry-way" into the user's personal sandbox. Each user can do just about anything they want within their User namespace, as long as it's in accordance with the guidelines dictated within the Community Citizenship Guide. Users are asked to...

...avoid editing another user's page without permission (not applicable to wiki administrators), doing so is a breach of etiquette.
...at least edit the page adding some information about themselves for others ... even a link to another website or their forum profile is a good start.

Special Pages[edit | edit source]

Coming soon...

[edit]

General Management[edit | edit source]

How to create, delete, edit and manage a wiki page...

A wiki is simply an integrated assemblage of pages containing information, which usually link to other wiki pages. Every internal wiki link points to another wiki page. If the link is blue, the page exists. If it's orange, the page is referenced, but has not been created. Feel free to click on orange links and create their corresponding pages by adding something relevant and saving.

  • Wanted Pages is a special page that houses a list of links that have been created within content, however, the linked pages not not exist.

Create a Page[edit | edit source]

If one has never used a wiki before, creating a new page is not immediately intuitive; however, it's very simple once the method is known. Regardless where on the Wiki a new page is being created, the method is the same. Since User namespaces were just discussed, the example below will show how to create a page in a User namespace:

  1. Log into the Wiki, if not already.
  2. In the URL type https://stepmodifications.org/wiki/<namespace>:<pagename>/<subpagename>
    Example: https://stepmodifications.org/wiki/User:TheCompiler
    • The <namespace> field is replaced by the namespace in which the content belongs to. Note that it's always followed by a colon ( : ).
      For the User namespace, this would be: User:
    • The <pagename> field is replaced by the name of the page being created.
      For the User namespace, this would be username that matches the login.
    • The <subpagename> field is replaced by the name of the subpage being created. This is optional and is only show as an example.
      For the User namespace, this would be: User:TheCompiler/Sandbox
  3. Hit Enter to load the page.
  4. To create the page, either click the "create this page" link in the displayed text or click the icon on the navigation bar.
    • To save, there must be content in the editor box.
    • Some writers have found that typing "Hi" or == Introduction == is good enough to get the page started.

Categories[edit | edit source]

Categories are used to topically associate wiki pages. They also provide a simple means to navigate and view associated pages. Simply scroll to the bottom of any page and follow the category links to view more pages within that same category. Assigning a page to a category is as simple as adding [[Category:<CatName>]] when editing the page. Categories can be referenced on a page without adding that page to the referenced category by adding a colon to the beginning of the code as such: [[:Category:<CatName>]]. Users are asked to:

  • Read about how to use categories.
  • Assign pages to the proper existing categories.
  • Avoid creating new categories --leave that to the site admin. Just let one of the administrators know.
  • Place the category code at the TOP of the page for consistency and to make it easy for other users to find.

PageTitle Template[edit | edit source]

The PageTitle template is used to create a standardize title at the top of a page. It's recommended to be placed at the top of all non-guide pages. This creates a consistent look across the Wiki. It can be seen used for all officially curated content (such as this Guide). This template should be placed at the top of the page, directly after any listed categories.

Table of Contents[edit | edit source]

Most lengthier pages should include a table of contents (TOC). Step has provided a couple of templates to add with this while providing a style that is suitable for the Wiki themes. To include a TOC use one of the following templates:

  • TOC left | places TOC, floated to left side of page
  • TOC right (preferred version) | places TOC, floated to right side of page

The TOC templates will appear on the pages at the position the template is placed. Therefore, it's possible to have elements (such as an Alert) above the TOC. In general, this template should be placed directly after the PageTitle template or categories.

Edit/Delete/Move/Rename[edit | edit source]

Edit a Page[edit | edit source]

Editing an existing page easy. Simply navigate to the page and click the button on the wiki navigation bar.

It's expected that any information added to the wiki is clearly cited, where applicable, as many users do not appreciate unverifiable speculation, unless it is plainly stated as such. That is to say, feel free to write what might or might not be factual, but qualify what is intended to be factual with verifiable information by posting a link where appropriate. However, we want to facilitate community contributions to the wiki, so we encourage all users to get involved. The Cite extension is available on this wiki and makes adding inline citations and references easy.

  • More to come ...

Delete a Page[edit | edit source]

From time to time maintenance warrants the removal of pages, however, this shouldn't be a routine task. Users should be aware deleted content is not actually "deleted", but rather "archived". Thus, deleted pages can be restored. Pages are only truly deleted when old archives are purged during maintenance (performed a couple times a year...maybe). To delete pages:

  1. Click on the icon on the navigation bar.
  2. Click [Delete]
  3. One the page that loads, select a reason for deletion.
  4. Enter additional information, if applicable.
  5. Click the [Delete page] button.

Move/Rename a Page[edit | edit source]

Moving and renaming a page is the same process. This is because you can only rename a page by moving. Whenever pages are moved, a redirect should always be created. The redirect allows any links linking to the old page to be redirected to the new page, seamlessly. To move/rename a page:

  1. Click on the icon on the navigation bar.
  2. Click [Move]
  3. On the form under New title, select the namespace from the dropdown box (this typically matches the original namespace).
  4. Under that within the input box, type the page name of the page.
    This box is where users can rename the content, if desired. Either type the same page name or provide a new one.
  5. Within the input box under Reason, provide a short explanation why the page is being moved.
  6. Ensure the boxes are ticked for Move associated talk page and Leave a redirect behind.
  7. Click the [Move page] button.

Using Forms[edit | edit source]

Placeholder.

[edit]

General Formatting Tips[edit | edit source]

This will hold the do's, don'ts and good habits with formatting but be focused on where to look for the info.
Like the cheat-sheet...

Writing Style[edit | edit source]

When writing content outside of the userspace, the third-person writing style should be used. Other writing styles are acceptable, depending upon the particular context of the article; however, any factual content created to serve as an informative article (e.g., guides and references) should be written in the third person. This is more clear and professional and not as prone to degenerating into a mess of first-second person reversions. Any content that exist outside userspaces and is also not written in the third person should be corrected accordingly. Examples:

  • First person: "I first must click on the 'edit' button ..."
  • Second person: "You first must click on the 'edit' button ..."
  • Third person: "First, click on the 'edit' button ..."

Magic Words[edit | edit source]

Magic words are special 'text strings' that are used by the wiki software to return values or functions. A full description of them can be found on the MediaWiki website.

Common Magic Words[edit | edit source]

__NOTOC__ Hides the table of contents (TOC).
{{FULLPAGENAME}} Prints the Namespace and full page Title (including all subpage levels).
Result: Guide:DDSopt/DDSopt_INI
{{NAMESPACE}} Prints the Namespace.
Result: Guide
{{PAGENAME}} Prints the full page Title (including all subpage levels) without the namespace.
Result: DDSopt/DDSopt_INI
{{SUBPAGENAME}} Prints the subpage Title of the current page. If not a subpage, defaults to {{PAGENAME}} behavior.
Result: DDSopt_INI

Instruction Sets[edit | edit source]

Follow these guidelines when writing instructions:

  • When instructing a user to 'click' or 'select' any UI element: use the Ui template, as in the following example:
    • Click {{ui|Edit}}, then right click {{ui|some UI element}} ...
    • Click [Edit], then right click [some UI element] ...
  • When referring to messages in the UI: Italicize the UI message, and do not highlight it in any other way.
  • In-line headings: If you have several bullets or paragraphs in a row which each refer to a certain topic, you may use bold, peach-colored formatting to highlight the topic of each bullet or paragraph, as in the following example:
    • {{fc|important|'''First Topic Name.'''}} This paragraph explains the first topic. Other paragraphs will have their own in-line headers and explanations.
    • First Topic Name. This paragraph explains the first topic. Other paragraphs will have their own in-line headers and explanations.
    • Working Example

Symbols[edit | edit source]

Basic symbols can be displayed by inserting its hex code into the text. Users can search for symbols and use its hex code to produce the symbol on the page,

like so: →

Font Awesome[edit | edit source]

The Wiki supports Font Awesome and users can insert any of the free icons from this awesome source directly into the wiki page,

like so: 

Text Size & Coloring[edit | edit source]

For readability and consistency, use the Fc to modify font color and/or Fs to modify font size. These work well with the wiki themes.

[edit]

Inline Styling[edit | edit source]

Custom, inline styling using HTML and CSS is not recommended, but not restricted either. Users should keep in mind that the Wiki uses themes. Step has taken great care to ensure the styling on the Wiki is clean, consistent across all themes, and up-to-date with modern standards. This is seen in the responsive design of the wiki, so users can enjoy the Wiki wherever they are and on whatever device they may have. This also creates a consistent look across the Wiki, regardless of theme used. The use of inline styling can easily break Step's intended design, therefore, users are asked to limit using it to a last resort option. If any user finds they are consistently using inline styling for a specific reason, we ask that they contact a member of staff (see bottom of the page) to inquire about changes being made globally.

HTML[edit | edit source]

Inline HTML is perfectly fine to use. Users should keep in mind that HTML is restricted and parsed by the Wiki. This means the Wiki will automatically remove HTML that is not found on their permitted list. It's always preferable to use wiki markup.

CSS[edit | edit source]

As mentioned, inline styling is available, but should be used as a last resort. With that said, if customization is necessary, the Wiki is mostly compatible with Bootstrap 4. Users should use Bootstrap's list of classes as a first reference for any necessary inline styling deviation before moving on to completely custom edits.

HeaderTabs[edit | edit source]

Use of HeaderTabs should be limited and the majority of content should use the TOC method. HeaderTabs are still great for some applicable content, however, they should be used sparingly. An example of HeaderTabs is use on this page to display the content within these tabbed sections.

Tables[edit | edit source]

Wiki tables are flexible enough to provide simple data sets or complex data sheets. Once their format is understood, tables should only be used for displaying data. When creating structural code on custom pages, HTML is preferred. For a complete table reference, see the MediaWiki documentation.

  • The standard "wikitable" class has been customized to work with our site and is preferred.
  • Users can utilize Bootstrap's classes to help with custom formatting, as needed.
[edit]

Templates Explained[edit | edit source]

Templates are standard wiki pages whose content is designed to be transcluded (embedded) inside other pages. Step utilizes templates for creating standardized elements (alert boxes, galleries, side boxes, spoilers, table of contents, etc.), which are used across the wiki for all content. Templates are also used for creating some of our framework and guide structure. Since they are essential for our guides and basic website elements, templates have restricted editing rights; only certain staff groups can edit these pages. However, all users can utilize the templates for their content and are encouraged to do so where appropriate.

Templates can be found from the navigation "Tools" menu by clicking: Special Pages scroll down to Page Forms heading Templates

Common Templates[edit | edit source]

Some of the more common Templates that are used on the STEP wiki are:

  • Alert | creates a large, centered alert box
  • Alert Small | creates a small, inline alert element
  • Clear | used to clear floating elements
  • FC | used to change font color to a pre-defined color (colors work with themes)
  • FOMOD | creates a graphical representation of FOMOD instructions
  • FS | changes the font size. Accepts any valid CSS.
  • Icon | places a small icon for specific uses
  • Quotation | creates a stylized blockquote
  • Sidebox | creates a stylized box to the side of the content
  • Spoiler | creates an element with hidden content that reveals when a title is clicked
  • TOC right | floats a Table of Contents to the right of the page
  • Video | embeds a YouTube video on the page
[edit]

Moderated Content Overview[edit | edit source]

The Wiki has many pages of content that are considered "Moderated Content". This simply means they are either watched more closely than other or restricted via user groups. Below are the different types of Moderated Content user will find on the Wiki.

Namespaces[edit | edit source]

There are several namespaces on the Wiki that are restricted to specific user groups. These include:

  • Project
  • STEP
  • Template

Guides[edit | edit source]

The Wiki is home to many guides that are considered official Step content. Such guides are considered "Moderated Content". Since they should all have the same general look and feel, Step exerts a level of control over this content. Any major changes to these guides should be posted to their topics on the Forums.

Following are some basic standards for guides...

Guide Standard Header[edit | edit source]

Use the PageTitle template.

[edit]

Wiki Resources

Mediawiki[edit | edit source]

Home Page - Entry point to lots of relevant info, including reference and help as well as latest development and news
Help - MediaWiki's Help directory
Cheat Sheet - List of the most commonly used mediawiki markup
Tables - Wikitext syntax for tables
Magic Words - Behavior switches and variables
Parser Functions - Functions meant to provide more advanced logic

Semantic Mediawiki[edit | edit source]

Semantic Mediawiki - Documentation about Semantic MediaWiki ()see lower portion of middle frame).
Semantic Forms - Documentation about Semantic Forms, which provide a form-based interface for maintaining relevant SMW pages and content.
Semantic Forms Inputs - An extension for Semantic Forms

The Step Modifications Wiki[edit | edit source]

(top bar) TOOLBOX > SPECIAL PAGES - Links to all kinds of information about The Wiki.
(top bar) WIKI > RECENT CHANGES - Links to all of the most recent edits on The Wiki.
Software used on this wiki - Software and versions with links to documentation.

HTML and CSS Resources[edit | edit source]

CSS Resource - Not all info on this page is relevant but it contains various keywords that can be used
HTML Resource - Not all info on this page is relevant but it contains various keywords that can be used

Need Help?[edit | edit source]

Private message one of these guys if you need some sort of help with The Wiki.

Primary Wiki Editors/Maintainers[edit | edit source]

Always looking for others!

Recently active wiki editors[edit | edit source]