Vintage Story Wiki:Community noticeboard: Difference between revisions
(Added further wishlist items) |
|||
| Line 23: | Line 23: | ||
===== Update MediaWiki to at least 1.37+ ===== | ===== Update MediaWiki to at least 1.37+ ===== | ||
* While a handful of extensions get bundled with MediaWiki in future versions (''See here: [https://www.mediawiki.org/wiki/Bundled_extensions_and_skins Bundled extensions and skins]''), we're primarily interested in [https://www.mediawiki.org/wiki/Extension:VisualEditor VisualEditor]. | * While a handful of extensions get bundled with MediaWiki in future versions (''See here: [https://www.mediawiki.org/wiki/Bundled_extensions_and_skins Bundled extensions and skins]''), we're primarily interested in [https://www.mediawiki.org/wiki/Extension:VisualEditor VisualEditor]. | ||
* A noticeable amount of extensions that should be active on this wiki (current version: 1.34) are deactived/uninstalled. If possible, | * A noticeable amount of extensions that should be active on this wiki (current version: 1.34) are deactived/uninstalled. If possible, enabling all bundled extensions would be helpful, as certain ones like [https://www.mediawiki.org/wiki/Help:Cite Cite], or [https://www.mediawiki.org/wiki/Extension:InputBox InputBox] would be really handy to have available. | ||
* Assuming the above, any other bundled extensions that might interest us are not listed below. | |||
===== [https://www.mediawiki.org/wiki/Manual:Short_URL Short URL] ===== | ===== [https://www.mediawiki.org/wiki/Manual:Short_URL Short URL] ===== | ||
* It might be easier to put in place a short URL at the same time as updating MediaWiki so that the wiki's address becomes something closer to <code><nowiki>https://wiki.vintagestory.at/wiki/<page></nowiki></code>. | * It might be easier to put in place a short URL at the same time as updating MediaWiki so that the wiki's address becomes something closer to <code><nowiki>https://wiki.vintagestory.at/wiki/<page></nowiki></code>. | ||
| Line 29: | Line 30: | ||
* 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 creative teleporter 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. | ||
* This means we could attribute all relevant data to a specific item, block or entity, and only need to call its' table entry in order to retrieve that information, instead of having to manually write it every time. | * This means we could attribute all relevant data to a specific item, block or entity, and only need to call its' table entry in order to retrieve that information, instead of having to manually write it every time. | ||
* Tied with some potential logic extensions, this would help automate a lot of content as well. | * Tied with some potential logic extensions, this would help automate a lot of content as well. | ||
===== [https://www.mediawiki.org/wiki/Extension:Display_Title Remove Extension:Display Title] ===== | |||
* Causes redirected links to take on the name of the page they redirected to. Doesn't seem to provide any benefit to editors at all, other than give us headaches. | |||
===== [https://www.mediawiki.org/wiki/Extension:CSS Extension:CSS] ===== | |||
* Allows for unique, single-page CSS code that is only visible to that page. | |||
* This would be especially useful for larger templates, where certain CSS styles are defined multiple times, by allowing editors to reduce the amount of clutter without needing to have full CSS editing permissions. | |||
===== [https://www.mediawiki.org/wiki/Extension:Variables Extension:Variables] ===== | |||
* Introduces variables for use in templates to facilitate using information throughout the code. | |||
* Mostly similar to above, would allow us to store data in variables within a template so as to keep it consistent wherever the template needs it. | |||
===== [https://www.mediawiki.org/wiki/Extension:Loops Extension:Loops] ===== | |||
* Adds logic loops - self-explanatory. | |||
* Once again, would help reduce clutter in templates and allow for more dynamic templates. | |||
===== [https://www.mediawiki.org/wiki/Extension:TranslationNotifications Extension:TranslationNotifications] ===== | |||
* Allows translation administrators to send notifications to all registered translators when a page or group of pages are in need of translation. | |||
}}</div> | }}</div> | ||
Revision as of 02:26, 9 August 2022
{{{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:
- Category:Priority translation with accompanying
{{Priority translation}}, aliases pt and PT - Category:Stub
{{Stub}}(I recently went through this, that's why it's empty) - Category:Under construction
{{Under construction}}, alias WIP - Category:Outdated
{{Outdated}}
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)
I can see it being eventually useful, and probably good to have for the time being - but seeing as most translations are barely even started, it might not get much use for now? Sana (talk) 02:10, 9 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
trusteduseror 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)
