Forum:Brickipedia: The reincarnation/Templates and infoboxes

From Brickipedia, the LEGO Wiki
Forums - Brickipedia: The reincarnation/Templates and infoboxes
This page is waiting to be archived by an administrator. Please do not edit the contents of this page.


Anything we want changed about any templates? Any we want removed or added? NovaHawk 23:50, 2 July 2014 (UTC)

  • One small thing I don't personally like is on set articles, the bar at the top which I think used to be white has been changed to one of the colors used on the infobox. Since the infobox color is pretty vivid, I find it jarring and sort of ugly. I'd like to change it back to white or to a shade of blue which matches the site background (though some of them are different colors, so I don't know how easy that would be). Anyway, that's all that immediately comes to mind. Maybe we could update maintenance templates with rounded corners or something to make them seem more modern? Berrybrick (talk) 00:10, 3 July 2014 (UTC)
    • The set header change was done due to extreme lack of response, but did end up as a 3/1 vote. I'm happy to try something different if necessary personally. I like the idea of redoing templates to be more curvy and fit with many of the templates deisgned after the move NovaHawk 00:14, 3 July 2014 (UTC)
  • One thing I would improve is the Price template as some of the images for the flags aren't the same width, though they are the same height and it bugs me whenever I look at it. This may be something I can modify whenever I next get some spare time. SKP4472 (Admin) 17:26, 7 July 2014 (UTC)
    • I went with height so they didn't affect the line spacing (see extreme expample of what could do that). But they're different widths because flags all have different dimensions :) NovaHawk 23:09, 7 July 2014 (UTC)
      • Ah right, I didn't know flags could have hugely different dimensions. I always thought that they all conformed to a specific size ratio. Never mind then. Using the same height is better than using the same width as it's easier to read than having huge spaces between prices. Thanks for the clarifciation, I appreciate it. :) SKP4472 (Admin) 10:39, 9 July 2014 (UTC)
  • Also, the release date in the Infobox template is rather inconsistent. Some pages will list a release date as 'July 28, 2008' or July 28 2008'. Also some state different release dates for individual countries. Should we start providing release dates for individual countries or should we just stick to a year of release to keep things simple? SKP4472 (Admin) 17:28, 7 July 2014 (UTC)
    • I think for things which have specified release dates, such as movies, some exclusive sets which have the date mentioned by some official source, etc. that they should be using {{Date}} (an incomplete template I was working on, it's functional, I just need to add more countries). Unless it's a global release, in which case just use "month day, year". For set articles which don't really have a specific release date but just show up on shelves, I think we should have the release date of where it first appeared (month listed only). Or, maybe we could have the release date of where it first appeared, with the US release date underneath (for the largest audience). But I think keeping these to the nearest month would be best, as it's possible a set could be put out on one day in an obscure country, but wasn't reported until a couple of days later, making the day wrong. NovaHawk 23:09, 7 July 2014 (UTC)

ThemeTable[edit source]

  • At the moment, {{ThemeTable}} is virtually useless, apparently becuase of RAM. I was thinking we could have a similar "SetTable", which is more of a grid, like this, but without the break between the templates:
It does mean manually entering the filename for the image, and no info on the pieces/price is displayed however... but it's better than nothing at all isn't it? NovaHawk 05:20, 9 July 2014 (UTC)
Yup. CJC95 (talk) 14:21, 9 July 2014 (UTC)
Agreed, I like it. -NBP3.0 (talk) 15:15, 9 July 2014 (UTC)
I like big images! I'm not such a fan of the sideways scrolling though. More generally, I think replacing themeTable with something like this is good. Obviously becuase of the display issues, but also themeTables are really boring to look at... (SMW grabbing the image?) UltrasonicNXT (talk)
I thought SMW grabbing the images was the whole reason that themetable didn't work? :P Sorry about any horizontal scrolling- I should've put less in the box instead of just catering for my screen- when I get the time, I'll probably work on a JS function to get it so there's no horizontal scrolling, and the number of sets going across would be determinate on the screen size. NovaHawk 22:16, 9 July 2014 (UTC)
  • See User_talk:NovaHawk/SetGallery for a working example (no JS required) NovaHawk 12:26, 14 July 2014 (UTC)
  • Personally I like our previous layout more. It's easier to read being in rows instead of being rows and columns for each set. I think to redesign our current layout we should increase the size of the images for the sets and give it a more modern (and mobile-friendly) layout for row organisation. I really like how Brickset does their rows for set lists: http://brickset.com/sets/query-44 --ToaMeiko (talk) 20:40, 14 July 2014 (UTC)
    • Ah, yeah... but aren't you forgetting it doesn't work? :P I'd prefer to have a bit more information there myself, but that isn't an option really NovaHawk 22:08, 14 July 2014 (UTC)
  • I'm happy with anything that will actually display, and not crash pages. So this looks fine to me. :P -Cligra
  • I don't mind a new design, but manually entering the image filenames will/would be a pain. --LK901 12:18, 27 October 2014 (UTC)

Part infobox redesign[edit source]

This section is resolved, but preserved for record-keeping purposes. Please do not edit this area.

  • Proposed redesign. It would eliminate the need for a part gallery template, have a place for the part's official name in the header, something the current template doesn't have, and make it easier to see which which colour is associated with which Element ID. (original forum here) NovaHawk 02:27, 27 October 2014 (UTC)
  • Going ahead an implementing this. I've been trying to get a response about this for the last six months, and I'm fed up with trying to squeeze a comment out of anyone. Obviously everyone has more "important" things to discuss than the appearance of 88 articles. I'll also be going through and closing off other things that have had little/no response from these forums in the next few days. If anyone has a problem with this, sue me (or better yet, start commenting in open topics). NovaHawk 06:33, 4 November 2014 (UTC)

Extra parameter for Template:Set[edit source]

This section is resolved, but preserved for record-keeping purposes. Please do not edit this area.

  • I'd like to have an extra field, "mn" for {{set}}. Basically, what it does is change the "Minifigures:" bit to something else when it's appropriate. For example, mini-doll figures are not minifigures, yet every Friends set uses the "minifigures" field. Therefore, if you want to change it, you could just do |mn=d, and it'll say "Mini-doll figures" instead of "Minifigures". Similarly for TECHNIC figures, microfigures, Belville dolls, or a generic "Figures" which could be used for things like BIONICLE, or if there's a mix of things like Bigfigs, minifigures and animals. NovaHawk (talk) 00:25, 30 October 2014 (UTC)

Minifigure Gallery with extra views[edit source]

Example: User talk:NovaHawk/MG2 (and requires you to add the code from User:NovaHawk/common.js to <insert name here>/common.js

  • Just an idea where we could fit back views and shots of figures with their second faces all into the minifigure gallery template. There are a number of problems (mainly handling what would happen if there is more than one minifigureGallery on the page), but just wanted to know whether it was worth doing before I bother to go any further. NovaHawk 00:19, 31 October 2014 (UTC)
Not sure what you would use it for. I suppose to stop side scrolling on very large galleries. --LK901 10:17, 31 October 2014 (UTC)

Infoboxes[edit source]

This section is resolved, but preserved for record-keeping purposes. Please do not edit this area.