About: The Sims Wiki:Project Message template standardization/Manual of style   Sponge Permalink

An Entity of Type : owl:Thing, within Data Space : 134.155.108.49:8890 associated with source dataset(s)

In addition to The Sims Wiki:Manual of Style, message templates should follow these style guidelines. Keep appearance small. Using scaled-down images, borders of only a few pixels, limited width settings and the 'small' code on text. No one likes looking at huge clunky boxes. Smaller message templates also make them easier to ignore for regular users. Keep information and text short. Use as few words as possible while still communicating the full message without room for common misunderstandings. Use links to other pages to clarify meaning if neccesary. Avoid bright colors. Except on borders if they are kept small. Powerful colors can be good for framing message templates. While powerful colors are not so easy on the eye if used as backgrounds or if used extensively. Simplic

AttributesValues
rdfs:label
  • The Sims Wiki:Project Message template standardization/Manual of style
rdfs:comment
  • In addition to The Sims Wiki:Manual of Style, message templates should follow these style guidelines. Keep appearance small. Using scaled-down images, borders of only a few pixels, limited width settings and the 'small' code on text. No one likes looking at huge clunky boxes. Smaller message templates also make them easier to ignore for regular users. Keep information and text short. Use as few words as possible while still communicating the full message without room for common misunderstandings. Use links to other pages to clarify meaning if neccesary. Avoid bright colors. Except on borders if they are kept small. Powerful colors can be good for framing message templates. While powerful colors are not so easy on the eye if used as backgrounds or if used extensively. Simplic
dbkwik:sims/proper...iPageUsesTemplate
abstract
  • In addition to The Sims Wiki:Manual of Style, message templates should follow these style guidelines. Keep appearance small. Using scaled-down images, borders of only a few pixels, limited width settings and the 'small' code on text. No one likes looking at huge clunky boxes. Smaller message templates also make them easier to ignore for regular users. Keep information and text short. Use as few words as possible while still communicating the full message without room for common misunderstandings. Use links to other pages to clarify meaning if neccesary. Avoid bright colors. Except on borders if they are kept small. Powerful colors can be good for framing message templates. While powerful colors are not so easy on the eye if used as backgrounds or if used extensively. Simplicity Limit the template to as few components as possible. A standard 'image, title, text' format is preferred. Keep practicality in mind. It's no good if a message template suddenly breaks or looks awkward when irregular images are used. It needs to be compatible with all varieties of images and arrangements of text eg. bullet point lists. Ensure customizeability. When coding a message template, make sure it can be customized. Images changes, colors switched and the layout of the template altered if need be. Mind code complexity Make sure that the code is not too cluttered in order for other users to quickly gain insight into the template. Naming Avoid abbreviations and numbers when naming a message template. Make it easy and logical to find. Compatibility Using code that is compatible with standard browsers (IE, Firefox, Chrome, Opera) is preferred. Eg. three-digit hex codes (#EEE) does not show up in Opera.
Alternative Linked Data Views: ODE     Raw Data in: CXML | CSV | RDF ( N-Triples N3/Turtle JSON XML ) | OData ( Atom JSON ) | Microdata ( JSON HTML) | JSON-LD    About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data] Valid XHTML + RDFa
OpenLink Virtuoso version 07.20.3217, on Linux (x86_64-pc-linux-gnu), Standard Edition
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2012 OpenLink Software