Template talk:Suite

I actually might suggest E2E6FF for the background color. I think you'll find it looks nice when these are clinging like barnacles to disambig templates.--Rosicrucian^Talk 02:52, 21 August 2009 (EDT)

So is it okay for us to start using this, or should we wait for stuff to be finalized? - Semysane 02:56, 21 August 2009 (EDT)

Right now the Optimus Prime G1 articles are proof of concept. I wouldn't go nutty on this just yet.--Rosicrucian^Talk 03:04, 21 August 2009 (EDT)

Right. Response is positive so far, but it's polite to give people a chance to respond in case someone has an outright objection (or just thinks of a really good reason you should Not Do That.)

Normally I wouldn't proof-of-concept it on such a prominent article either (better to go obscure when testing) but really... there is no article other than "Optimus Prime (G1)" that really can show this off properly -Derik 03:14, 21 August 2009 (EDT)

#E2E6FF seems too intense, personally. Like it's calling a distracting ammount of attention to itself. (Though I agree the color make sense, from a color-coding standpoint.)

You want to experiment, just set the background-color attribute for .tt1_suite. Your personal css file will override the development one. -Derik 03:19, 21 August 2009 (EDT)

Hmm, my only concern with it would be if it got too wide. Is there a way to wrap the contents over more than one line? Though I don't know how likely it would be for us to have a whole pile of subsections all on different pages... --abates 03:50, 21 August 2009 (EDT)

There is not currently. I'm actually proposing a 4th sub-section for the Optimus Prime article @ the Community Portal specifically in order to make the template wider so we can test various solutions. (If it goes two lines do we want to down the font size? Put in actual bullets like on the franchise nav to make it clearer?)

My suspicion is that we'll end up with an optional explicitly-setable width or max-width on the template, which we then add in if it gets too wide. (preferable to a 'general' max-width which 'barely' forces the thing to two lines on an article where a slightly wider suite template would be preferable to a two-liner one.) -Derik 04:13, 21 August 2009 (EDT)

Whitespace issue

Can this template be fixed so it doesn't cause excessive whitespace at the top of articles? Mimi 05:15, 29 April 2013 (EDT)

Moving the current suite pages

The way we have it at the moment, Optimus Prime (G1)/suite is a small page in the main namespace which is useless on its own, but comes up in searches and using the random page function. I propose we move them to subpages of Template:Suite, so aforementioned Optimus Prime's suite would be at "Template:Suite/Optimus Prime (G1)" and so on. This would take them out of the main namespace and they would still function identically. --abates (talk) 19:07, 10 December 2014 (EST)

I'll second this suggestion. I can't think of any reason to keep these in the main namespace. --Tigerpaw28 (talk) 16:10, 14 December 2014 (EST)

My main concern with moving them is that it might make them harder to find/create, but I guess once the documentation is updated it'll be all right (and we can add a link to [1] to make them easier to find). --abates (talk) 22:17, 17 December 2014 (EST)

Rather than moving them individually, I just made one big list at {{Suite/list{{#if:||{{{2}}}|}}}}. The version that uses that can be seen (and tested) at {{Suite/test{{#if:||{{{2}}}|}}}} - I haven't overwritten the live version yet. - SanityOrMadness (talk) 14:27, 18 December 2014 (EST)

That seems like it would make them harder to create/modify, since people doing so will have to know how to edit templates. --abates (talk) 14:51, 18 December 2014 (EST)

No harder than adding a faction icon or Go-Box. You're doing the same thing as now, only instead of posting (e.g.):

{{subsuite|content=*[[Blaster (G1)|Main]]
*[[Blaster (G1)/Generation 1 cartoon continuity|G1 cartoon]]
}}<noinclude>[[Category:Page suites]]</noinclude>

to X/suite, you're adding:

|Blaster (G1)=*[[Blaster (G1)|Main]]
*[[Blaster (G1)/Generation 1 cartoon continuity|G1 cartoon]]

to {{Suite/list{{#if:||{{{2}}}|}}}}. - SanityOrMadness (talk) 18:08, 18 December 2014 (EST)

Hmmm, I think I could go for Sanity's setup. It really doesn't seem to require any more effort than the current set up to modify or add (You go to the page, add the link/suite in the right spot. Finding the right spot is a little bit more complex, but not drastically so.) and this might actually reduce some caching load on the server (if the suite pages themselves are actually cached). --Tigerpaw28 (talk) 20:33, 18 December 2014 (EST)

I'm thinking if we put spaces between each entry in the list, it would make it easier to find individual entries when editing, but I'm not sure if that would mess up the formatting on the end result. --abates (talk) 21:35, 18 December 2014 (EST)

I suspect it would - new lines have no meaning to/impact on the #switch function, so a double-newline at the end of each entry would insert a paragraph break there (just like anywhere else). - SanityOrMadness (talk) 23:55, 18 December 2014 (EST)

We could probably fix that with css (set the line height on the second paragraph to 0 or something). --abates (talk) 01:10, 19 December 2014 (EST)

I stuck some extra lines in using | to avoid the paragraph breaks - it works fine and makes it a lot easier to see where each entry begins and ends. --abates (talk) 02:55, 28 December 2014 (EST)