English
About this handbook

This handbook belongs to the template Example for QuartzControl. It explains the template and, at the same time, shows everything it can do.

The text here comes from a Markdown file, not from the configuration.

Title and date

The title

Out of the box Quartz sets the page heading at the same size as an h1 in the text.

In this template it is larger and more tightly tracked (letter-spacing: -0.02em), and its lines are balanced rather than filled (text-wrap: balance): a title is skimmed, not read line by line, and one that wraps after four words looks like an oversight.

On narrow screens it drops one step — at 390 px the full size would be half the screen.

Date and reading time

Out of the box a line in the text colour.

In this template muted, smaller, and the parts are separated by a middle dot that is paler still than the text. The values are the content; the punctuation steps back.

Where the date comes from

From the frontmatter, otherwise from the file system — in that order, set on the Created modified date plugin.

A symlink takes Quartz's git dates away

Out of the box the order is frontmatter → git → filesystem, and git would be the better source: a commit date survives a copy, a restore and a fresh checkout, a file’s modification time does not. It is missing here all the same. This site’s content lives in an Obsidian vault that content/ points to as a symlink; the plugin follows the symlink and does find the vault’s git, but then computes the file’s path against the project directory — and so asks for a path that leads back out of the vault. Every lookup fails. That is why 250 of the 254 pages produced “isn’t yet tracked by git, dates will be inaccurate” in the build log; the only silent ones were the four pages carrying a lastmod in their frontmatter, which never ask git in the first place. The date came from the file system the whole time, so git in the list was nothing but noise. The bug is reported; once it is fixed, git belongs back in front.

The format follows the page, not the site

Quartz formats dates site-wide by configuration.locale, which is German here. The multilingual plugin’s localizeDates re-formats every <time> element in the browser in the language of the page, so an English page shows an English date.

Which variables apply here

These 7 variables are read by the section meta-title-and-date in content.scss. They can be changed in QuartzControl under Styles → Variables — without a line of CSS.

VariableValuealso applies to
--gray#5F5F5F · dark #A1A1A122 other components
--tpl-rule-strongvar(--gray) = #5F5F5F8 other components
--tpl-space-2xs0.25rem16 other components
--tpl-space-xs0.5rem20 other components
--tpl-text-2xl1.75rem6.4 – Variables
--tpl-text-3xl2.25rem6.4 – Variables, Error page
--tpl-text-sm0.875rem20 other components

This table is generated: it is read out of the stylesheets rather than kept by hand.

Read on

This page belongs to Example — the example template for QuartzControl. An overview of every area is on the English home page.

On a narrow screen the navigation is collapsed at the top.