The Chess Variant Pages

Enter Your Reply

The Comment You're Replying To
John Lawson wrote on 2002-04-05 UTC
I fall between Peter and David here.  When I write a comment, I don't
really plan it.  Something in the page, or another comment sets me off, and
I just start writing.  If it leads somewhere not completely germaine to the
page being commented on, so be it.

BUT, the result is that discussions that are potentially interesting or
inspiring get buried attached to pages that effectively conceal them from
later browsers.  (Look at the recent discussion attached to the
'Archoniclastic Chess' page.)

To do the thing properly, comments should be limited to the variant they
are attached to, and any flight of fancy should be moved to the discussion
group.  I think this is against human nature (at least mine) and I would
probably never make 50% of those posts.  Furthermore, the discussion group
posting may be cryptic outside of context of the variant page that inspired

On the other side, the number of people 'misusing' the comment system are
relatively small.  It would be a huge waste of time and resources to build
a parallel discussion system for a handful of 'chatterers'.  Also, the
public discussion board has a better possibility of attracting random

Maybe a compromise is possible.  Let me note here that I am no programmer,
and I have no idea how difficult any particular idea would be to implement.
 An idea that seems simple to me might be to allow the writer of an
extended comment to select a small set of keywords ('Ruddigore',
'double-move') which the comment system could also search for.

Better ideas?

Edit Form

Comment on the page General Comments Page

Quick Markdown Guide

By default, new comments may be entered as Markdown, simple markup syntax designed to be readable and not look like markup. Comments stored as Markdown will be converted to HTML by Parsedown before displaying them. This follows the Github Flavored Markdown Spec with support for Markdown Extra. For a good overview of Markdown in general, check out the Markdown Guide. Here is a quick comparison of some commonly used Markdown with the rendered result:

Top level header: <H1>

Block quote

Second paragraph in block quote

First Paragraph of response. Italics, bold, and bold italics.

Second Paragraph after blank line. Here is some HTML code mixed in with the Markdown, and here is the same <U>HTML code</U> enclosed by backticks.

Secondary Header: <H2>

  • Unordered list item
  • Second unordered list item
  • New unordered list
    • Nested list item

Third Level header <H3>

  1. An ordered list item.
  2. A second ordered list item with the same number.
  3. A third ordered list item.

Alt text for a graphic image

A definition list
A list of terms, each with one or more definitions following it.
An HTML construct using the tags <DL>, <DT> and <DD>.
A term
Its definition after a colon.
A second definition.
A third definition.
Another term following a blank line
The definition of that term.