Check out Symmetric Chess, our featured variant for March, 2024.

Enter Your Reply

The Comment You're Replying To
🕸Fergus Duniho wrote on Thu, Jun 10, 2021 02:06 PM UTC in reply to Greg Strong from 12:57 AM:

I think the H2 text size is very, very large. I'd like to see that scaled down a bit, but things are looking better.

Is that because you are used to it being smaller, or because there are specific pages on which the H2 heading is too long?

I looked into the default sizes of H1-H6, and I learned that by default, H4 is the same size as the body text, and H5 and H6 are even smaller. This doesn't make sense to me. Headings should always be larger than the body text. Additionally, higher level headings should be larger than lower level headings, and size differences between headings of the same style should be large enough to tell them apart. Bearing these considerations in mind results in the headings all being larger than they are by default. This doesn't leave a lot of room for adjusting the size of H2, which is already closer to the size of H3 than to the size of H1.

Additionally, text is appearing larger on Chrome than on Firefox. I normally develop on Firefox, but if you're using Chrome, you will see larger fonts than I normally do. When I inspect the page h1-h6-test.html, which has no CSS or styling, it gives me the same values for the font sizes even though it appears larger on Chrome. In inspecting, Xiangqi, I get the same values for the style elements, though I cannot get Firefox to give me the size in pixels. I need to look into why text is larger on Chrome and see if there is some way to standardize the size in different browsers on the same computer. You may inspect these pages yourself with Developer Tools on Chrome or Web Developer Tools on Firefox.

There are pages on which I plan to use a different style or a lower heading level. These would include link pages, Zillions pages, and Game Courier preset pages, which normally have fewer sections and less text than other pages. I'll work on that later.


Edit Form

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.