Check out Modern Chess, our featured variant for January, 2025.

Enter Your Reply

The Comment You're Replying To
🕸Fergus Duniho wrote on Tue, Jul 3, 2018 01:56 AM UTC:

Where there is an entry for the tag in tagDetails, it would be helpful to include the tagSentence after the name of the tag in this list. This will help people better understand what each tag means, and it will let us know which tags still need descriptions.

I would like to avoid cryptic tags. These tags are meant to be read by people, not simply by machines. Generally, the tag alone should be enough to inform someone what it means. The "shape:board" tag is cryptic. Every board has a shape. Something like "Unusual Board Shape" might work better. Phrases would be less cryptic than using a colon between two different words. Also, I'll be using a colon in the pseudo UserIDs for tag pages. This is partially in the works, though more needs to be done.

I have changed the collations in the tagDetails table to utf8_general_ci, and I have extended the size of the tags to 64 to match the size in the Tags table.

 


Edit Form

Comment on the page Tags Listing

Conduct Guidelines
This is a Chess variants website, not a general forum.
Please limit your comments to Chess variants or the operation of this site.
Keep this website a safe space for Chess variant hobbyists of all stripes.
Because we want people to feel comfortable here no matter what their political or religious beliefs might be, we ask you to avoid discussing politics, religion, or other controversial subjects here. No matter how passionately you feel about any of these subjects, just take it someplace else.
Avoid Inflammatory Comments
If you are feeling anger, keep it to yourself until you calm down. Avoid insulting, blaming, or attacking someone you are angry with. Focus criticisms on ideas rather than people, and understand that criticisms of your ideas are not personal attacks and do not justify an inflammatory response.
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.
Here is some preformatted text.
  This line begins with some indentation.
    This begins with even more indentation.
And this line has no indentation.

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.