User:RinasaurusRex/Sandbox

todo: Go through screencaps for files that are out of date. We've got some from, like... a couple layout changes ago. Also maybe institute policy that screencaps should be taken with the default skin? Looks messy to have caps from a bunch of different skins...

todo: add hidden cats for stripe colors to automate stripe breeding lists

todo: Standardize how we cite forum posts. Maybe make a template for it. Just a plain forum url is aesthetically unpleasant and also not super helpful unless you route through to see what the actual post is. maybe standard text like "Forum from ${PERSON} on thread ${TITLE}. ${LINK}"

todo: Make sure all event articles have redirects from "[EVENT NAME] [YEAR]" to the article (eg, "Halloween 2015" => "Brewing Mischief").

todo: create main article for Dragon Cave Birthdays so we can empty out these very long category pages...

File naming conventions
after category naming convention is fully implemented, we might consider updating the file naming convention.

We sort of have an unwritten rule that "dragon" is dropped off of file names (eg, Albino Dragon => Albino adult.png), but things like "wyvern"/"wyrm"/"pygmy" etc. are not. But this isn't fully standard across our files.

We also don't seem to have a concrete convention for sprites with variations. Things like stripes end up with their files scattered to the winds in categories, because the color leads instead of the breed (eg. File:Red Striped egg.gif, File:Blue Striped egg.gif, etc.). Might be nice to structure file naming convention as breed-first (Striped red egg, Striped blue egg, then they'll sort with each other).


 * Maybe name files for sorting prioritization as ?

Current naming scheme causes sprites of same breed to be split up, and within breeds sprites of same stage to be split up.

Update: while doing the sprite templates, finding so many files don't even follow the current naming convention. Will absolutely need to nail down a good convention before I start going through and cleaning these up.

Spoiler Policy issues
So wiki spoiler policy is that all new releases/ongoing events should be documented in CBR until the end of the release/event. No new articles created, or articles updated until then. Hasn't been an issue until this last holiday, which saw a return of old holiday mini-games. Some slight gameplay differences between original and current runs of the mini-games caused confusion, spoiler notices directing people to CBR for up-to-date info were largely ineffective

I don't love the idea of just gutting the spoiler policy, bc it is more efficient to keep things central until information is finalized. Better plan may be to restructure holiday event articles. instead of Holiday Cooking being for the 2012 Holiday event, it can be just for the mini-game? Create a new Holiday 2012 event article that explains the extras around the mini-game for that year (holiday raffle, red-star recipes counting as raffle tickets, etc). Might reduce the chances of having things that change between uses of the mini-games?

Category cleanup
Need to finish standardizing category names

also need to go through categories and define what they should contain because there's a lot of tangles in these trees


 * Releases (and events?) should be in  format Releases now follow naming convention (except Originals, which i don't quite know what to do with yet)
 * Categories should be plural where applicable (eg, Sprites vs. Sprite)
 * Categories should be sentence case rather than Title Case (eg, Western dragons vs. Western Dragons)
 * Articles should also be sentence case rather than title case but that's another project
 * Standardize terminology to in-game canon (eg, Christmas -> Holiday, DC Drakes -> Drakes)

Event categories
To change "Christmas" to "Holiday" to match in-game terminology, gonna need to shuffle things. Also might need to define structures for the event categories. Lots of articles double-categorized as "Christmas" and "Christmas Dragons"

People Categories
Should just make all people-articles as standard articles. Can transclude into categories for information if we need to, or just link to person article. Articles can DPL the category contents for easy viewing. Saves us having to do all the  links.

Time-Based Conditional Experiments
messin' with parser functions

Cached =

Harvest Location:

Seasonal Variation: