Thread:Ursuul/@comment-30691033-20170812153231/@comment-28083312-20170812170924

I disagree. Like with the Achievement Template, while it was good, it does not show up in Mercury at all & was a pain to accommodate just to make sure it only doesn’t show up, as opposed to actively disrupting the page on mobile. Unlike the Achievement Template however, this one really isn’t needed, doesn’t look identical to the in-game phenomena, & is inferior to simple, clean images (which actually show up in Mercury). While I’m sure you worked hard on it & I appreciate that, & I am sure that if more admins worked on it you might be able to use styling to make it look more like the in-game phenomena than actual images of the phenomena, it simply does not work in Mercury & so as a general principle that kind of thing should be avoided on article pages period. That said, I am glad you are creating templates, I would simply rather you reprioritized which kinds of Templates you should make. If you want to flex your muscles with styling, then the Navbox project is still waiting; I saw you recreated your own navbox using Template:Navbox, but you wrapped it in external styling when you can use the internal style fields to make it look like literally anything you could imagine. Creating a standard style using _only_ the Navbox Template would allow us to begin replacing Navboxes in Conceptual namespaces, with the standard style you helped to create, & we would be able to actually use your styling then because Navboxes don’t work on Mercury anyway, so we don’t need to accommodate it. Beyond styling, creating future-proofed templates such as Template:Interlang or Template:MercuryTab that are designed to work with Fandom’s current & future infrastructure while serving a helpful purpose, would be much more appreciated than the creation of Templates that, while they are well done & worthy of recognition, cannot be used to any purpose beyond that of conceptual namespaces.