User:FlyingRagnar/TODO: Difference between revisions

From Dragon Quest Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(19 intermediate revisions by the same user not shown)
Line 1: Line 1:
====Configuration====
==Dragon Quest Wiki==
VersionTabs template needs updated to not use jQuery anymore.  Probably can use flexbox CSS instead like on the Final Fantasy Wiki.


====Templates====
Tabs are too much work to support in MediaWiki.  Easier to just use the collapsible jQuery stuff that is now included by default.  Templates that have tables should probably all use that.  One "featured" version of the template could be marked as un-collapsed on Desktop.  On Mobile, they could all be collapsed by default?


====Extensions to consider installing====
Table width on desktop can be anywhere between 50%-75%. On Mobile they should all be 100% since there is not much space.
* [http://www.mediawiki.org/wiki/Extension:MultiUpload MultipleUpload]


====Other====
The site could use some work on looking better on mobile. Mobile traffic is currently 65% of all traffic and will likely increase even more.
* Recipe Search
 
** Read formulas
 
** Store as a HashMap of String arrays
===Bot===
** Do string cascading search
* Move [[:Category:Dragon Warrior III]] into [[:Category:Dragon Quest III]]
* Write script to grab alchemy recipe book locations and parse into a table.
 
* Write script to count number of book recipes for comparison against total number of recipes.
==NIWA==
* Adjust the bot program to be able to easily connect and make mass changes as programmed.  This will be useful for the list of alchemy recipes by x. 
 
* Make a table of party tricks for the [[List of party tricks in Dragon Quest IX|list page]].  Maybe parse this as well?
==SEIWA==

Latest revision as of 04:06, 29 May 2020

Dragon Quest Wiki[edit]

VersionTabs template needs updated to not use jQuery anymore. Probably can use flexbox CSS instead like on the Final Fantasy Wiki.

Tabs are too much work to support in MediaWiki. Easier to just use the collapsible jQuery stuff that is now included by default. Templates that have tables should probably all use that. One "featured" version of the template could be marked as un-collapsed on Desktop. On Mobile, they could all be collapsed by default?

Table width on desktop can be anywhere between 50%-75%. On Mobile they should all be 100% since there is not much space.

The site could use some work on looking better on mobile. Mobile traffic is currently 65% of all traffic and will likely increase even more.


Bot[edit]

NIWA[edit]

SEIWA[edit]