FANDOM


  • When somebody thinks about making an infobox with a completely different design, like myself, he/she should start from either resetting the default settings or overriding it part-to-part(this reminds me of constant nightmare with Bootstrap).

    A standardized system is useful to most of people, but sometimes stifles creative attempts. I would like to have an option to create PI without the CSS bundle.

      Loading editor
    • Welcome, Cafeinlove. There's the option of a compact default theme (when Europa is off) or a high-readibility colorful theme (with Europa on) - neither require handling CSS. This can be done in Special:WikiFeatures c:

      You may find that the CSS practice you get when customizing the infoboxes is of benefit to you around the rest of the wiki. Here's an accessible explanation of what CSS is. This wiki is also a good place to get step-by-step assistance on customizing infoboxes yourself or to have Vanguard do this for you. You can request that help here.

        Loading editor
    • Thank you for replying. Somehow I should have been a bit clearer with my point. I was looking for a way to reduce effort in fighting against the built-in CSS settings while customizing my own theme.

      Talking about the details: for instance, Qualroo.scss has higher priority over Wikia.css — meaning if I want to create my own PI theme, I will have to give all of my selectors even higher priority, which I consider rather valueless work during the infobox customization process. I would more than love it if something like <infobox preformat="false" /> could help.

      It is still nice to know that at least Europa theme is optional.

        Loading editor
    • Ah, I understand. For example, it is going to be difficult to do this:

      .portable-infobox {
          background: #000;
      }

      But it will be possible to do this.

      .portable-infobox.pi-background {
          background: #000;
      }

      The design helper classes should come in useful.

        Loading editor
    • Right. Could help anybody else reading this thread. As for myself, I am one of those guys in the web design business..

        Loading editor
    • Cafeinlove wrote:
      Thank you for replying. Somehow I should have been a bit clearer with my point. I was looking for a way to reduce effort in fighting against the built-in CSS settings while customizing my own theme.

      Talking about the details: for instance, Qualroo.scss has higher priority over Wikia.css — meaning if I want to create my own PI theme, I will have to give all of my selectors even higher priority, which I consider rather valueless work during the infobox customization process. I would more than love it if something like <infobox preformat="false" /> could help.

      It is still nice to know that at least Europa theme is optional.

      Qualaroo should always be overridden by Wikia.css, as Wikia.css is loaded later. But adding a feature like custom selectors (in particular custom classes) are directly oppositional to the purpose of Portable Infoboxes, as they (by definition) make non-portable code opportunities. Such selectors would also destroy, rather than supplement, our ability to use Mercury (our mobile skin) effectively. The design helper classes are the best selectors available for consistent styling. We are looking for additional feature opportunities; this one will not be a good fit.

      Part of that goes back to one of our core portability tenets: content should not define presentation.

      We are happy to help you within our available framework.

        Loading editor
    • My idea was rather a conditional CSS load than conditional selector assignment. I wish my PI not have any built-in effect in desktop mode, while the classes are present there to make mobile layout work as intended.

      I'm not sure this is a good idea, since I don't know the cost of separating PI styling aside to make it optional, nor the side effects of it. I would like to simply say PI's skeleton has a highly opinionated style and it requires way more work to make a creative theme out of it than styling from nothing.

        Loading editor
    • Thank you for clarifying. In that case, it is much easier to override the helper classes. However, blanking all properties is also something we can't support. We can't, as a platform, make Qualaroo optional and have a basic consistent experience on desktop or mobile. Eliminating the defaults would make Portable Infoboxes (and most other elements) dissolve into puddles of goo, which is not a great user experience.

      I'm curious what kinds of CSS you're trying to achieve that requires such "fighting", as this is not a common issue. Do you have mockups or illustrations?

        Loading editor
    • Thank you as well. I understand that. It's not something that I can't roll without, I wanted to hear the opinions.

      The infobox I mentioned above has been implemented already:

      The implementation itself did not take too long, since I am familiar with situations where I have to work with pre-formatted stuff. I just did not like spending time for this process, and was worried about more occasions when I will make templates like this for other communities I am taking part to.

        Loading editor
    • Interesting. Although I'd call what you have there two separate things: the lefthand pane is a navbox (albeit a fancy one) and the infobox is to its right.

        Loading editor
    • Maybe. Since the content section has become relatively narrow in Oasis, I always disliked my first paragraphs being squeezed in the left half, while the ToC + infobox take up the right half. I thought having a full-width infobox above the text content could give us different experience.

        Loading editor
    • Sounds interesting. A little harder to track.

      Would you be interested in us working with you over at 포켓몬 위키 on implementing PIs? I can show you some things that will preserve your existing CSS, or we can walk through the places where there will be minimal compromise. Interested in pushing the limits of what PIs can do with the built-ins?

        Loading editor
    • That's hooray! There are lots of infobox-like templates on there and they are causing serious drop in performance. I recently opened up a forum thread about the topic and started discussing it with our contributors. Your guidance will surely make our mission advance.

        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

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.