Check out Grant Acedrex, our featured variant for April, 2024.

Enter Your Reply

The Comment You're Replying To
🕸Fergus Duniho wrote on Mon, Aug 20, 2018 05:15 PM UTC:

Having started on this, it seems to me that things would go more easily if all internal links were relative links. But having part of the site in a separate subdomain makes this impossible. Links between the main site and the subdomain have to be full links, and full links have to either HTTP or HTTPS. Relative links have the benefit of conforming to whatever the page being viewed is.

I looked into this further this morning, and the pages I read argued that putting everything on one domain is better for SEO. A subdomain is treated like a separate site, and it does not inherit the authority of the main site. Given that the main site and the subdomain are interrelated, sharing links and images, and that the main site has a good amount of authority that I would like the play part of the site to benefit from, I think it would be a good idea to replace the subdomain with a subdirectory. The subdomain is already physically located in a subdirectory, and 301 redirects could be used to direct subdomain links to the subdirectory.

Once that is done, I could make all internal links relative. This would get rid of the HTTPS links I started to add yesterday. And when all links are relative, it would be a lot easier to convert the whole site to HTTPS at once.


Edit Form
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.
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.