Step 1: specify the parameters of your variant below:

Board dimensions
files:          ranks:
holdings type: (where captured pieces go)
Piece graphics(to constuct image filenames)
directory with piece images:(Must end with '/' !!!)
graphics format: (image filename extension)
white prefix:put on image filename to dis-
black prefix:  tinguish white and black pieces
square size:(at least 3 larger than images!)
Board colorsfor checkering(make equal for non-checkered)
light / dark squares: (white & greyish)
Promotion(not very important)
promotion zone depth:(in ranks)
nr of promoting piece types:(usually just the first: the Pawn)
promotion choice:(prefix with * if taken from holdings)
promotion offset (Shogi):(added to piece type on promotion)

Step 2: When satisfied with the settings above, press the button below.

  This should make a diagram of an empty board appear.

Diagram design page

Make your own interactive diagram!

This page can assist you in creating the HTML code that in collaboration with the betza.js JavaScript will create an interactive Chess diagram. If you follow the 5 easy steps, in the end it will display a piece of text that you can copy-paste into the body of your own HTML page. In order to work, however, the header of that page will have to link to the betza.js file (and, less importantly, the betza.css style file). This requires the two lines

<link rel=StyleSheet href="../betza.css" type="text/css">
<script type="text/javascript" src="../betza.js"></script>

to be incorporated in the header. And of course the two betza.* files to be present in the mentioned location relative to the HTML page.

To view this page your web browser had to download those files, but it did not save them on the disk, and discards them after you are done with this page. To download them for saving, you can use these two links: JavaScript and style file. Of course you will also need to set up a directory for the pieces.

Some hints - There is unfortunately no way to go back to an earlier design stage; the only way is to refresh the page and restart from scratch. When during design of a very large variant you discover that you made a mistake in an earlier piece (e.g. user a wrong ID, or messed up the Betza move specifier), it might be faster to just complete the design process, and then edit the HTML code that comes out afterwards to correct the error. Everything you entered will be quite easy to recognize from the HTML code, and with a regular text editor like NotePad you should have no problem to locate the line for the erroneously specified piece, and correct the name, ID or move for it.