Repository navigation
Vault Publisher 0.1.4
The notes you mark with pinned now lead the left panel, and you decide what order they come in.
Start here, beside the tree
"Start here" was reachable only by opening the search field, and it vanished
the moment you typed. The most editorial thing on a site sat behind the one
control a reader touches when they already know where they are going.
It now sits above the file tree, stays put while the tree scrolls, and is
gone from the drop-down, which keeps recency alone. Five show at once and the
rest sit behind a Show more that expands in place, so pin as many as you
like. The block is bounded, so thirty pins scroll inside their own section
rather than pushing the tree off the panel.
An order you choose
pinned now carries where a note goes as well as whether it is listed:
pinned: 1 # leads
pinned: 2 # second
pinned: 1.5 # between those two, without renumbering eitherNumbered notes lead in their numbers, then everything left on true follows
in title order. The order used to be whatever the file sort returned, which
is alphabetical by vault path, so the folder a note sat in decided whether
it led and a note called "Begin here" in archive/ came last. One sort now
runs for the panel and the front page, which read titles and paths
respectively before.
Light or dark, as the site opens
Appearance, Opens in decides what a first-time visitor sees: their own
system setting, which is the default and what every site did before, or light
or dark whatever their machine says. It is written into each page at build
time, so it holds before the first paint and with JavaScript switched off,
and a reader who works the toggle still wins from then on.
A password screen that says something useful
The locked-site screen explained that the page was ciphertext and that the
key was derived locally. All true, and all jargon to most of the people who
will ever see it. It now says what a reader who is stuck can act on, which is
that the person who sent the link has the password.
It also tells you when it is working. Deriving the key is 600,000 iterations,
close to a second on a laptop and several on a phone, and the whole of the
feedback used to be a dimmed button. The action and the failure no longer
share a colour either, and the screen opens in the same mode as the site
behind it.
Two things that were quietly wrong
- Pasting a token left the Publish button dead. The block at the top of
the settings panel reported what was still missing and was then left alone,
while everything it reads on is edited below it. Closing the tab and
opening it again fixed it. It now keeps up on its own. - A finished publish could report itself as failed. Turning on GitHub
Pages is the last call of a publish, after everything is committed, and it
can answer 500 having done the work. The publisher now reads the state back
before giving up, so a publish that worked says so.