Check out Chess with Different Armies, our featured variant for July, 2024.

Preferred HTML form of contributions

If you send a text to this website, it helps a lot if it is already written in HTML. If you want to help even more, you can use the following guidelines for the form of the HTML code. (Comments on the contents can be found on another page.)

If you feel that following the guidelines is too difficult for you, don't worry: read below.

The advantage of following the guidelines is that all pages of this website have the same look, and also look reasonably good on any kind of browser or machine. Not everybody uses the same browser as you!

Post Your Own Game

If you are member who has already contributed pages to this site, you can post your own material. Just go to the following link: Post your own game, and follow the directions.


This site loads three carefully chosen web fonts. These include one serif font, one sans serif font, and one monospace font. The current choices are Literata, Noto Sans, and Courier Prime. Each is associated with particular HTML elements. By default, it will use the serif font for body text, the sans serif font for headings, buttons, and some navigation items, and the monospace font for pre-formatted text. For the sake of maintaining a consistent look across pages, you should not select individual fonts.


HTML Don'ts

Use the standard template

All webpages have the same kind of yellowish-white background color, and the same colors for links (followed, unfollowed), and black text. It depends on the depth in the directory/folder hierarchy what kind of header you can use:

HTML Entities and UTF-8

The .htaccess file on this site is set up to indicate that each page should be displayed in the UTF-8 character encoding. UTF-8 is a variable-width form of Unicode that stores all the ASCII characters as single bytes, using multiple bytes only for other characters. Since the pages on our site are primarily written in ASCII, using UTF-8 will not appreciably expand the size of our files, yet it still gives us the advantage of a single character encoding that includes a wide variety of the world's languages, as well as various symbols. Although you might be comfortable with Latin-1 (ISO 8859-1), we need to consistently use the same character encoding for all our pages. Telling the browser what character encoding to expect is what makes all our pages readable on any browser. Since UTF-8 combines compactness with the variety of Unicode, and since all ASCII documents are already UTF-8 documents by virtue of ASCII being a subset of UTF-8, UTF-8 is the best character encoding for us to use.

Nevertheless, you should favor HTML entities over UTF-8 characters. The reason for this is that HTML entities will display properly no matter what character encoding a browser uses. As an example, here are two umlauted e's, one displayed in UTF-8 and one displayed as an HTML entity. Use your browser to change the character encoding, and the HTML entity will still look correct, but the other one will not.

UTF-8HTML Entity

Here are some useful resources I found on the web:

While it is not critical to convert pages from UTF-8 to HTML Entities, it is important to convert pages using Latin-1 (a.k.a. ISO 8859-1) or Windows-1252.

A common error

If you want to use a < or > in the text, like in the following mathematical sentence: if 5x < 10, then 2 > x, then you cannot just use a < or > in your html-code: while some browsers (depending on version) display this as you wanted, others expect a html-command and may display the webpage not as wanted (e.g., skip some part of the text.) The correct way to resolve this is to use the code &lt; for the < sign, and the code &gt; for the > sign.

This is too hard for me.

If you feel that it is too hard for you to follow all these guidelines: Don't worry - we'll manage. Just send in your text in another form, and we'll try to edit it. Some deviations of these form-rules are acceptable, and depending on time, we'll try to resolve some others. In case of doubt, just contact us.

Originally written by Hans Bodlaender; Revised by Fergus Duniho
WWW page created: April 24, 2000.