FANDOM

FishTank

aka Isaac

Staff
  • I live in San Antonio, Texas, US
  • I was born on November 18
  • My occupation is Community Technical Specialist at FANDOM
  • I am male
  • Bio I don't always help FANDOM users; but when I do, it's as an anthropomorphic fish in an armored military vehicle.
  • [Show More]
A FANDOM user
  Loading editor
  • Hey,

    I posted on Monochromatic Bunny's wall about using a Crossref template for episode references, and your input is needed. Would you care to have a look here?

      Loading editor
    • A FANDOM user
        Loading editor
  • I've thought about adding cast lists to episode pages. However, the method I was thinking about using was not portable, so I used PIs.

    See here - Template:Episode Cast/testcases (first example)

    The PIs are altered with CSS to give the look of wikitext cast lists, and it also displays very nicely on mobile.

    However, after doing that, someone pointed out there was a rather simple way to accomplish portability with the cast lists by using only wikitext. That is the second example in the link above.

    Now, I'm sending this to you since you introduced yourself as Wikia's go-to portability guy. :P Which do you prefer, and which do you think looks better on mobile?

    I prefer the PIs since the infobox gives the cast list a nice look, as stated above. The purely wikitext example looks like any normal text with headers. I don't like that because headers on mobile are not collapsible, making some pages unnecessarily long (also causing long periods of scrolling).

    So what do you think?

      Loading editor
    • The first thing I'd like to note is that this is really not what Infoboxes are meant for, as what you're describing are not key / value pairs. It seems like using it might be a good idea here, but Infoboxes are meant to be used specifically for data; using them in this way is actually anti-portable, as it confuses the data-collection part of the parser. If it helps (and you think like a coder), think of an infobox template as an object-oriented class. Lodging arbitrary things in there is not always a good idea. An infobox is also, by design, only an element offset from the corner of the content.

      The alternatives? Use another portable element (the one that would spring to mind is either Sidebar (aka vertical Navbox) or Side box), neither of which you want, as they take the data out of the narrative body. What you're really trying to accomplish is a multicolumn layout.

      There's a bit of a difference between true portability and "it looks good on mobile". There's also a little bit of difference between "legally portable" (what the server flags as portable) and "literally portable" (actually works on all platforms). For better or worse, due to abuse, nothing with a <div class="..."/> is considered legally portable.

      So, since what you really want is a way to make is a block that cascades into a multi-column layout on desktop and is space efficient on mobile, the best case is to wrap the lists in a span (which is legally portable), and to make the class for it define multiple columns in Wikia.css. Now you run into the next problem, which is that those lists have headers. Those are block elements, and they can't work inside a span. You can alter the span, as a hack, to be a block-level element. It'll come off as illegal HTML, but it will achieve the result you're looking for.

      So: the longer version of the question is to wonder why and whether you want to accomplish a given result. It's actually much better on mobile to not show the cast list for a given episode at all, as it provides mostly redundant data and is a short (but growing) list that takes up episode space with little payoff (few people navigate such links from an episode page, and it's considered largely redundant unless you're doing it strictly for data purposes). What's the best way you want to represent this, and is it actually useful?

      > I don't like that because headers on mobile are not collapsible, making some pages unnecessarily long (also causing long periods of scrolling). All headers being pre-collapsed are the norm in the Community Apps, and I heard a rumor that this may be the behavior in Mercury (the mobile skin) by the time that Community Apps start using Mercury. There are several reasons for this, including measured increases in engagement and (as you mentioned) long scrolling in articles.

        Loading editor
    • I initially came up with the idea because I wanted the look of Once Upon a Time wiki's cast lists, but they use the col-begin, col-break, etc. templates. A Vanguard member suggested I use PI to accomplish the task, since it would look better than the previous design on mobile.

      Anyway, with your reasoning, I can see how this particular design wouldn't work. :)

      I wanted to include the cast lists because this is a wiki. I believe we should have anything and everything relating to Stranger Things. Of course I don't mean everything, but rather everything that is factual. Some users may find it useful, and some may not. That can be said with every feature.

        Loading editor
    • Don't get me wrong, I'm all for more data. But I also recognize that with more data comes more challenges in displaying that effectively. Really, the best place for a cast list is in a sidebar, not in the body of the article. Such a sidebar would not be displayed on mobile at all, but the data would still be collected and presented in an accessible way on desktop. I think we should have a <section> element that handles this in the body of the text, or an <aside> that handles it in an offset (like an Infobox or a Sidebar). Those are just portable solutions we haven't developed or enabled yet. :-)

      A Vanguard member suggested I use PI to accomplish the task, since it would look better than the previous design on mobile.

      Which one? I may have to talk with them about that.

        Loading editor
    • Hopefully there will be more portable solutions in the near future. Thank you for your long and detailed replies, I greatly appreciate it. :)

      The user was Trollocool. However, after a wikitext solution was mentioned by another user, Trollocool suggested I use that method instead of the PI.

        Loading editor
    • A FANDOM user
        Loading editor
  • Do you think the season 2 episode pages should be listed/mentioned on the wiki? I'm not sure if the titles in the Season 2 teaser were officially announced as the episode titles (even though they most likely are).

    Editors on Wikipedia have removed the episode list as the person who added them did not source the episode titles.

      Loading editor
  • Hello!

    I'd just like to know, which is more efficient for the two posters on the Season 1 page, sliders or a gallery?

    Thank you!

      Loading editor
  • The episode names for Stranger Things on Google are "Chapter One: The Vanishing of Will Byers", "Chapter Two:", etc.

    Do you think we should name the episode pages using that style?

      Loading editor
    • I don't actually. Beyond the obvious bulk, for reference purposes it's potentially problematic because of the colon in the title. If necessary, we can add redirects. I can ask our SEO people if there's a significant difference.

        Loading editor
    • Ah, okay. It would be great to ask Wikia's SEO people, thanks so much. :)

        Loading editor
    • Spoke to our SEO people. Regarding the "Upside Down" page naming:

      In this case the page name is not as important as our internal linking structure. That is what will tell Google what the most important/valuable/interesting page is - and that is the one we want to rank. You can have both pages on the wiki, but send the contextual and navigational internal links to best article on the topic (not the disambiguation page). The disambiguation page can be linked to from those relevant articles, but we want to send that link value to the “right” page. [...] [In the case of Stranger Things] the article name doesn't matter as long as it is consistent. Feel free to have a disambiguation page, but do not link to it as the main internal link for that term. Rather, link to the episode when you mean the episode and the location when you mean the location.
      There's more also, but the boildown also is that Google is going to more strongly link to the most relevant terms, rather than the "Chapter One:" which is considered filler.
        Loading editor
    • A FANDOM user
        Loading editor
  • Hi!

    I'm kinda new at this wiki thing, so please bear with me if the answers to my questions are obvious to you.

    1. In the "Locations" category menu, there is a link to "Benny's Diner", which redirects to "Benny's Burgers". Shouldn't "Benny's Burgers" be in the menu instead? I can't figure out how to fix it.

    2. Is there a general discussion somewhere about what categories should exist? For instance, I think there should maybe be a "Trivia" category where currently category-less pages like "MK Ultra" and "Demogorgon" could be placed, and there could also be subcategories like "Props", "Production" and others, though since I'm new I don't feel comfortable arranging this on my own (I'm not even sure how to do it properly).

    Thanks in advance!

    (I wrote the same message to UmbraStar13 but he said I should probably talk to someone else as he didn't know much about this sort of stuff apparently.)

      Loading editor
    • Benny's Burgers is in the menu. It just didn't change there right away.

      There's no general discussion at the moment about what Categories should be where, and there's no real policy right now. Personally, I'd argue that there's no real place for articles on this community MK Ultra or Demigorgon, and that those should be links to relevant articles elsewhere (such as Wikipedia or the Dungeons & Dragons Wiki).

      Production makes for an excellent category, though, and Stranger Things/Production should be in it. 

        Loading editor
    • I wouldn't mind short articles about MK Ultra and the Demogorgon and such, with some sort of "read more" link to Wikipedia or other relevant material. I mean, what's the harm? But where to place them is a little tricky of course...

      But alright, so we agree that a Production main category should be created! How would you go about doing that? I'm really not well versed in the technical aspects of this.

        Loading editor
    • A FANDOM user
        Loading editor
  • Hey!

    I see that the merge has been completed. However, you replied to my message on the old wiki and it is now lost due to the merge. Do you remember what you said?

    Also, it seems like I've lost my admin rights. Would I be able to regain them because that wiki merged into this one?

    Thanks. :)

      Loading editor
    • I've restored your admin rights. Still waiting to hear about my own. :-)

      The merge is mostly complete. Is there anything you see is missing?

      The old wiki is not actually lost, by the way.

        Loading editor
    • A FANDOM user
        Loading editor
  • Hey!

    I added the plot for the first three episodes. Please tell me what you think, as this is my first time writing plots.

    Also, I added the episode plots from Wikipedia as placeholders for the time being, just for the sake of content. I did use the Wikipedia template to indicate the info was from Wikipedia.

    Finally, I replied to your comment on my blog about my design. I included the specifics about the Theme Designer.

    Thanks. :)

      Loading editor
Give Kudos to this message
You've given this message Kudos!
See who gave Kudos to this message

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.