The Sims Wiki talk:Project Message template standardization/Manual of style

Discussion aspects
Add aspects of the layout under Heading 3 here eg. width, border etc.

Width
In order to maintain a sleek design, I think the width of the entire message should be relatively small. It should also be dynamic to scale with the many different user resolutions available. Here's some suggestions: Duskey ( talk )( blog ) 08:47, July 14, 2010 (UTC)
 * Full page message at the top before other content: 60%
 * Messages used alongside text and images: 40%
 * Very small info messages: No restriction

I'm beginning to lean more towards a dynamic width for header messages since they should be clear of other elements in the article. ~60-80% sounds good to me. Inline messages are trickier since they could have a 235px infobox on one side and a dynamic-width TOC on the other. A dynamic width is no good since it counts the entire article width. I suggest we keep message templates from the TOC area and set the width to 500px, this allows them to still fit beside infoboxes at 1024x768 resolution. Duskey ( talk ) 01:09, August 1, 2010 (UTC)

Image(s)
I think we should add one image or icon to all messages. It'll help users identify messages more quickly and adds a level of customization to the wiki. Images should be kept small though as not to draw too much attention to themselves, the user came to the page to look at the content. Images should also, whereever possible, be from The Sims, which keep the messages unique to this wiki. The exception to this should probably be warnings, which often notify of stuff not related to the sims. We shouldn't plaster the message in images of course, which distracts more than it informs. Duskey ( talk )( blog ) 08:47, July 14, 2010 (UTC)

Using icons from the game would be best, in cases where that's not possible, we should look to Wikipedia for inspiration and use simple icons. Duskey ( talk ) 00:58, August 1, 2010 (UTC)

Contributions
This is where we post, experiment and discuss the future base template. Any contributions should be under a Heading 3 (===) with your username. Please add some initial comments from yourself as to why you think your contribution is good and how it fulfills the goal of this project. If you're going to post additional contributions in different varieties or as response to feedback, please mark these under a Heading 4, so contributions are listed by User and then varieties. If you have any comments for other contributions, please add them and don't forget to sign your posts. You are fully allowed to copy others contributions, edit them and post them as your own contributions. It's all CC-BY-SA licensing.

I'm hoping for this to be a constructive debate where we can come as close to the goal of this project as possible. Duskey ( talk )( blog ) 03:07, July 12, 2010 (UTC)

The 'Duskey' template has been chosen, yay! Duskey ( talk ) 00:57, August 1, 2010 (UTC)

Duskey

 * Example

Appearance Practicality Notes
 * Reasons why I like it
 * Easy on the eye: It is slim with smooth edges which makes it appear more plesant than standard brightly colored messages and square edges.
 * The image has a 1:1 size ratio and is set at a 32px width which is the double of a file icon in older Windows versions. This also promotes being easy on the eye.
 * Uses the wikipedia standard of a very light grey background color (#EEEEEE) which helps users to identify this as a wiki message.
 * Uses small text so it can easily be dismissed by users who are already aware of the notification.
 * Has a dynamic 60% width to accomodate most user screen resolutions.
 * The image and the color of the border states the nature of the warning even for users who have not read the text.
 * Retains individuality to The Sims Wiki by using an icon from the sims games and by using a unique shaped and colored border, which is different than standard wiki format.
 * The seperation of the image, the text and the boldness of the title, caused by the table, helps the user to quickly identify the nature of the message.
 * The light background color can hide some residual pixels from turning an image with a colored background into a gif or png with a transparent background.
 * The relatively small (32px) width of the image helps not to distort ingame icons from the sims games, which can sometimes be hard to find in bigger resolutions.
 * Easy customizeable features include the color of the border & background, the image and the title of the message, making this an easy-to-use template for a standardized collection of messages.
 * My intent is that the background color should be kept at the very light grey #EEEEEE unless it's specifically an important warning or fits very nicely with the theme of the page.


 * More examples

-- Patrick (LostInRiverview) (talk)(blog) 16:41, July 14, 2010 (UTC)
 * Questions and Comments
 * I like the style - however I have a couple questions.
 * Will the decreased font size make it more difficult for some users to read (either because of screen resolution or because of vision issues)?
 * Will the universal template be too difficult for inexperienced users to use correctly?


 * I'm using a 16:9 1920x1080 resolution and the is still readable. I do have a huge screen though and I see your point. Perhaps should be kept to minor additional notes in messages, such as 'see also' or a url to a site.
 * About difficulty in implementing. My idea was that we just decide on the look here. The template won't be some 1-template-wonder. It'll be split up in multiple templates, each with their own image and text. The woohoo example above would be one template. The fair use another. Putting them on a page wouuldn't require more than a woohoo or fair use for instance. It is only when a new template is created it gets abit tricky, but still very doable even by template beginners. Source code for the woohoo one is


 * Again I must point out that these message templates won't refer back to some all powerful master template, they are just similar in appearance, but have different names and functions. This gives us a high level of customizeability aswell. Duskey ( talk )( blog ) 12:45, July 15, 2010 (UTC)


 * Updated licensing examples

Feedback appreciated. Duskey ( talk ) 17:06, July 20, 2010 (UTC)