Cameron wrote: > Below are some direct suggestions that I made, but are definitely open > to constructive comments: > * Screen shots: Should be done at a consistent screen resolution. AT > work we "unofficially" use 800 x 600 which seems to be quite common.
Perhaps 1024x768? This is quickly becoming the "standard" to code web pages for because most computers are set to this on install these days (at least that's my understanding). I don't know much that would need to be stretched/shrunk when printing to a page though. > * Resolution: I would say an absolute minimum of 150dpi, but more likely > use a 300dpi. Usually a higher the resolution will give you a better > quality image when it comes to print and 300 seems to be the standard > nowadays. Depends on the purpose. 300dpi makes NO difference when viewing the picture on the screen (other than the extra space/ram needed). Monitors typically only display 75 or 90 dpi only. This also may have an impact on screen captures. If the monitor will only do 90dpi, then what is the 300dpi doing that is any better? NOTE that this does not apply to generated images (aka Gimp/Photoshop, Inkscape, etc...) If printing, then no less than 300dpi is the recommended standard I've seen from the printers and/or print shops. > * Fonts: One or two common fonts that are preferably open source. > Usually you will have one for titles and one for text. Usually there is > never more than 3 or 4 as an absolute max. Liberation Fonts: http://en.wikipedia.org/wiki/Liberation_fonts (download link near the bottom). The selling point here is that a) it is free (as in speech), and b) it uses the same dimensions as common non-free fonts (aka Arial). So putting a document onto a system that doesn't have the Liberation fonts installed, *shouldn't* result in formatting issues due to font differences. > * Layout: Standardized layout with consistent margins, etc . to give the > same look and feel between different topics. Obviously some stuff may > not fit in the space provided so start with a base and adapt as necessary. Kin's sample tonight was generally approved by the group in attendance. Kin said he would make the file available to anyone who wanted to create on a cheat sheet themselves. > These are just a few ideas, but are by no means definitive. I would > welcome feedback on this as I am sure Kin would as well. I would highly > encourage everyone to get involved at whatever level you re comfortable. > You investment doesn;t have to be huge, but every little bit helps to > move things along. You don't to be an artist or a orgrammer or do > anything fancy if thas not your bag. Even if you are just interested in > writting content I am sure any help would be appreciated. Additional comments: - Are there any existing guidelines for cheat sheets available online? (I'm guessing not anything that is commonly accepted....). Failing that, are there any pertinent sub points that do have existing guidelines/standards? (like image resolution, fonts, etc.) - If anyone is tackling a different cheat sheet, I'd recommend doing a few minutes of search to see if your topic already has something available. This could be in the help files, man pages, or someones web site. If you DO find one, is it up to date? Can it be adapted? Is it under copyright? Is it good enough? If any of these is a "no", then there is room to improve or create a new version. There is nothing saying you can't create your own version anyways, but why re-create the wheel if something suitable exists? (If you do find something existing, then we should probably at least make the URL known...) - There was some talk about applying a license to these. The short of it is that it is generally understood that the files/efforts would likely be donated to CLUG (with proper credit to the author of course), who would then make these available under an open license (insert your favorite license here! - we got a little side tracked on this one tonight... ) Good discussion topic. Shawn _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
