FANDOM


  • We’re reaching out to a few of our top communities, hoping to get you on board with the migration to the new infobox markup. And we have tools to help!

    Why we’re doing this

    Simply put, most current infobox structure translates very poorly to mobile experiences and any device that doesn’t use desktop-style displays. On desktops and laptops, they often look amazing. The problem is that Wikia’s traffic is trending mobile. There is an important graph on our recent forum post about infoboxes that illustrates this trend.

    Mobile is the future, not just for Wikia, but for the web as a whole. Take a look at the recent trends and future growth predictions for mobile traffic. It's staggering.

    We partnered with the Wikia community to create this new markup to make sure that your hard work can be easily displayed on mobile devices (as well as any future technologies) without any new coding conventions. It’ll take some effort up front, but we’re here to help, and the work you put in now will pay for itself tenfold in the future.

    Tools we’ve designed to ease the process

    We’ve enabled two new features on your community. One is a tool for migrating the “old” infobox code to the new markup. It identifies templates on your community that look like infobox templates and places a box on the right rail of the template page. When you click the “Generate draft markup” button in this box, it opens a new tab containing a draft of your infobox using the new markup. You can read more about the migration tool at Help:InfoboxMigration.

    The second is a new feature on Special:Insights that will highlight which infoboxes on your community have not been migrated to the new infobox markup. You can click on the infobox title link itself to see the old markup, or simply click the “Convert!” button on the right, which performs the same action as the “Generate draft markup” button mentioned above.

    This is our help page for the new markup, which goes into detail and includes multiple examples. I look forward to your feedback and answering any questions you have.

      Loading editor
    • As an example, I created Template:InfoboxModTest as a converted version of Template:Infobox:Mod. You can see it in action at User:JoePlay/test. I embedded a small bit of CSS to center the text on the title and headers, which are left-aligned by default, to match the existing infobox.

        Loading editor
    • cool

        Loading editor
    • i have no idea what that is....

        Loading editor
    • i prefer wikia apps. the ones for terraria and elder scrolls are excellent.

        Loading editor
    • This new markup nearly completely deprecates all the coding we've put into the infoboxes to fully summarize each. I would also like to mention that the Mod Infobox is nearly completely unused in comparison to others such as Item and Monster.

        Loading editor
    • Heya :)

      Our team of engineers in Poland is really excited to work directly with your wiki during the month of October. You might be interested to know that, not only has your traffic from mobile grown since August, but so has the sophistication of our new infobox code. We'd love to show you what we can now do with infoboxes. It would involve some staff members you may or may not know working on your wiki, and likely altering MediaWiki:Wikia.css — but only to affect the styling of infoboxes.

      Would you have any objections to us providing you mockups for {{Infobox:Item}} and {{Infobox:Monster}}?

        Loading editor
    • I have absolutely no problem with seeing some mockups, as my main concern with porting the code is the loss of functionality we would previously have suffered. I do still stand by my opinion that the mobile skin needs quite a lot of refining, as the vast majority of mobile-styled skins I've come across (not referring to Wikia alone) sacrifice functionality and aesthetics for faster loading times. With a large portion of mobile users having above-average devices, I don't see any reason for them to need a mobile theme when the Oasis theme functions perfectly.

        Loading editor
    • Dzylon here. What perceived issue are you actually looking to fix here? A couple pieces of information are obscured on mobile, so we need a couple of tweaks, but our infoboxes work pretty well on phones already. What use is there for any kind of serious restructure when you're already handling things with mobile-specific CSS?

      http://i.imgur.com/N9ZvVoi.png

      Edit: Btw Path, if you add alt codes to the images in the quality and coins templates, I think those bugs shown in the screenshot I posted will be fixed.

        Loading editor
    • Hey Pathogen —

      It would help us help you better if we knew precisely what loss of functionality you think might be on the cards. Do you have any examples of functionality that must be preserved for you to perceive of the mocks as successful?

        Loading editor
    • Anon1681 wrote: Dzylon here. What perceived issue are you actually looking to fix here? A couple pieces of information are obscured on mobile, so we need a couple of tweaks, but our infoboxes work pretty well on phones already. What use is there for any kind of serious restructure when you're already handling things with mobile-specific CSS?

      http://i.imgur.com/N9ZvVoi.png

      Edit: Btw Path, if you add alt codes to the images in the quality and coins templates, I think those bugs shown in the screenshot I posted will be fixed.

      Heya Dzylon, I'll test out the alt codes and try viewing them on my mobile browser, thanks for the tip! I would never have thought of it myself. Also, have you lost access to your previous account?

      CzechOut wrote: Hey Pathogen —

      It would help us help you better if we knew precisely what loss of functionality you think might be on the cards. Do you have any examples of functionality that must be preserved for you to perceive of the mocks as successful?

      The way most of our infoboxes work is through multi-leveled template transclusion; my worry is that this functionality would be damaged or made more complicated/less efficient. Example:

      1. Infobox:Item checks the validity of an item's value parameter to see if it's the proper numerical value (e.g. 12345 for 1 GoldCoin Small 23 SilverCoin Small 45 CopperCoin Small
        • If it's a valid number, it'll use ValueCalc to display the correctly-formatted amount.
        • If it's not, it'll simply display whatever the value parameter was set to (e.g. {{gc|1}} {{sc|23}} {{cc|45}} for 1 GoldCoin Small 23 SilverCoin Small 45 CopperCoin Small)

      This being just one example, I wonder how the new code would affect this function. Also, I am of a mind with Anon1681 above (or Dzylon as it seems), in that a couple of tweaks are all that I believe should be needed.

        Loading editor
    • Has anyone seen this nonsense survey? All the "choices" make you either look lazy, stupid, or that your reason can be easily countered. Where is the option to say " Our infoboxes should function fine for the majority of todays mobile users with the quality of devices they own"? 

      2i06o3p.png

        Loading editor
    • Squazzil wrote: Has anyone seen this nonsense survey? All the "choices" make you either look lazy, stupid, or that your reason can be easily countered. Where is the option to say " Our infoboxes should function fine for the majority of todays mobile users with the quality of devices they own"? 

      This is a very good point. I think the main problem that mobile users have is not with the infoboxes themselves, rather with the skin used to replace oasis.

        Loading editor
    • The Pathogen wrote:

      Squazzil wrote: Has anyone seen this nonsense survey? All the "choices" make you either look lazy, stupid, or that your reason can be easily countered. Where is the option to say " Our infoboxes should function fine for the majority of todays mobile users with the quality of devices they own"? 

      This is a very good point. I think the main problem that mobile users have is not with the infoboxes themselves, rather with the skin used to replace oasis.

      All of the above. If we could just get rid of the garbage mobile skin that no sane person actually uses (I always switch to the non-mobile layout on my devices anyway because they can handle it and it looks worlds better), and just keep Oasis up-to-date and optimized for mobile devices, I really don't see why all this trouble is necessary. And that "survey" is pathetic.

        Loading editor
    • A FANDOM user
        Loading editor
Give Kudos to this message
You've given this message Kudos!
See who gave Kudos to this message
Community content is available under CC-BY-SA unless otherwise noted.