Skip to content

docs: make Nova click for new users - #4

Open
bioinformatist wants to merge 2 commits into
Yazelix:mainfrom
bioinformatist:docs/nova-stable-site-contract
Open

bioinformatist wants to merge 2 commits into
Yazelix:mainfrom
bioinformatist:docs/nova-stable-site-contract

Conversation

@bioinformatist

Copy link
Copy Markdown
Contributor

Oi Lucca!

Glad to say: Your part-time employee has finally clocked back in 😄

The part of this PR I care about most is a small mental model for people who have never used Zellij—or any terminal multiplexer—before:

A Nova session is like a browser window. Project tabs are the tabs inside that window. Panes are the tools working inside each project, and processes live inside those panes.

I think this makes the relationship between named sessions and project tabs click surprisingly quickly. A complete newcomer no longer has to understand Zellij first and Nova second; they can look at Nova as one coherent workspace and discover the underlying layers naturally. To me, that makes the product feel much more inviting.

Most of the other changes grew out of keeping that story consistent. The current site now:

  • describes Rio instead of Mars
  • the package and configuration docs match current Stable
  • the screenshots and clips have been recorded again from the same world the prose describes

The old Nova v1 article and its Mars-era media remain untouched as historical material. A new user should no longer learn one model from the words and see another one in the pixels.

Also: your automated recording setup is honestly brilliant. It is one of those ideas that looks obvious only after somebody else has done the hard thinking. I tightened it around pinned public sources, isolated state, deterministic cleanup, and separate source captures for the current site, but the underlying approach is yours and I learned a lot from it.

KUN has a CLI-driven playground too: https://kun.bigdick.live/playground/ . After working on the site this time, I am seriously considering borrowing more of the same recording philosophy there. Apparently I'm stealing 😃

I also took care of some less glamorous housekeeping: a reproducible Nix devShell, the pinned Playwright browser environment, typo checking, stronger public-contract tests, and a few small wording/rendering fixes.

Just like before: this is my interpretation of Nova, and it may not match every part of your original/current intent or design. Please feel completely free to push additional commits, rewrite anything, extract only the pieces you like, or close the PR altogether. I am not attached to the shape of the contribution. Any honest attempt that helps Yazelix become better is worth making! Thus no matter which parts eventually land or in what form.

What I checked locally

The full Astro build and typo checks pass, as do all 26 Playwright tests. I also inspected Home and Features at desktop and 320px widths, checked the current recordings and posters, verified that draft/public media copiesmatch, and confirmed that the frozen Nova v1 assets remain unchanged.

The Codex clip opens the real TUI and types a prompt without submitting it. Recording state is isolated, configured MCP servers/apps/plugins are disabled for that process, and no persistent user configuration is modified.

@vercel

vercel Bot commented Sep 1, 2026

Copy link
Copy Markdown

@bioinformatist is attempting to deploy a commit to the Lucca's projects Team on Vercel.

A member of the Team first needs to authorize it.

luccahuguet added a commit that referenced this pull request Sep 7, 2026
Update launch, package variants, and native configuration paths against Stable revision 16810b21ef76e98057707c3bb18068a04ba4a350. Keep the existing media and Kinestra recorder, and record the broader refresh deferral in Beads.

Adapted from the Stable documentation changes in PR #4.

Co-authored-by: Yu Sun <ysun@sctmes.com>
@luccahuguet

Copy link
Copy Markdown
Collaborator

hey yu sun! thanks for that. I corrected the stale informations based on your input

but the new media will have to wait nova's new flow to land on stable and main (and i'll likely have to record again)

luccahuguet added a commit that referenced this pull request Sep 7, 2026
Validate cached public origins and pinned commits before creating independent
run checkouts. Point Nova, Codex, and zoxide at those checkouts and use the
same Nova revision for the source tree and executable.

Add an offline source-isolation check covering cache reuse, contamination,
revision selection, and independence from other takes and the cache.

Implements kinestra-zlf; adapted from Yazelix/nova-site PR #4.

Co-authored-by: Yu Sun <ysun@sctmes.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants