FANDOM

FishTank

aka Isaac

Staff Bureaucrat
  • 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
  • I was wondering if you ever found a way that those of us who use Infoboxes (in the form of transformers - which I think you loosely referred to as cancer once) for lookup data for template tables to reflect the infobox data directly instead of manually refilling information?

    I think last I heard you were taking on Dragon age wiki to remove their infobox transformer dependency? Wondered how that worked out and if you were able to do the change but still allowing some sort of lookup data transfer. I am asking because I may take on another wiki and I know you'd cringe if I did an infobox transformers again.

      Loading editor
    • A FANDOM user
        Loading editor
  • It's not really about portable infoboxes, but it is about templates. I never spotted this before, but I think it's related to the last Mercury update.

    Our disambigs, which already looked crap, look even crapper now. Gor some reason, it ignores the template and the text, and just uses the gallery, in a weird order, with no visible captions. It's not really helpful if people look for Batman, but don't actually see any of the two main versions. I found it out through looking at Carmine Falcone... where the leading picture is one of Deathstroke saying Falcone's name (which, as the only alternate comic book version, gets listed before other media). That's not helpful.

    The Disambig is currently listed as Design - is there a better type that makes sure it is included in Mercury?

      Loading editor
    • We've touched on some semi-related issues before, but this is a good conversation to have. I'm going to digress briefly, because your underlying issue is the appearance of these pages.

      So, first things first: what you are calling a disambiguation page is not really well-named. This is a long running taxonomy misunderstanding. Disambiguation pages are intended as connective pages where terms with radically different senses — such as the chemical element "Mercury", the Roman god "Mercury", the planet "Mercury", the Fandom skin "Mercury", etc. — can sort out which is which. People searching for Batman expect to find a summary page for the character who fights crime in Gotham City (unless they're looking for Bruce Wayne's batman (butler / valet) Alfred Pennyworth). Disambiguation pages are not meant to be extensively crawled by search engines nor should they be the landing points for a keyword search. From a search engine sense, what should appear at w:c:dc:Batman is an extensive article (either a review of the shared / common histories of Batman, or more likely the Prime Earth article moved into this position) with a great deal of material. Having the portal page as you have it is a bit of an issue. All the other alternatives, should be branched off the main article such as [[Batman/New Earth]], [[Batman/Golden Age]], and so on.. Yes, I'm fully aware of what a reorganization pain that would be; that doesn't mean I don't think it's not worth doing.

      I had to mention that, because it strikes at why the mobile skin isn't working properly. Both the skin and Google are operating on some of the same basic assumptions. It is expecting an actual article there, and what's on that page is a table at the top (which Google doesn't even try to understand when it crawls) followed by what it thinks are really weird image galleries. The table containing the text is completely ignored because tables are not meant to be used for layout like that, and the crawler (and the mobile skin) thinks that's a message box or somesuch and doesn't contain anything useful. To get it to crawl and render the page properly, it needs text in the basic part of the article. Not in a template. Not in a table.

      Design is, in fact, the right template classification. It has no effect on the mobile skin. The table / template itself is not portable or mobile ready, because it's a table and not meant to be used that way.

      As for the gallery, we're aware that navigational galleries do not work as they should on mobile (with captions and of consistent size), and we're looking at changing those. That Deathstroke image on Carmine Falcone image is probably showing because that's the first image outside of a table of sufficient size or resolution.

        Loading editor
    • We've already vetoed the subpages idea; not all Batmen are called Batman or Bruce Wayne, so that's just weird. Also, grumble grumble we've been doing this since before Wikia existed grumble grumble etc. You've heard that last one before, probably.

      If we look at just the template, what would the best course of action be, to keep some of the esthetic? Is it possible to make it like the other page templates, with an infobox template in the page template? For example, two pseudo-infoboxes left and right (or just one?) for the main images and then just the text plain in the middle? That might even be bottable.

      I've also noticed galleries no longer get cut off after 8 images. We kind of went for extra headers (see Batman) for ease of browsing, but that's undone again with the current Mercury.

        Loading editor
    • An unrelated thing - after the viewership reports on Council, and especially the one about Marvel one, I've been doing some thinking, especially about the lack of an intro paragraph - or rather, if there's an intro paragraph it's below a lengthy ToC. Is it possible to remove the History header, thus forcing the ToC down? It might not help Google, but it would be definitely better for readers. It's just going to look ridiculous on characters that don't have a history yet, but there's a project in there somwwhere...

        Loading editor
    • A FANDOM user
        Loading editor
  • Aren't you the founder of this wiki perchance?

      Loading editor
  • Someone on CC was saying they couldn't make a post, so I was testing it... I'll bet they're using a bad old browser or something like that.

      Loading editor
    FishTank
    FishTank closed this thread because:
    Question answered.
    07:29, May 12, 2018
  • Hi, FishTank. It's nice to meet you. By the way, How do I join the vanguard? It's an invite-only group.

      Loading editor
    • A FANDOM user
        Loading editor
  • Did I not say to not do anything with our templates without expressed approval from the others?

    They have been very clear about not wanting this because there are things they want that the portable infoboxes are incapable of thus we have no use for them.

      Loading editor
    • View all 15 replies
    • Perhaps that requires some clarification. Upon a click or tap, it's always going to expand to full resolution (the 320+px) inside a lightbox / modal. Inside an infobox, it's going to resample and not lose resolution or be blurry; ergo, it can get smaller without the blurriness. It's when that is re-expanded via CSS that the blurriness occurs. It's like taking orange juice, dehydrating it to concentrate, and re-constituting it. If the infobox isn't expanded via CSS past 300px, regardless of the size or resolution of the image, the image won't blur. Does that make sense? 

        Loading editor
    • When the infobox width is a typical size, the image is not blurred.

      Digimon - Arukenimon - PI Digimon - Arukenimon - PI-wide

        Loading editor
    • A FANDOM user
        Loading editor
  • Do you know of any place where I could post or track an Insights-Bug?

    Because from what I read on this wiki my issues with Insights do not belong here (which is what I initially thought).

    Duke Chain'em (talk) 01:25, December 26, 2017 (UTC)

      Loading editor
  • So I'm in the process of converting this wiki's infoboxes to portable ones, and everything seems fine except for the horizontal data line. Basically, I want the height of the line to be shorter than it is by default (specifically, 12px), however, by adjusting the height in CSS it prevents the < br /> tag from working because the section cannot expand past 12px. Do you know of any way to fix this?

    Here is my code:

    .portable-infobox h2.pi-item.pi-title {line-height:20px; padding:5px;}
    .portable-infobox { color:transparent; widith:100%!important; padding:0.5px;  border:3px ridge; border-color:#2cd0ff; border-radius:10px; 
    }
    .portable-infobox .pi-item-spacing { text-align:center; padding:0.5px; padding-left:2px!important; }
    .portable-infobox .pi-header, .portable-infobox .pi-title, .portable-infobox .pi-navigation { background-color:#2cd0ff; margin:1px; padding:0; color:white; }
    .pi-background { background-color:transparent; }
     .portable-infobox .pi-image img { width:99%; height:auto; border-bottom:2px #2cd0ff ridge; padding-top:1px;}
    .pi-border-color { border-color:transparent; }
    .pi-title, .pi-data-label, .pi-secondary-background { background-color:#2cd0ff; }
    .pi-title { border-radius:0 0 0 0; text-shadow: 3px 3px 3px black; }
    .pi-header {border-radius:0 0 0 0; font-size:11px;}
    .pi-data-label { background-color:#2cd0ff; border-radius:0 8px 8px 0; text-align:left!important; padding-left:2px!important; font-size:10px!important; height:17px; }
    .pi-data-value { border-bottom:1px #2cd0ff solid; color:black!important; text-align:right!important; padding:2px; font-size:10px!important; height:12px!important; }
    .portable-infobox .pi-title, .portable-infobox .pi-secondary-font { background-color:#2cd0ff; color:white; }
    .pi-data { margin:0!important; font-size:10px;}
    .portable-infobox .pi-horizontal-group  {
        padding:2px!important; font-size:10px;
    }
     
    .portable-infobox .pi-image img { border-top-left-radius: 10px!important; border-top-right-radius:10px!important; }
     
    .pi-horizontal-group .pi-data-label{ background-color:#2cd0ff; padding:2px; border-radius:5px;text-align:center!important; padding:2px!important }
     
    .pi-horizontal-group .pi-data-value {border-bottom:0px #2cd0ff solid; color:black!important; font-size:11px; text-align:center!important;}

    Code including various themes
    Page with the problem (see under the "Nicknames section when editing

      Loading editor
    • View all 5 replies
    • Another general comment: it feels like your various themes are repeating too many unnecessary CSS rules that are common across all of them. If the different themes only differ in image and color, then theoretically it is possible to only specify the difference.

      See this page for example, where the top portion handles common styling (sizes, shapes, padding etc), and the bottom portion handles custom colors for the different themes.

        Loading editor
    • PanSola wrote:
      Another general comment: it feels like your various themes are repeating too many unnecessary CSS rules that are common across all of them. If the different themes only differ in image and color, then theoretically it is possible to only specify the difference.

      See this page for example, where the top portion handles common styling (sizes, shapes, padding etc), and the bottom portion handles custom colors for the different themes.

      I do know about that, but thank you for letting me know. This was done in a rush and it works alright, but for future themes, I'll calm down on the code.

      Thank you for the fix as well!

        Loading editor
    • A FANDOM user
        Loading editor
  • Hello, it's me again. I just wanted to know if non-Vanguard users are allowed to give unofficial responses to Mentoring requests if they think they know how to solve the users' problems. If the answer is yes, is there a particular template to mark the response as unofficial; on CC there is one, but I'm not sure about here. Thanks in advance!

      Loading editor
  • Hello. Since I really like to work on Infobox styles, I was wondering if I could develop some example ones and then share them here, using the Themes category. Am I allowed to do that or you select only specific styles to be added to that category? Thanks in advance!

      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.