Only pages from the content folder
A menu item that leads to another website is not a page and appears in no tree. Quartz’s footer
(links) or a layout box is there for that.
The words exist only in German and English
“Previous”, “Next”, “Overview”, “Home” and the names for screen readers come with the plugin in these
two languages; every other language gets English. Only title and ariaLabel can be changed, and the
plugin does not translate them (7.3).
Shared pages get the default language
Tag pages and folder pages shared by several languages belong to no language. There the navigation
shows the tree of quartz-multilanguage’s default language — even on the tag page of an English tag. If
every page lives in a language folder, the site’s locale decides instead
(8.3).
With the language in the frontmatter, only one language has a start page
The index.md in the root belongs to exactly one language. The other language’s tree has no start
page: showHome and showScopeRoot with scope: root show nothing there.
detection with frontmatter before folder
If you reorder detection in quartz-multilanguage that way, pages in a language folder that carry lang
in the frontmatter keep the folder in their path; the others lose it. The English tree then shows
docs twice: in the root and under en. With the default [folder, suffix, frontmatter] this does
not happen.
breakpoints does not apply to a single navigation
The stylesheet is one for all. Different values in different entries end up as two stylesheets on the site, both acting on every navigation (6.2).
stripNumericPrefix also hits titles from the frontmatter
Not only titles from file names but every title that starts with a number and -, _, . or a
space. “1.2 – Getting started” becomes “2 – Getting started”. Only navTitle stays untouched
(2.1).
columns.max has no effect
The option is accepted, but the grid follows the width only (4.3).
The jump menu needs JavaScript
select and mobile: select navigate through a script. Without JavaScript an option can be chosen,
but nothing happens (5.3).
No custom icons in the jump menu
An option of a <select> can only hold text (7.1).
One order per navigation, not per page
Sorting applies to an entry’s whole tree. A page cannot ask to sit somewhere else in one navigation than in another — unless the two navigations sort differently.
Hover only with a mouse
trigger: hover works on devices that report hover. On touch devices the click opens.
The mobile menu needs a clear path
It sits over the window with position: fixed. Inside an ancestor with transform, filter or a mask
it gets squashed or cut off (6.1).
exclusive depends on the browser
One folder per level through the name attribute of <details> is supported by current browsers. Older
ones leave several folders open — the navigation still works.
Memory depends on the ID
persistState stores under the id. Without a fixed id, every option change changes the ID and what
was remembered is gone (5.1). It is stored in the visitor’s
browser; another browser, a private window or cleared site data start from scratch.
Folders are remembered under their real path. With language folders, de/docs and en/docs are two
folders, and memory starts afresh after switching language; with language suffixes both languages share
one folder and with it what was open.