|
|
|
|
|
Guidelines for writing scout pages for this siteFollow the requirements from my disclaimer page. There are different levels of required conformance. For example just because your document contains a link to a page doesn't put any requirement for that linked-to page. Links to pages which don't follow the guide lines are ok. On the other side if you ask me to store a page at my site, then I might or might not play zsar. When playing zsar, nothing I dislike will make it to the server. Also nothing which uses more bytes then I'm allowed to, and, nothing which grossly displeases my council. I want documents to follow the standards for html. Attributes which only work with non-standard document viewers will get my opposition. I do not want to give support to companies providing non-standard features. On the other side, if the feature is not violating the standard for commercial reasons but uses experimental or rearch stuff, I'm game to try. I hate blinking text. Besides, the standard does not (yet?) support blinking text. Blinking text keeps blinking when the reader wants to aim his attention to a different window. Avoid fancy backgrounds. It is not standard, the slowest thing to display on high speed workstations, and foremost: it frequently makes text hard to read. Don't scroll text in the message window; the message window is there for a purpose and scrolling text makes messages unreadable. Frames are almost ever a nuisance; they seem to be very difficult to use right. Pictures: Use pictures sparingly. Or, use pictures from links which warn the users. Many of the people interested in scouting stuff might have slow modems for connecting to the internet. Links: Pages without links look boring. But since somewhere on
the web there should be real information, it sometimes make sense
not to have links.
Web guidelines from scouting sources
Other sources of web writing wisdom
|
