The control moves to the header

A page that enables a feed publishes its title, feed address, and whether email subscription is offered. The header reads that and renders the subscribe control beside search, the theme toggle, and the account menu. The dialog opens from there with the same options it always carried, the feed address and the email form when the page enables it.

The control leaves the changelog page heading, so the heading is now the title alone. On narrow viewports the control keeps its icon and drops its label to hold the header on one line.

Any page type can offer the control by publishing the same feed state, so it is no longer tied to the changelog renderer.

Published pairing

A guarded bundle resolves each file against the pairing written when the bundle was published, matching on the bundle and the file it ends with, and falls back to the bundle path only when no pairing exists. A guarded module whose stored address differs from its source path now loads instead of returning nothing.

Harness context

A svelte system's harness reads its context into a local before the state rune uses it, so the rune sits in a declaration initializer where svelte expects it. Stories that mounted through a svelte harness now load on the first try instead of erroring during setup.

Back to top

The button slides in once you are far enough down a page, and pressing it returns you to the top.

It watched for scrolling in a place the page never scrolls, so it stayed hidden no matter how far down a reader went, and pressing it moved nothing. It now watches the column the page actually scrolls in and returns that column to the top.

Closing the subscribe dialog

The subscribe dialog closes from an icon button in its header rather than a small text label. Pressing escape still closes it.

The hash follows the reader

Scrolling through a page updates the address bar to the heading in view, so copying the URL at any point shares the exact section on screen.

The page shell fills the viewport and scrolls inside its own column rather than scrolling the document, so the listener watching for scrolling never heard anything and the hash only changed when a reader clicked an entry in the right rail. It now listens where the scrolling actually happens.

This reaches every page that carries a table of contents: doc pages, changelog collections, roadmaps, and the API reference.

Icons for issue types

A roadmap sidebar row carries a glyph for its kind rather than the kind spelled out. A milestone shows a flag, an epic shows a box, a feature shows a sparkle, and a bug shows an alert. The row reads as an icon followed by the issue title.

Deeper control trees

The walk from a schema to its controls expands nested members twelve levels deep. An array of groups holding lanes holding entries holding a style block holding colors now resolves to real controls the whole way down, where it stopped at an opaque leaf before.

A member past the bound still becomes a raw editor and the warning names it, so a warning on a member that carries its own properties is the bound speaking rather than the schema.

Chunk cycle guard

Every build checks the emitted bundle for chunks that import each other, for the site and for each component system. A cycle fails the build and prints each cycle as a chunk path with the source module behind every chunk.

The failure this catches only appears in a deployed static site. Dev serves modules unbundled and works, while the built site throws on whichever cyclic chunk evaluates first and every page loading either chunk renders nothing. nimpress lint builds, so the guard runs there and in continuous integration with no configuration.

The fix is always on the shared side: a registry or menu that statically imports a component loads it through a dynamic import instead.

Icons on sidebar rows

An icon on a sidebar block or on a story definition accepts three kinds of value.

1. Literal text or ascii art, rendered verbatim in the mono font.

2. Inline <svg> markup, rendered as markup.

3. A path ending in .svg, resolved against the declaring file or against the content root when it starts with a slash, and inlined at build time.

An unreadable path warns and drops the icon. Icons render from sidebar blocks and story definitions only.

The root page in the sidebar

The root index joins the sidebar through its own sidebar block placed at sidebar.path, so the site landing page becomes a clickable top level item rather than an entry with no row.

Page rail

The right rail switches to container queries on the page shell and the mirror column beside it is gone. The rail holds its place as the shell resizes instead of reacting to the viewport.

Story rows

A story decorates its own sidebar row through a sidebar object carrying name, icon, and style. The link stays keyed on the resolved story name, so only the label changes and the URL does not.

An underscore in a story file name reads as a space when the name falls back to the file name, so a file named for a case renders a readable row.

Dev rebuilds

Page bodies and page component modules invalidate with their registered ids, so editing a story file rebuilds the component data behind the page it belongs to.

The paths block

1. paths.out is the build root and defaults to dist.

2. paths.cache is the single cache root and defaults to node_modules/.nimpress. The docs build cache, the harness cache for each component system, and the lint verification build all layer beneath it.

3. paths.export is the folder the export command fills for the docs pipeline and defaults to .nimpress.

4. paths.modules and paths.guarded are both the folders under the build root and the URL segments they are served at, defaulting to _components and _guarded.

Breaking change

Breaking. outDir folds into paths.out. A config still setting outDir needs it moved.

Lint leaves the repo root

The lint verification build writes under the cache root rather than the repo root, and cleans up after itself when the run is interrupted.

Warnings stop repeating

Schema coaching warnings collect into one registry keyed by position, deduplicate, and flush once, grouped per component with the source file and a best effort line and a single suggested fix. They print after the dev banner, after each rebuild, and at the end of an update, an import, and a lint.

The automatic schema upsert in dev is guarded by a hash of the source content, so writing a schema no longer retriggers the pass that wrote it. The rebuild loop and the warning flood it produced are gone.

The schema file

Each component page carries one schema.json or schema.yml beside it. The workshop controls, the validation, and the mock selection all read from that file.

1. nimpress modules update upserts source changes into the schema: new props, slots, and events are added and changed type shapes refresh on existing members.

2. Authored fields are never overwritten. A member that disappears from the source stays in the file and is flagged so the author decides.

3. In nimpress dev the upsert runs on every component change.

4. data.schema in page frontmatter layers over the file for a small curation that does not warrant editing it.

Coaching warnings

Every pass reports what a reader of the library would miss: props without a description, opaque types, and schema members with no counterpart in the source. The warnings print without failing the run.

Sizing belongs to the story

A story that needs a width or a height owns it in its own markup or in a harness component it wraps itself in. The workshop frame centers whatever the story mounts and scrolls it when it is larger than the frame.

Control surface

1. Enum options render as chips, and a long list collapses to one line that expands on hover.

2. A default button at the panel header resets every control to its schema default, and one at the events header resets every handler to the logging stub.

3. Filling a value by mock excludes options already present, so a second click lands on a fresh one.

4. Number mocks respect the minimum and maximum the schema declares.

5. The canvas pans on a middle press or a modifier click, and a modifier double click recenters it.

Decoration only pages

An index file carrying frontmatter and no body decorates its sidebar group without becoming a page of its own. Such a file needs only sidebar.name, and content lint judges a page by its body so the file passes.

Page visibility

Breaking. A page declares where it appears through visibility, which takes visible, hidden, or dev-only. The boolean flag that carried this before is gone from the schema.

1. visible is the default and needs no declaration.

2. hidden takes the page out of the sidebar, out of search, and out of the build.

3. dev-only keeps the page in nimpress dev and leaves it out of the built bundle. Its sidebar row carries a red dot so the author can see at a glance that the page does not ship.

The frontmatter schema accepts unknown fields without failing, so a page still carrying the boolean builds and publishes as a normal public page. Any page meant to stay unpublished has to be moved to visibility to keep its intent.

Composable harness

A component system declares its frame instead of relying on discovery. ComponentHarness, ComponentStory, ComponentHarnessEffects, and ComponentHarnessOverlay import from the harness package and arrange freely, and a system that declares no harness gets the default composition.

1. The harness field on a system points at the component wrapping every story.

2. The harness field on a single story wraps that one story inside the system harness.

3. The setup module bootstraps the app, installing plugins and providers on every created app before mount.

Sidebar groups from frontmatter

A sidebar block nests a page under a named group without changing its URL. A declared group sits beside the physical folders rather than inside one. On a folder index the block decorates that folder's own row.

Guarded bundles

Guarded pages build into their own folders keyed by the bundle the guard function names, and the build writes the map of page to bundle alongside them.

Workshop panels

The props panel and the console panel each dock to the bottom or the right of the workshop and split the slot when they share it. The console streams everything the component frame logs, including window errors, and takes typed expressions that evaluate inside the frame.

1. Events render as control rows with an always visible editor holding a real handler function.

2. A handler compiles in the frame and counts its firings on the row.

Page rail

The right rail lives in a grid gutter on the page shell, so the content column stays centered and the rail stops clipping at narrow widths.

Diagrams

Mermaid moves into the dependencies of the package, so a consumer resolves it through nimpress rather than installing it separately.

Stories sit beside their page

A story file placed next to a component page belongs to that page. There is no separate registry and no path to configure.

Sidebar groups carry decoration

The sidebar block in frontmatter takes an icon and a style alongside its name, so a group row can carry a glyph and inline styling without changing any URL.

Hash links

Following a link that carries a hash lands on the target heading rather than at the top of the page.

Stories that run

A story file exports a definition through vueStory or svelteStory. A story carrying props seeds the workshop controls as before. A story carrying render returns a mount definition that the harness runs verbatim, so markup, fixture data, and composition all live in the story itself.

Importing a library

nimpress modules import walks a component source tree, reads existing story files for their groups and named cases, seeds a schema per component from its types, and writes a default story for any component that has none.

1. --match narrows the walk to component names matching a pattern.

2. --select picks components interactively.

3. Re-running the import upserts and never clears authored content.

Workshop screen

The workshop shell fills the viewport. The document itself does not scroll; the sidebar, the panels, and the component frame each scroll on their own.

Component workshop

A folder holding a component page and its stories becomes a live page. The component mounts inside an iframe harness, the controls drive its props, and the stories list beside it in the sidebar.

1. type: component on a markdown page names the system and the component through data.system and data.component.

2. The modules array in the config declares one system per component library, with its framework, source root, package name, and harness port.

3. nimpress modules runs the workshop commands: a dev server per system, a static build, and a lint pass.

Release feeds

A changelog collection publishes an RSS feed. The page carries a subscribe control that hands the reader the feed URL, and a site wired to an auth endpoint offers an email subscription against the reader's account.

1. rss: true in frontmatter publishes the feed for that collection.

2. subscribe: true adds the email option beside the feed URL.

3. The subscribe config block names the endpoint and the app slug the subscription registers under.

Guarded pages

gate marks a page guarded. The build lifts every guarded page out of the public bundle into its own folder and writes a map of what went where, so the public site never carries the bytes of a page the viewer may not read.

1. nimpress guard is the command that reads and reports that map.

2. The auth.guard function in the config decides which bundle a gate value maps to.

Authentication

The auth config gains callback hooks and a backend for frontend mode, so a site can run its session through a server path rather than the browser alone.

Docs pipeline

A repo keeps its docs in a .nimpress folder and publishes them on a version tag rather than on a branch push. One source can now map into several target folders in the docs site.

A site runs from a nimpress.config file with sensible defaults. The nimpress command serves, builds, previews, and scaffolds with init, so a consumer needs little beyond that file and its markdown.

Assets and styling

Shared assets live in a root folder served at a configurable base, while images next to a page travel with it. A site wide stylesheet named in css and a per page stylesheet sharing a markdown file name override the theme.

Content linting

nimpress lint validates the frontmatter of every page, and a build fails on an invalid page, so a broken page cannot ship.

Docs across repos

A repo keeps its docs in a .nimpress folder. On change it notifies the docs site, which mirrors the folder into its tree under a mapped path, lints, and publishes.