FANDOM


Forums: Index → Improvements and Issues →  Portable infoboxes and you!Forum_Icon.pngPost


So here's a thing.

Your traffic here at the Fairytail Wiki will likely be evenly split between mobile and desktop users by next year. As you can see in the chart below, derived from Quantcast.com, about 45% of your American visitors are already on mobile devices, and about a third of you global audience is on a mobile device. There’s no logical reason to expect those mobile numbers to do anything but expand over the remainder of the decade.

FairytailStats

Look how many of your mobile visitors are from iPhones! As I stare harder at this wiki’s stats, what’s interesting to me is the ‘’composition’’ of the mobile users. About 60% of your iOS usage is from phones. That means that the majority of your mobile traffic is actually seeing our mobile skin. On many wikis the iPad usage is much higher — and iPads see the desktop skin. These stats don’t break down Android, Wndows and other operating systems, but the trend from iOS seems to suggest that a healthy chunk of your visitors are actually seeing our default mobile skin.

That's why I'm really excited to tell you about a new form of infobox that our engineering team have been developing. We call it the "portable infobox". And it does a lot of great things:

  • it looks great on phones - better than any other solution we've come up with to date
  • it's pretty easy to understand how to build
  • it's pretty easy to move your existing code to the new markup — without disturbing the data an images you have in place
  • it operates in the same way for the editor who's actually filling out the infobox as whatever infoboxes you're currently using
  • it will allow you, in the coming months, to actually use the data you put into infoboxes. As we continue to evolve the infobox into 2016, you'll be able to, for instance, add an automatically-updating list to a page of "all the characters voiced by Toshiyuki Morikawa", based upon the fact that you've added voice = Toshiyuki Morikawa to your various character infoboxes.

It would be ideal if we could try to get these new portable infoboxes up on your site by the end of July.

Making the switch

Obviously, you guys are code masters. So I want to give you an opportunity to try to migrate the infoboxes on your own. I know I wouldn’t like it if someone suddenly came onto my main wiki, Tardis, and just stared making changes to my infoboxes!

That’s why Wikia has tried to make it easy for you to help yourselves. When you go to an existing template, you’ll now see a little module pop up in the top right hand corner. It’ll ask you to convert the infobox to the new portable infobox code. If you accept that invitation, it’ll take stab at automatically converting the code for you. The tool isn’t perfect, though, and it will probably be confused by some of your more complex code. But it gives you a good starting point.

Special:Insights

We also have a second tool, called Special:Insights. This tool gives reports for more than just the new portable infoboxes, so you may have already seen it before. If not, here’s the help file. Mainly, though, it just runs various Special pages reports in a more user-friendly way. But the Portable Infobox report is new.

Unfortunately, it doesn’t work so well on your wiki, yet. This is because your infobox templates aren’t in the template namespace, but the project namespace. This is a highly unusual location for infobox templates, and the tool simply couldn’t have anticipated that. But i still wanted to mention Special:Insights to you, because some of our help files will refer to it.

If we moved all your templates to the proper template namespace, of course, Special:Insights would be of great help to you in this project. So I just wanted to ask if there was a particular reason for your infoboxes being in namespace:4, and whether you’d consider moving them to the template namespace?

Asking for help

Like me, you have some complex code in your infoboxes, so you may puzzle over how to translate a few things, here and there. That’s why it's really important that we get crackin' on these during the month of July. The main reason for the urgency is that we now have the ears of the engineering team. They're keenly interested in polishing the product. And so if we find anything that's unusual about your wiki's infoboxes, we'll be able to get very quick support, directly from the engineering team. None of the usual "File a Special:Contact and we'll get back to you with 48 hours" stuff. The workflow is going to be: you tell me, I get on the Bat-Phone to our engineers and we get you an answer within a few minutes, provided the question is asked when our guys and gals are in the office, obviously.

So please, as you go through this process, feel free to ask for any help you need. And, just to make sure these helpful pages are plainly evident to you, make sure you stop by:

I want to stress that this is a rare opportunity to help shape the future of Wikia, and we're so happy to be able to offer it to this community.CzechOut @fandom 07:44, July 23, 2015 (UTC)


100% opposed to the use of this. This is what, like my 7th year on wikia now? Nothing wikia has released in years has ever worked right ever at least until a year or two has passed. When they actually get these running and not failing, then we should consider their use, but I never trust any new product on wikia until at least a year has passed-- God · Pray · 08:02,7/23/2015 

Hey Godisme! Long time, no see. :)
What Wikia are tying to do by offering this to you guys right from the start is to guarantee that your concerns will actually fold into the development of the product. 'Course, that doesn't mean that all your suggestions will be implemented, but with the communities I've helped already, I've seen things get fixed within just a few hours. And I think the product is at a place that can truthfully be called "Version 1.0" — not "Pre-Beta" or anything like that.
You and I have both been around Wikia for a Long Damn Time, so I think you'll know I'm not BS-ing you when I say I've honestly never seen Engineering work so hard, so quickly or so passionately. So although I feel ya on the 1 year rule thing, it just doesn't apply this time around.
Almost half your visitors from the US are on mobile right now. Do you really want that many people to suffer with mobile infoboxes as they are today? C'mon, you're far too design-sensitive a guy to not want to at least try to improve the situation. — CzechOut @fandom 08:26, July 23, 2015 (UTC)
I'm not so sure about this... since it seems one of the main reasons you are promoting this to us is that it will improve how mobile users see the infobxes; how will the new infobox effect those that use PC's?
Could you possibly provide us with an example of how this infobox will look on an already existing page, perhaps on another wiki? Forget it, found the examples. Onfire.gif Wonder Talk 12:01, July 23, 2015 (UTC)

I say yeah! I dont see why we cant take a stab at it. Of course it would be ideal to try it only on new test infoboxes and use them on sandbox pages until we get them working 100% Bickslow Doll Bickslow Doll3Bickslow Doll 2 14:33, July 23, 2015 (UTC)

To answer your question, no, there isn't a particular reason we have them in the Project namespace, so moving them if we decided to use this infobox wouldn't be an issue. And as far as this infobox in general goes, I'm not opposed to its usage. I've never been a mobile browser myself, but I have no issues with trying to make the wiki viewing experience better for them. However, before we consider implementing these on our articles, we'll have to test them out in sandboxes to see if a) there are no issues with them and b) we can make them aesthetically pleasing (something which is very important to us here). But thanks for the heads up! We'll try and see if this is the right fit for us. ^___^ Iam...    JakuhōRaikōben 15:32,7/23/2015

I don't particularly mind this either, especially if we can report any issues/have some suggestions implemented. If this is something that's gonna eventually be used, why not start trying now? Miskos3 Message 17:14, July 23, 2015 (UTC)

Thanks much for your comments so far. I'm glad to see such a quick response from a variety of different people. I agree strongly with Jakuho's notion that these new infoboxes must be aesthetically pleasing. Luckily they are — though styling occurs exclusively through your CSS files. Typically, Common.css is the best place to put it. Inline CSS, like adding rounded corners directly to the code of a template, generally doesn't work.
WonderfulUnicorn mentioned finding some examples of infoboxes. I'm not sure exactly which ones were discovered. But to show you at least one example of really classy design, please go to: http://fireemblem.wikia.com/wiki/Template%3AWeaponInfobox/Draft, and examine http://fireemblem.wikia.com/wiki/MediaWiki:Common.css to see the supporting CSS.
Finally, though I agree with Jakuho's notion of creating a "sandboxed" version of these templates, I'd probably not recommend that you go off to a separate sandbox wiki. Instead like has been done over at w:c:fireemblem, I'd keep the new infobox design on this wiki, on the /Draft subpage that's automatically created by our migration tool. Then, pick one page where that infobox is transcluded, and switch the infobox over to the /Draft version. As long as you don't approve the /Draft, you'll have time to tinker with the new infobox until you get it just the way you like. Thus, you'll be able to take full advantage of the CSS that's actually here, and see how the infobox looks on a real page, on this site, without fear of damage to the infoboxes as they currently exist. — CzechOut @fandom 21:19, July 23, 2015 (UTC)
Quick question. All of our infoboxes here on the site use different theme colors depending on which page they are going on - could those theme colors be customized inline or do all of the infoboxes need their individual theme colors customized via the css pages. Iam...    JakuhōRaikōben 23:03,7/23/2015

Looking at all of this, I see no issue in giving it a shot. If it makes the wiki more mobile/tablet friendly or whatever, then it's not a bad thing in my books.

That being said though, I must ask the same question as Jak above. Our current infoboxes have strict colours and layouts so that we can easily change them between pages, and therefore altering them is quick and easy, and adding new versions for new characters etc. is a breeze. If we are going to need a bazillion different types of code just to change the colours and layout slightly, then I am going to be a lot more hesitant, because that will really just be wasting our time quite a bit.

But, so long as we can get them looking good, I think it's cool. Might also give us a chance to clean up the info in our infoboxes, because tbh, I don't think we've revised a heap of our pages in years .-. ☆°・*CarrotSays...*・°☆ 02:08, July 24, 2015 (UTC)

Sorry for the delay in answering, guys! No styling is really done inline. Instead you create themes in CSS and then call those themes. It's totally possible to do the kind of intricately-styled variations that you have now. For the end user/editor it will be easy to switch from one theme to another, but it will take a bit of time to set up the CSS. Don't be afraid of that, though: once you've set it, you can — as the old advertisement copy goes — forget it. — CzechOut @fandom 19:01, July 30, 2015 (UTC)
Thanks for the reply! I'll get started seeing what I can do with the .css. ^___^ Iam...    JakuhōRaikōben 19:37,7/30/2015
Any success with the CSS? Don't be afraid to ask for help if you need it :) — CzechOut @fandom 17:41, August 25, 2015 (UTC)
Sorry, we have very short term memory on this wiki, lol. :D I'll start fiddling around the CSS as soon as possible. Thanks for checking in. ^___^ Iam...    JakuhōRaikōben04:42,8/26/2015
Hey again, guys! So one of our engineers dropped by today and built you a brand new version of Fairy Tail Wiki:Character Template (Fairy Tail). Even though it's going to make this page extend down a bit (and it has a big red error because we're not going to bother with a closing references tag here in a forum, I thought it important to just bring the thing here so you don't have to do any clicking around.
What do you think of it? Are we headed in the right direction for you? Are there things about it you'd like to see change? Please feel free to kick the tires and give us as detailed a response as you can. Thanks! :) — CzechOut @fandom 23:32, October 23, 2015 (UTC)

My only problem is the font size. Any way to dumb that down a notch or two?
WrathRogue ChibiZero 23:45, October 23, 2015 (UTC)

My only problem is that its unreadable in monobook. Are these entirely new classes that don't inherit from already styled classes?-- God · Pray · 00:26,10/24/2015 

That looks amazing!! Many thanks to the engineer who helped us out!! And I really, really, really hate to nitpick, but as Wrath mentioned, is there anyway to alter the font size? If we could bring that down a little, then it'd absolutely perfect. Iam...    JakuhōRaikōben04:49,10/24/2015

Hello all!
Yes fonts can re-sized in CSS. @User:Godisme, the default Portable Infobox when viewed in the monobook skin is not very useful as you stated but it can be adapted with specific styling.
We would like to have community approval on the example in this thread as soon as possible, so please let us know what size the font should be (larger, smaller, specific px?)and any other concerns that may have come up in the last few weeks. Thanks! Pinkachu@fandom (talk) 05:22, November 22, 2015 (UTC)
Smaller. Preferably the same size as our current infoboxes. And also, we currently use the switch template in many of our infoboxes. Would we still be able to use that with the portable infoboxes? Really sorry about all the questions - we're just very thorough here on the site. Iam...    JakuhōRaikōben05:29,11/22/2015
I don't know why this edit has changed, but everytime i see a character article or an event article or guild, it only show Template:Character Template (Fight) in red. which that isn't working all the sudden. Kunoichi101 (talk) 02:38, March 13, 2016 (UTC)
And what made you think that undoing all the edits that the bot made was a good idea??? Thanks for wasting my morning by undoing yours. Clearly, this was a work in progress. Patience is something many clearly lack. Miskos3 Message 08:26, March 13, 2016 (UTC)

And with that said, there are still templates that I noticed haven't been working properly: Bradman, Type 74 Long-Range Rifle, Gogotora, Age Seal, Briar, Earth Magic are the affected pages that I've seen (don't wanna link the templates cuz yea...) Miskos3 Message 08:26, March 13, 2016 (UTC)

I'm handling that now guys. It seems he forgot to move a few templates over which was what was causing that issue. Iam...    JakuhōRaikōben08:32,3/13/2016
God bless you Miskos3 Message 08:34, March 13, 2016 (UTC)
Oh, I get it! A number of templates weren't categorised at all, so I had no idea they needed to be moved. But the bot naturally found all calls that needed to be moved. So the calls got moved, but the "invisible" templates weren't. Hence: redlinks. Sorry about that guys. Thanks, Jakuho, for knowing that there were some uncategorised templates floating around out there. I'm now adding the right cat to all those uncategorised templates so that things like this don't happen again. — CzechOut @fandom 16:13, March 13, 2016 (UTC)
No problem at all. ^__^ Iam...    JakuhōRaikōben19:44,3/13/2016

Cite error: <ref> tags exist, but no <references/> tag was found
Community content is available under CC-BY-SA unless otherwise noted.