PvXwiki
Line 64: Line 64:
 
:I have no problems with it, and I doubt any remaining users will have serious objections so long as it looks good and relatively similar. I'll still be able to have custom lists for navigation links, correct? (as seen [[User:Toraen/monobook.js|here]]) -- [[User:Toraen|<span style="color:darkred; font:bold 100% Lucida Blackletter">Toraen</span>]] [[User talk:Toraen|<span style="color:darkred; font:80% Lucida Blackletter">confer</span>]] <small>01:23, 17 March 2013 (UTC)</small>
 
:I have no problems with it, and I doubt any remaining users will have serious objections so long as it looks good and relatively similar. I'll still be able to have custom lists for navigation links, correct? (as seen [[User:Toraen/monobook.js|here]]) -- [[User:Toraen|<span style="color:darkred; font:bold 100% Lucida Blackletter">Toraen</span>]] [[User talk:Toraen|<span style="color:darkred; font:80% Lucida Blackletter">confer</span>]] <small>01:23, 17 March 2013 (UTC)</small>
 
:I saw that Guildwiki copy pasta and am shocked and offended. Is it possible to preview the changes just to ensure that they don't break any of our extensions? In case you missed it, this wiki is more or less dormant now, so I can't imagine any resistance assuming it doesn't break anything. [[User:Misery|<font color="black">A new misery</font>]] 19:54, 17 March 2013 (UTC)
 
:I saw that Guildwiki copy pasta and am shocked and offended. Is it possible to preview the changes just to ensure that they don't break any of our extensions? In case you missed it, this wiki is more or less dormant now, so I can't imagine any resistance assuming it doesn't break anything. [[User:Misery|<font color="black">A new misery</font>]] 19:54, 17 March 2013 (UTC)
  +
::Given all the custom extensions, trust me that we are proceeding very slowly moving PvX to the platform, however, our team has already gone through all of the extensions used, and has everything working properly in the dev environment. That being said... are there going to be issues when it happens live?.... probably, but we will not stop until they are all fixed. This piece, the skin, is really the last piece of the puzzle before we can actually move forward with this migration. Your personal css should still be usable, you will simply have to move it to '''User:X/Vector.css''' and then again to '''User:X/Hydra.css''' once the migration happens. I plan to implement the Vector skin first, make sure any and all issues are resolved and THEN give the ok to migrate it to the new platform. --<small> [[User:Wynthyst|Wynthyst]] [[Image:User Wynthyst sig icon.png|19px ]] [[User talk:Wynthyst|<span style="color:black">''talk''</span>]]</small> 07:26, 18 March 2013 (UTC)

Revision as of 07:26, 18 March 2013

Looking for a way to improve the wiki? See the Improvement drive!

Welcome to PvXwiki

This page is intended as a task list to keep our efforts in the wiki coordinated and help highlight specific issues that need attendance. Additionally, this page's discussion page is used for discussions that affect the wiki in general.

Reporting Bugs

General Bugs

If you spot a problem with the wiki in general, please report it here.

PvXcode

PvXCode was implemented in order to improve the general layout of the attribute and skill bar as well as facilitate build articles. Any flaws or errors discovered in PvXcode should be added to the talk page at PvXwiki:PvXcode

Inter-Wiki Links

Because this Wiki does not house Skill information, Armor information, etc. it is necessary to link to the official Guild Wars Wiki or to GuildWiki.

The correct way to make such links are [[gww:Frenzy|Frenzy]] (displayed as Frenzy) and [[gw:Frenzy|Frenzy]] (Frenzy), respectively.

If at any point you see a build containing links that should link to either of these wikis but do not, please correct them. As well, in order to make this Wiki as professional as possible, it is also important to edit links which display with a | before the link name. This often results when people believe that inter-wiki links require a second |. For example, [[gww:Frenzy||Frenzy]] will display as |Frenzy. In order to fix the issue simply remove the extra |.

Updating "Help:" Pages

Pages such as Help:Contents, PvXwiki:About, and others, require a good deal of work before they are in working order.

Special Pages

Keeping an eye on various Special Pages is a great help to this Wiki. Anything ranging from clearing/creating categories, adding deletion tags to redirects, or keeping an eye on Recent Changes. Your vigilance is appreciated.

Perennial Tasks

Policies

Please look at PvXwiki:Policy for suggested guidelines for proposing and changing policies, a more centralized way of tracking what is currently up for discussion, and a more up-to-date listing of PvX policy.

At this point in time, we have adopted a multitude of GuildWiki policies, therefore, it also becomes necessary to review such policies in order to ensure that they can be correctly applied to this Wiki.

Projects

Major projects which require coordinated effort by Wiki users can be found at PvXwiki:Projects.

Uncategorized Builds

The special page Special:Uncategorizedpages was modified to list also uncategorized pages in the Build: name space. You can help cleaning up by putting the proper category tags on these pages.

Expired Grace Periods

Builds that have been in trash or abandoned for two weeks should be deleted. Before deleting it, please check the talk and rating pages to see if the build deserves a reset of the grace period, being moved to another category, or if someone would like to keep it in his user space.

Also, pages in Category:Build stubs or Category:Trial Builds should be tagged with Template:Abandoned if there have been no significant edits to the build or its talk page for over two weeks.

Altered Builds

Builds that are in Category:Builds that need updating have been affected by game changes, and may require retesting, revoting, or archiving. You can clean up this section by creating discussion on the builds' talk pages to help update them.

IRC

Anyone can join the discussion at #pvx on Gamesurge. If you don't have an IRC client, you can use GameSurge's Java applet.

Some possible IRC clients available for use are Chatzilla and mIRC.

This is an unofficial irc channel for casual discussion. Anything typed into the irc channel are not covered under wiki policy.

Moving forward

Curse is moving full steam ahead now that our Gamepedia platform has been launched and is stable. We have begun the process of migrating our existing wikis to it. In order to successfully migrate GuildPvXwiki, we need to convert it to the Vector skin. This is required. There is no option for retaining monobook on the Gamepedia platform. Since you have retained a mostly default monobook look, this should not be very difficult, I can move the background image and minimize the visible changes relatively easily. Comments? -- Wynthyst User Wynthyst sig icon talk 17:28, 16 March 2013 (UTC)

I have no problems with it, and I doubt any remaining users will have serious objections so long as it looks good and relatively similar. I'll still be able to have custom lists for navigation links, correct? (as seen here) -- Toraen confer 01:23, 17 March 2013 (UTC)
I saw that Guildwiki copy pasta and am shocked and offended. Is it possible to preview the changes just to ensure that they don't break any of our extensions? In case you missed it, this wiki is more or less dormant now, so I can't imagine any resistance assuming it doesn't break anything. A new misery 19:54, 17 March 2013 (UTC)
Given all the custom extensions, trust me that we are proceeding very slowly moving PvX to the platform, however, our team has already gone through all of the extensions used, and has everything working properly in the dev environment. That being said... are there going to be issues when it happens live?.... probably, but we will not stop until they are all fixed. This piece, the skin, is really the last piece of the puzzle before we can actually move forward with this migration. Your personal css should still be usable, you will simply have to move it to User:X/Vector.css and then again to User:X/Hydra.css once the migration happens. I plan to implement the Vector skin first, make sure any and all issues are resolved and THEN give the ok to migrate it to the new platform. -- Wynthyst User Wynthyst sig icon talk 07:26, 18 March 2013 (UTC)