At the very bottom of every page stand two things that come from two different plugins and are meant to look like one.
Out of the box
The Footer plugin writes a “Created with Quartz” line with the year, and under it the links its options name — four here: Quartz itself, QuartzControl and the two plugins this template uses (Layout Box and multilanguage). Nothing about it is styled; the links inherit whatever the body text gives them.
In this template
- A hairline separates the footer from the text, in the same colour and the same width as every other rule on the page.
- Everything is set muted and smaller: the footer is apparatus, not content.
- The links are not underlined until they are hovered — unlike in the body text, where the underline is compulsory. Here they stand in a row of their own; that they are links is what the row says.
- Every link has padding above and below. They are small and often the last thing anyone tries to hit on a smartphone.
- The row of links wraps rather than overflowing.
The second half is a layout box
The line below it — site name, language and the current page’s path — does not come from the footer
plugin. It is one of the seven instances of the Layout Box plugin, placed at position: footer. It
is there as the example for the three placeholders {{siteTitle}}, {{locale}} and {{slug}}; see
The instances.
That the two read as one block is the reason they are handled separately: the footer plugin brings its own spacing and the layout box brings its own — and left alone, two different gaps would sit between the two lines.
The footer lies over the right column
A
position: stickygrid item does not stay inside its area in Chromium: on long pages the right column ran into the footer. Proved that the grid changes nothing about it — an explicitgrid-rowmoved the overlap by one pixel. It is solved through painting order instead: the footer gets a layer and a ground of its own and thereby covers what reaches in from above.
Comments would be the third part
The Comments plugin (giscus) is switched off in this template — it needs a GitHub repository that an importing site does not have. The styling travels along anyway — in the lower half of the
site-footersection inlayout.scss— so that switching it on in QuartzControl does not drop an unstyled frame under every page.
Which variables apply here
These 11 variables are read by the section site-footer in layout.scss. They can be changed in QuartzControl under Styles → Variables — without a line of CSS.
| Variable | Value | also applies to |
|---|---|---|
--gray | #5F5F5F · dark #A1A1A1 | 22 other components |
--secondary | #1463A3 · dark #699DC3 | 19 other components |
--tpl-radius-md | 8px | 17 other components |
--tpl-rule | var(--lightgray) = #DDDDDD | 19 other components |
--tpl-rule-width | 1px | 25 other components |
--tpl-space-2xs | 0.25rem | 16 other components |
--tpl-space-md | 1rem | 18 other components |
--tpl-space-xl | 2.5rem | 5 other components |
--tpl-space-xs | 0.5rem | 20 other components |
--tpl-text-sm | 0.875rem | 20 other components |
--tpl-underline-offset | 0.18em | 6 other components |
This table is generated: it is read out of the stylesheets rather than kept by hand.