简体中文
EnglishWebsite review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is wiki.gg Support Wiki?
The wiki.gg Support Wiki is the help and documentation site for wiki.gg, the wiki hosting platform. It is explicitly separate from any content wiki you might read or edit: it explains how the platform works and how to build, style and maintain a wiki on it, rather than covering a game or subject itself. Pages are open for anyone to edit, and there is a sandbox wiki at test.wiki.gg for experiments.
What it covers
The navigation is organized around tasks, which makes it useful as a reference rather than a linear tutorial:
- Getting started: creating a new wiki, creating an account, the redirect browser extension, and the indie.io connection.
- Editing articles: wikitext formatting, table markup, and templates such as DRUID infoboxes and RANGER navboxes.
- Styling: theming, CSS help, theme toggle, and the common.css and Vector.css pages.
- Adding functionality: available extensions, sample gadgets, ParserFunctions and string functions, Cargo for structured data, and DPL.
- Tools: AutoWikiBrowser and PyWikiBot for editing, plus Lookup User and Multiwikifinder for searching across wiki.gg.
- Policies and resources: AI policy, closing a wiki, customization and protection policies, licensing, and Python libraries such as mwclient, mwparserfromhell and mwcleric.
Who it is for
It suits three kinds of readers. A new editor who has just been given access to a wiki can follow the getting-started path and learn markup without breaking live pages. A wiki administrator deciding how to structure data will find the Cargo and DPL material more relevant than the formatting pages. Someone writing scripts or bots will gravitate to the API libraries and example Python code. The official Discord server is listed for community discussion when documentation does not answer a question.
How to use it
Start from the "I need help with..." menu and pick the task closest to what you are doing, rather than reading top to bottom. If you are about to change a live wiki's appearance or templates, rehearse on the sandbox wiki first. For MediaWiki concepts that are not specific to wiki.gg, the pages link out to mediawiki.org, which is the authoritative source for core software behavior.
A practical example: an editor asked to add a character infobox would read the DRUID infobox page, copy an existing template, test it on test.wiki.gg, then apply it. If the wiki later needs sortable data tables generated automatically, the Cargo documentation becomes the next stop.
How do I create a new wiki on wiki.gg?
The support wiki points editors to a "Creating a new wiki" page in its "Getting started with wiki.gg" section, which is the starting point for requesting a new wiki. The support site itself is documentation, not the request form, so the actual application process is described on that linked page rather than on the Support Wiki home page. See wiki.gg Support Wiki for the current instructions.
What to expect from the process
- A request step: new wikis are set up through wiki.gg rather than created instantly by any visitor, so you'll likely submit details about the topic and your plans.
- A separate content wiki: the support site notes it is "a different site from your content wiki," so your new wiki will live at its own address once approved.
- A sandbox for practice: if you only want to test editing, use the sandbox wiki at test.wiki.gg instead of starting a real one.
Before you apply
- Check whether a wiki for the topic already exists, using the search tools the support wiki lists (Lookup User, Multiwikifinder).
- Read the "Getting started (start here!)" and "Getting started editing my wiki" pages so you can describe how you'd structure articles, infoboxes and navigation.
- Review the official policies linked from the support wiki, including the AI policy and customization policy, since they affect how your wiki can be built and run.
A practical next step: open the "Creating a new wiki" page on wiki.gg Support Wiki and follow its linked form or contact route, then join the official Discord server mentioned there if you need help from other editors during setup.
How do I customize my wiki's theme with CSS?
The wiki.gg Support Wiki routes theme customization through its "Styling my wiki" section, which covers Theming, CSS help, the Theme Toggle, and the three CSS pages you'll edit: MediaWiki:Common.css, MediaWiki:Vector.css, and Special:MyPage/common.css. Treat that section as your starting point rather than guessing at selectors.
What each CSS page is for
MediaWiki:Common.css— site-wide styles applied across skins; the place for changes every reader should see.MediaWiki:Vector.css— styles scoped to the Vector skin, useful when you only want to adjust the default desktop look.Special:MyPage/common.css— your own personal stylesheet, visible only to you; the safe place to test rules before proposing them site-wide.
A practical workflow
- Draft and iterate in your personal
common.cssso a broken rule affects only your view. - Move proven rules into
MediaWiki:Common.css(orVector.cssif skin-specific) once you've checked them on article, category and talk pages. - Use the Theme Toggle to confirm your changes hold in both light and dark modes — a frequent failure point is hard-coded colors that vanish against a dark background.
- Check with other editors before broad changes, since site-wide CSS affects every reader.
Related pages worth knowing
- The support wiki's CSS help page for syntax guidance.
- Available extensions on wiki.gg and Some sample gadgets, if your styling goal is really about adding functionality.
- Customization policy under Official policies — read this before large-scale theme changes, as it sets expectations for what's acceptable.
If you're new to the platform entirely, the Getting started (start here!) page precedes the styling material. For MediaWiki CSS conventions in general, the upstream documentation at MediaWiki.org covers selector behavior and skin structure that the support wiki assumes you know.
Which extensions and gadgets are available on wiki.gg wikis?
The support wiki points to a dedicated page, "Available extensions on wiki.gg," plus a separate page of "Some sample gadgets." That is the authoritative list; the support wiki's front page only names those two entry points and does not enumerate the extensions itself. It also links to "ParserFunctions & String functions" and "Cargo documentation on wiki.gg," which tells you those two are part of the standard toolkit, and to "Theme Toggle" and CSS pages for presentation changes.
What the page structure implies for editors
- Functionality is curated, not open. Extensions are a fixed set chosen by the platform, so a feature you want may simply not be installable. Check the available-extensions page before planning a wiki design around a specific extension.
- Gadgets are opt-in extras. The "sample gadgets" page is a starting point for site-specific JavaScript/CSS tools; they are typically enabled per user in preferences or added by admins, so treat them as conveniences rather than guaranteed features.
- Data-heavy wikis lean on Cargo and parser functions. If you are building infoboxes, navboxes or query-driven tables, confirm Cargo's behavior on the wiki.gg documentation rather than assuming upstream MediaWiki defaults.
A practical next step
If you are scoping a new wiki, open the available-extensions page and list the three or four features your content depends on (for example, a data table, a map, or a video embed). Then compare that list against the sample gadgets page to see whether a gadget covers the gap. For anything involving templates, read the DRUID infoboxes and RANGER navboxes pages alongside the parser-function docs, since those combine extension behavior with local conventions. General wiki communities such as MediaWiki document the underlying extensions, but the wiki.gg list is what governs what you can actually enable.
For broader platform questions — account setup, theming, or bulk editing with AutoWikiBrowser and PyWikiBot — the support wiki's "I need help with..." sections are the better starting point than the extension list alone.
How can I use AutoWikiBrowser or PyWikiBot to edit my wiki?
AutoWikiBrowser (AWB) and PyWikiBot are both listed on the wiki.gg Support Wiki under "Using tools to edit my wiki," so the platform points editors to them for semi-automated and scripted editing. The key difference is how you drive them: AWB is a Windows desktop tool with a form-based interface, while PyWikiBot is a Python library you script yourself.
What each suits
- AutoWikiBrowser: a good fit for repetitive, rule-based cleanup on many pages at once — fixing a template parameter, normalizing categories, or applying a find-and-replace across a set of articles. It works through a list of pages you define, and you review changes as you go. This suits editors who prefer a GUI over writing code and who work on Windows.
- PyWikiBot: better when the task is conditional or data-driven — pulling values from Cargo tables, generating pages from a spreadsheet, or updating infoboxes based on external data. It requires Python familiarity but scales to jobs AWB's interface can't express. The Support Wiki also points to other Python libraries (mwclient, mwparserfromhell, mwcleric) for related work.
Practical next step
Before running either tool, confirm your account has the rights the task needs (for example, editing protected pages) and test on the sandbox wiki at test.wiki.gg rather than your live content wiki. Start with a small page list, check the diffs, then widen the run.
For background on the underlying API and bot frameworks, the official documentation at MediaWiki.org covers both AWB and PyWikiBot, and wiki.gg is the main platform site. If you get stuck, the Support Wiki notes an official Discord server for discussion with other editors.
Where can I get help or discuss issues with other wiki.gg users?
The two main places are the official wiki.gg Discord server and the support wiki's own help pages on wiki.gg Support Wiki. The Discord is where you talk with other editors and community members; the support wiki is where you read step-by-step guidance and then try things yourself.
Choose based on what you need
- A conversation or a second opinion: join the official Discord server linked from the support wiki. It is described there as the place for discussion with other members of the community, which suits questions like "is this infobox approach reasonable?" or "has anyone hit this template problem before?"
- A procedure to follow: start from the support wiki's "I need help with..." navigation. It is grouped by task, so you can go straight to getting started, creating a wiki, account setup, editing and formatting, styling and theming, extensions and gadgets, data formatting, or editing tools.
- Safe experimentation: the support wiki points to a separate sandbox wiki at test.wiki.gg for trying out wiki pages, and notes that the support wiki is a different site from your content wiki. Use the sandbox rather than testing on a live content wiki.
- Searching across wikis: its tools section covers Lookup, User and Multiwikifinder for finding content and users across wiki.gg.
A practical example
Suppose you are setting up an infobox on a new game wiki and the parameters render blank. Read the DRUID infoboxes and table markup pages on the support wiki first, then take the specific error to Discord and paste the wikitext. Other editors can spot a mismatched parameter name faster than you can work through documentation alone, and you keep the reference material for next time.
Decision criteria
Use the support wiki when the answer should be repeatable and written down; use Discord when the problem is situational, disputed, or depends on how others have solved it. For deeper technical background, the support wiki's external links point to MediaWiki documentation, which is the right place for core parser, template and extension behaviour rather than wiki.gg-specific setup. If you are writing scripts against the platform, the same resources list programming libraries such as mwclient and mwparserfromhell, with example Python code.
Cloudflare
Google Workspace
User reviews (0)