September 17, 2026

Editorial tags land on submissions

Submissions on Curvenote SCMS now carry editorial tags: a site-scoped catalog admins curate, addable and removable from the submission details page, visible on the listing, filterable from the toolbar, and carried through to the published work payload for downstream tools. Rendering picks up a broad quality pass across every Curvenote-Reader-powered site — configurable site fonts, correct Google Scholar dates, no more layout shifts when an inline banner loads, and a hydration fix that stops React re-rendering the whole page on visits to articles with a mid-paragraph blockquote.

Curvenote SCMS¶

Editorial tags on submissions. Each site now curates its own list of editorial tags and puts them to work on submissions. Admins manage the catalog on a new admin-only Tags page — list, create, rename the display label, delete — with deletes cascading to remove the tag from any submissions it was on. From the submission details page, adding or removing a tag is a one-click popover; the picker creates the tag in the catalog on first use if it is not there yet, and the timeline records one entry per real change so double-clicks and second tabs no longer noise up the log. The submissions listing gains a dedicated tags row per submission with an “Add tags” empty state that opens the picker inline, and the site-admin listing toolbar picks up a Tags multi-select chip so editors can filter the queue by tag combinations. The site’s tag catalog is returned on the site endpoint, and each published work carries the tags actually applied to it — a narrow public shape (name and label) with no internal ids leaking, so the tags travel to downstream tools without exposing catalog identity.

Multi-step create-form flows unblocked. Multi-step work-creation forms are no longer bounced back to step one when the second step lives on a different path. The work create option that names the form’s paths now accepts a list of path fragments, so the draft-only work layout guard recognizes every step of a multi-step flow as part of the same form.

Curvenote Sites¶

Editorial tags on submissions. The tags experience described above is fully wired on Curvenote Sites’ site-admin routes: the submissions listing shows an editorial-tags row per submission, the listing toolbar carries the new Tags multi-select filter chip, and the submission details page exposes the “Add tags” popover — anchored to the tag row (not to any individual chip) so it always opens in the same place, whichever chip or the add control opened it. The site-admin sidebar gains a Tags entry that goes to the new catalog page.

Curvenote Reader¶

Configurable site fonts. A site can now choose its own fonts on its theme configuration, self-hosted or served from Google, across four semantic slots — headings, body text, small text (footnotes, captions, backmatter, outline), and code. UI chrome deliberately stays on the system stack, which is Roboto on Android and ChromeOS and costs no bytes, so the interface never feels foreign against a site’s chosen fonts. Font styles are rendered server-side so there is no flash of the fallback family, self-hosted files are preloaded, Google slots are fetched from a single combined stylesheet link, and metric overrides (size-adjust, ascent-override) keep the page from reflowing when a face swaps in.

Correct Google Scholar dates on every article. Every article now emits a correctly formatted Google Scholar publication date. A bug had built citation_publication_date and citation_online_date from the wrong parts of the date — the day-of-week where the day-of-month should have been.

The article bar and the meta tags now agree with what publishing resolved. The article bar was reading the manifest’s raw date and doi — whatever the author typed into the content, which publishing never updates — while the same page’s <meta> tags and analytics resolved the platform’s published date and DOI. A revised article could show one date to readers and another to crawlers and citation tools. The bar now takes the same resolved values the metadata already uses, so the visible date and DOI and their machine-readable counterparts stay in step.

A hardening pass on link colors. Link colors in the Reader now come from --link and --link-hover design tokens instead of hard-coded blue utilities, so a site can restyle them from one place. The default is body-text color (black on white, white on black) with a 60%-opacity underline that goes full strength on hover — a visible change on cross-references, citations, footnote markers, the figure “Show more” toggle, and the link cards, all of which used to read as bright blue and now read as plain text until a site opts into a color. Prose links inside article text follow the token too — the typography plugin had been ignoring it.

Lightbox captions readable on the dark backdrop. Citations and links inside a lightbox caption used to inherit the near-black link color of a light-mode page and vanish into the black backdrop. The lightbox dialog now carries dark-mode tokens end to end, so every caption’s citations and links read against the dark background regardless of the page theme.

Wider margins on centered article layouts. At large viewports, content_grid: center now leaves more room either side of the body column, on every Curvenote-Reader-powered site rather than only Curvenote Theme sites.

openRxiv Labs — Curvenote Reader¶

Readers on openRxiv Labs pick up every Curvenote Reader change above — correct Google Scholar dates, the hydration fix for mid-paragraph blocks, reserved space for inline banners, working breakout containers, readable lightbox captions on dark backdrops, and wider centered page margins.

Curvenote Theme¶

A directly customizable site footer. The shared journal footer can now be adjusted from a site’s own theme configuration, for smaller overrides that do not need the footer hidden altogether.