Vintage Story Wiki:Community noticeboard: Difference between revisions

From Vintage Story Wiki
No edit summary
m (Replaced the carpet (?) with the creative teleporter)
Line 28: Line 28:
===== A favicon =====
===== A favicon =====
* Currently the wiki has no icon, and while minor, it would be nice to have regardless.
* Currently the wiki has no icon, and while minor, it would be nice to have regardless.
===== Replace the carpet (?) block in the top-left with Vintage Story's logo instead =====
===== Replace the creative teleporter block in the top-left with Vintage Story's logo instead =====
===== [https://www.mediawiki.org/wiki/Extension:Cargo Extension: Cargo] =====
===== [https://www.mediawiki.org/wiki/Extension:Cargo Extension: Cargo] =====
* Cargo would allow us to set up sub-databases on the wiki, which in turn lets us create data tables for any game object.
* Cargo would allow us to set up sub-databases on the wiki, which in turn lets us create data tables for any game object.

Revision as of 18:55, 8 August 2022

{{{ingredients}}}

{{{ingredients}}}

Requests

If you'd like to request and/or put forward a suggestion for anything in the wiki, feel free to edit it in below.

Work queues

We have a couple of rudimentary ones:

However, I'd love to see/make/maintain another one for specifically updating translation tags, since translation is both one of the easiest ways to get started, but the easiest to "mess up" and overwrite (plus there are many pages in English that are updated for the latest version of VS, but have not been re-marked for translation, meaning their translated pages may be months or years out of date).

Anyone got more? -- Veerserif (talk here or on Discord) 16:12, 8 August 2022 (UTC)

Extension wishlist

If we are going to keep using the Translate extension, maybe getting Extension:TranslationNotifications will help us retain volunteer translators? -- Veerserif (talk here or on Discord) 16:59, 8 August 2022 (UTC)

New permissions hierarchy

Right now, anyone with edit permissions has a lot of edit permissions, including default access to the Template namespace, translation administration etc. I would like to ask for:

  • A second "tier" of user, maybe trusteduser or something like that, granted on request via Discord or similar
  • Page protection on the whole Template namespace (and maybe even translation administration, though that would significantly slow the work of translation markup), requiring a "trusted user" userright to edit

Although we haven't really had issues with vandalism, I have definitely seen issues arising from enthusiastic application of translation tags breaking templates - see the version history of {{Breaking}} for one example. -- Veerserif (talk here or on Discord) 16:59, 8 August 2022 (UTC)