User talk:TheGreenMadHatter

Welcome to TheGreenMadHatter talk page. Feel free to send messages to me here. Please create a section and sign with your signature (four ~) Thank You!

Sub-galleries
Do you think we should add all the images to them, or just some of the more interesting ones? You know, like a miniature "featured images"?

Multiple fandoms
I'm not actually 100% of where to place articles that span across multiple sources. E.g. Howard Stark is only seen in Iron Man and Captain America franchises, but not in the globally used Avengers one. Should I place him under the fandoms Iron Man and Captain America, or those two as well as the Avengers one (since that's the name used for the whole movie universe), or skip those and just stick with Avengers? Red Skull is also only seen in Captain America, it does sort of seem wrong to have him marked as an Avengers character.

I don't know anymore ;A;


 * Only problem I can see with this is the "tags" on tumblr and the like usually group together the movie series as the "Avengers" franchise, which then might be confusing if you go here to search for Avengers ships only to not find any :|


 * Other than that I agree.


 * That'd be confusing if we have to do that for every page :| IIRC most templates can already have two fandoms, we could just expand this. (e.g. File:Avengers - Young Avengers - Stony Superboyfriends (Fwips).png)


 * Temp-solution: All images and pages featuring multiple characters from the Marvel universe that appear in the Avengers fandom will be tagged with both "Marvel" and "Avengers". Steve Rogers will therefore have "Marvel" and "Captain America", whilst Stony will be "Marvel" and "Avengers". Sounds good? :]

Databases
Since I'm all for auto-categorizing pages, and making new users have to do as little as possible, I'm thinking of adding template pages to all articles with info (e.g. Template:Steve Rogers). Using this we would have to manually add far less to certain pages, such as the category ones.

What do you think?


 * Just noticed fandom pages have templates with the same name. Whatever, we'll have to rename databases (if you agree to them that is) to Template: /Database, or the navigation templates to Template: Navigation. Let's just flip a coin.


 * What I was also thinking of was that as it is we have to manually add the navigation templates to the bottom of the page, but if we were to follow the wiki's example and make a whole page into a giant template, we could dynamically add the navs to the bottom without the editor having to worry about it.


 * Though that will sort of make it hard for brand new users to understand what's going on, since all pages will become harder to edit when there's a cluster**** of info all over. So we'll just have to decide what's more important: User friendliness or smart editing?


 * Yeah, that's one of the templates I was thinking of. And while that might be easier for those who understand it, I'm fearing less experienced user won't understand how to work it :I


 * But (at least I think so) we still need to give each page a template with info as mentioned earlier, since using the main page would be a hassle (users would have to add the info twice to the main page, and it would look ridiculous). Not really sure if I'm being understandable or not, but I think it could help. I've added links to the Sublinks template that lets the user know if the page has a template or not, which will also add the base text to it when clicked :]