docs: document versioned workspaces, tool scoping, and missing commands - #6
Merged
Merged
Conversation
The named-workspace mechanism (`version:` / `up --version`) was documented in the README but absent from the website docs: quickstart only described fresh timestamped workspaces, the command reference lacked `tarjan pull` and `tarjan upgrade` entirely, and `--version` / `--ai` were missing from the `up` flag list. Bring the website up to date (quickstart, commands, configuration — including a new "Workspaces & versions" section), and state explicitly in both README and website that parallel version workspaces coexist on disk but cannot RUN simultaneously, since services publish fixed host ports that every workspace shares — the existing already-running guard only covers re-`up` of the same workspace. Also document the service-scoped tool checks (`requires[].services`, `tarjan doctor <service>`) in the README tool reference, the configuration page, and the changelog.
The landing page hardcodes dark-canvas colors (text-white/60, border-white/10, ...) while the root layout pins theme to dark. But the docs pages expose a theme toggle, and next-themes persists the choice — switch to light in the docs and the landing page loses its .dark class, leaving white text on a white background. Make the page properly theme-aware: neutral dark-on-light colors by default with the original white-on-dark palette under dark:, keep the terminal/config panes dark in both themes, and drive the dark: variant from the theme class (@custom-variant) instead of prefers-color-scheme so it follows the toggle. Drop the hardcoded dark class on <html> — the provider owns it. Verified both themes render legibly (landing + docs) via a static build and Playwright screenshots.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Brings the docs in line with the current code, centred on how
tarjan upmanages versioned workspaces — plus a light-mode legibility fix for the landing page:tarjan pullandtarjan upgradeentirely, and--version/--ai/ positionalup [service...]were absent from the flag list. Quickstart, commands, and configuration are now up to date, including a new "Workspaces & versions" section on the configuration page.--version feat-a/--version feat-b) coexist on disk but cannot run simultaneously — services publish fixed host ports shared by every workspace, and the already-running preflight only guards re-upof the same workspace. Documented the down-then-up switch flow (fast thanks to clone/setup reuse).requires[].servicesfield andtarjan doctor <service...>scoping are now covered in the README tool reference, the configuration page, andCHANGELOG.md.text-white/60,border-white/10, …) while the layout pinned the theme to dark — but the docs' theme toggle persists via next-themes, so switching to light left white text on a white background. The page is now theme-aware (neutral colors by default, original palette underdark:, terminal/config panes stay dark in both themes), with thedark:variant driven by the theme class instead ofprefers-color-scheme. Verified both themes (landing + docs) with a static build and Playwright screenshots.gofmtfix ininternal/config/config_test.gosomake check's fmt gate passes.Type of change
fix)feat)refactor/chore)docs)ci/build)Checklist
make checkpasses locally (fmt, vet, lint, race tests + coverage gate).CHANGELOG.mdunder## [Unreleased](if user-visible).Notes for reviewers
/docs/configuration#workspaces--versions).@custom-variant darkinglobals.cssmakes Tailwind'sdark:utilities class-driven, matching how the fumadocs theme provider toggles<html class="dark">.🤖 Generated with Claude Code
https://claude.ai/code/session_01EAYGh5BQL2UZgbP2jMLYPs