Vintage Story Wiki:Community noticeboard: Difference between revisions
No edit summary |
mNo edit summary |
||
Line 112: | Line 112: | ||
<!--T:21--> | <!--T:21--> | ||
I've been trying to figure out how this wiki works and what would be the best way to get something done, but I keep running into difference in code, confusion on how something should work, and running into half-finished systems (i.e. Grid/Crafting). A focus towards sweeping through old pages, even those that may not need to be changed, and standardizing a method of source editing will make it easier in the future to understand, find and edit pages. It will probably take a lot of work in the beginning, and may start to fall behind on new content updates, but by making everything standardized will potentially speed up learning and editing for other people, leading to less burnout and confusion. -- [[User:RathfulConcepts|RathfulConcepts]] ([[User_talk:RathfulConcepts|User talk]]) 14:35, 16 March 2023 (EST) | I've been trying to figure out how this wiki works and what would be the best way to get something done, but I keep running into difference in code, confusion on how something should work, and running into half-finished systems (i.e. Grid/Crafting). A focus towards sweeping through old pages, even those that may not need to be changed, and standardizing a method of source editing will make it easier in the future to understand, find and edit pages. It will probably take a lot of work in the beginning, and may start to fall behind on new content updates, but by making everything standardized, it will potentially speed up learning and editing for other people, leading to less burnout and confusion. -- [[User:RathfulConcepts|RathfulConcepts]] ([[User_talk:RathfulConcepts|User talk]]) 14:35, 16 March 2023 (EST) | ||
</translate> | </translate> | ||
{{Editing navbox}} | {{Editing navbox}} |
Revision as of 18:38, 16 March 2023
Community noticeboard | |
---|---|
This page serves as a central hub for discussion relating to the Vintage Story Wiki.
Wiki news The wiki is currently ondergoing a heavy overhaul, as a majority of the templates and guidelines were fairly outdated or lacking in information to give an easy onboarding experience for new editors. If stuff occasionally looks broken, do not fret, as we're doing our best to get everything adjusted to the changes! |
Wiki wishlist | |
---|---|
As the wiki is developer-run, we cannot spontaneously add new features or change the global styling on our own. As such, this wishlist has been put in place in order to request various extensions or changes that only Tyron can make.
Please do not add anything here unless the wiki community has first come to a consensus about requesting it. Update MediaWiki to at least 1.37+
Short URL
A favicon
Replace the creative teleporter block in the top-left with Vintage Story's logo insteadExtension:Cargo
Remove Extension:Display Title
Extension:CSS
Extension:Variables
Extension:Loops
Extension:TranslationNotifications
|
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 pages
{{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
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)
To add to this, I've looked through our current user groups, and I'm noticing a few of issues.
- For one,
Confirmedusers
andeditor
seem to both have the exact same rights, so getting rid of one would clean things up a bit. - Second, it looks like all users can translate pages as well as review them, which might not be preferable.
-- Sana (talk) 02:42, 9 August 2022 (UTC)
- Yeah, I'm with your first point completely (or one of those becomes the new "trusted" user group).
- With regards to translation rights, I'd be completely OK with setting up one of the "basic" categories to have both the
translate
andtranslate-messagereview
userrights, and putpagetranslation
andtranslate-manage
behind "trusted" users. This would mean it's relatively easy to get started with actually translating content into another language, and harder to mark up pages for translation (which carries obviously the risk of breaking the pages in question). As a historical note, I think the original rationale was to make it really easy to mark up any page for translation to get the ball rolling, but I think that was also before seeing the potential downsides of, eh, messily-tagged pages.
- Also, certain high-traffic pages should probably also get page protected, such as the Main Page. -- Veerserif (talk here or on Discord) 13:59, 10 August 2022 (UTC)
Reduce Code Chaos
I've been trying to figure out how this wiki works and what would be the best way to get something done, but I keep running into difference in code, confusion on how something should work, and running into half-finished systems (i.e. Grid/Crafting). A focus towards sweeping through old pages, even those that may not need to be changed, and standardizing a method of source editing will make it easier in the future to understand, find and edit pages. It will probably take a lot of work in the beginning, and may start to fall behind on new content updates, but by making everything standardized, it will potentially speed up learning and editing for other people, leading to less burnout and confusion. -- RathfulConcepts (User talk) 14:35, 16 March 2023 (EST)
Editing articles | |
---|---|
Hubs | Community noticeboard |
Guides | How to help • How to translate the wiki |
Styling | Style guide • Versions |