User:Dantman/ToDo


 * Customize Quartz Skins
 * Work on portlet stuff to make it work with tabs in Quartz.
 * Create a QuartzSwith system for use in Quartz. Use the gelButtons Background and most of it's system for the drop-down.
 * Detail how ACG Wiki would be used for Definitions and other content.
 * Detail the used of ACG Wiki for Index Pages. (Each Universe having information on what Anime/Manga/Cartoon/Comic/Other Media series it has)
 * Create ACG CSS for Skins with a Dark content area. This will be able to be included at the top of the Skin's css and will modify the colorings of the Box class to work well with the dark content area.
 * Communicate with Wikipedia WikiProjects about Wikia ACG.

MediaWiki Programming Tasks

 * Second Rewrite of GENetwork extension.
 * Build redirect systems:
 * DEEPREDIRECT: A DEEPREDIRECT works like a REDIRECT, you place it on an article and it redirects to another page. The difference is a DEEPREDIRECT also affects the nonexistant subpages of that page.
 * RegexRedrect: Using MediaWiki:Regexredirect regex replaces can be used to create redirects. These redirects only work for pages which don't exist, using an edit url, or a &redirect=no will also halt the redirect.
 * The GENetwork extension should extend this to also use Worldpage/Tech/Redirects to redirect in world.
 * CSS Class Search: The system generates a table filled with rows listing a css class the page it is used in, and how many times it's used. On parsing of the page (purge or save) the system regenerates this list. A simple php script also allows for a list of jobs to be added for every page in the wiki to regenerate the full list (Mostly for installation purposes). The extension's special page allows for multiple bits of information. By default it lists a list of all the css classes used on the wiki in alphabetical order with the number of times it is used beside it in brackets. Clicking on one of those class links lists what pages the class is used in and how many times it is used. The special page can also output a list of css classes used on an article and how many times each of them are used.
 * SpamRevDelete: A Special page usable by Sysops. It's meant for clearing out spam revisions from an article much easier. The Sysop goes to Special:SpamRevDelete/Pagename and is given a list of page revisions, both deleted and open. Lists the comment, a diff link if possible, a view link for the revision and a checkbox like the line on the Undelete page. They then select the revisions there that are spam, and when they submit all those checked revisions are moved to the page defined by MediaWiki:Deletedspampage and automatically set as deleted.

Wiki Tasks

 * Complete Licensebuilder system so it can be put out for public use on WGEP wiki.
 * Continue Infobox development for Wikia ACG.
 * Build UserBoxes.
 * Mega Man UserBoxes for MMKB.
 * Ghost in the Shell UserBoxes for GITS Wiki.
 * InuYasha UserBoxes possibly.
 * Possibly CardCaptor Sakura.
 * Add information in default help pages to Global Wikia ACG Help so that default help in new wiki which join Wikia ACG doesn't need to be worked on.
 * Upgrade Searchswitch.js:
 * Add Afker's fixes.
 * Remove use of Dropdown or List switcher
 * Add switch link to search header
 * Create Switchbox wrapper (Toggle on with link in Searchbox, close on X or select)
 * Look into combining the card similars/related/listing boxes on the Yu-Gi-Oh! Wiki into one special thing using DPL Sections.
 * Fix issues with Tabs.css
 * History tab looks odd when active (on history pages) due to the sizing. Tweak it to accommodate for the bold when active.
 * Perhaps Tabs.css should be loaded by one of the tab systems instead of by default.

Bot Tasks

 * Possible: Template space standardization bot... Setting up infobox types templates to have matching locations for the ='s is a bit tedious for repeat work when adding new infobox parameters which end up making all current developing boxes to have more whitespace added to them. Why not a bot which will correctly space those signs and correctly setup templates with null values when missing them to make standardization easier with new additions coming out.
 * Possible: RulesIndex generation bot... Much of Template:RulesIndex on WGEP wiki is the same. Why not a bot which uses a /Local subpage and combines that with a global stuff and a format to generate the RulesIndex by bot to simplify adding new Global Policies.
 * Forum Setup/Forum Conversion Script: The WGEP uses a different forum setup than the default forum setup. SITETITLE Discussion where SITETITLE is the commonly used name of the wiki is used instead of Watercooler, SITETITLE Announcements forum is also added and a few wiki also use SITETITLE Collaboration. Forum pages also use  instead of a hardcoded header, and have a   where the comment recommendation for a forum header is normally located. This template can also be autogenerated.
 * Message Bot: Things such as MediaWiki:Community and MediaWiki:Wgep are matching pages on all wiki in the WGEP, also pages like MediaWiki:Sidebar use similar formats. Once the Pywikipedibot framework stops having protected page issues it may be good to have a bot do the work of setting these up on new wiki to the WGEP, and also re-generating things like the Sidebar on all wiki in the project when things are done like a new top-level wiki being added to the WGEP section of the standard sidebar. ~Dantman(talk) tricks May 12, 2007 @ 07:46 (UTC)
 * Add new syntax to this bot:
 * @param: ... Can set parameters.
 * @DefaultBox: Off will turn off the normal bot's actions of using syntax to alter the base sidebar, and instead it will simply check for the location of a  line in the /gen code, and turn that into a WGEP section, if it is not there, then the code will ignore this tag and use normal syntax.
 * @Append: On will turn on append after... Basically instead of specifying the location of each box you can instead specify the location of one, then after that the boxes will be added after that one and after each other, till you either turn Append Off at a later line, or specify another existing box and end up adding after that one.
 * using **@name will move a item from it's location to the location the other item is at. (Think about syntax a bit more)
 * using *@name will similarly move the location of another box
 * Continue running bots for Yu-Gi-Oh! Wiki