clean-jsdoc-theme

@clean-jsdoc-theme/aadesh

@clean-jsdoc-theme/aadesh is the CLI for clean-jsdoc-theme — localization is its first area. It does the disk-bound, process-orchestrating work that bhasha (the pure, browser-safe core) deliberately can't: spawning your JSDoc/TypeDoc pipeline, reading and writing the committable locale catalogs, and rendering one static site per locale.

Why the name? aadesh (आदेश) is Sanskrit/Hindi for command / instruction — fitting for the project's command-line interface.

The published binary is clean-jsdoc. The localization authoring verbs live under an i18n group; build stays top-level because it renders your site whether or not you use multiple locales (i18n is just one area of the CLI, and the top-level namespace is reserved for future groups). Run with no arguments for an interactive menu.

CODE
clean-jsdoc i18n extract    # sync the per-locale catalogs from your docs
clean-jsdoc i18n prompt     # (optional) emit an LLM translation prompt
clean-jsdoc i18n validate   # preflight the catalogs
clean-jsdoc build           # render one site per locale

If you just want to ship a single-language site you never need aadesh — the JSDoc/TypeDoc entry points build that directly. aadesh is the layer you add when you want multiple languages. The full walkthrough is in Localize your docs.

Where it sits

Locale is a build dimension, not a runtime toggle: each language is rendered to its own static output (the default locale unprefixed, the others under /<locale>), and the language switcher is navigation between them. aadesh owns that fan-out. It reads your locale config from the same jsdoc.json opts you already use (opts.locales + opts.defaultLocale) — there's no separate config file — and drives the real theme pipeline twice: once in extract mode to pull out translatable strings, and once per locale in build mode to stamp the translations back in.

The commands

  • extract — runs the pipeline in extract mode, collects every translatable string (UI chrome + API descriptions/summaries/example captions + parameter and return descriptions), and syncs them into one committable JSON per locale. Re-runs are a merge: new keys are added, source changes mark a key stale, and removed keys are soft-deleted (kept until --prune) so a rename never drops a translator's work. A no-change run is a zero git diff.
  • prompt — writes a ready-to-use LLM translation prompt file per locale (under clean-jsdoc-theme-artifacts/locales/prompts/, chunked for context limits) covering the new and stale keys only, with the exact return-JSON shape and instructions to preserve markdown / @link / code fences / {var} tokens. You paste each file into an LLM (or upload the .md); the directory is git-ignored and regenerated each run.
  • validate — preflights the catalogs: a coverage gap warns ("using the default"), a malformation (broken markdown-in-slot, a dropped {var} token, unknown keys) errors. Resilient by default; --strict escalates warnings to failures for CI.
  • build — template + filled catalogs → setu stamp → dwar render → one site per locale. Owns the cross-locale index that feeds the language switcher and the hreflang alternates.

Every prompt has a flag equivalent (--config, --dir, --prune, --strict, --locale, --chunk-size, --typedoc), so the CLI runs headless in CI and never blocks.

The artifacts

Catalogs live under clean-jsdoc-theme-artifacts/locales/, committed to your repo and edited by hand (or by your translation workflow). Each locale is two files:

CODE
clean-jsdoc-theme-artifacts/locales/
  en.json        # editable: _version + chrome.* / api.* translations
  en.meta.json   # auto-managed: source hashes + soft-deleted keys (don't touch)
  ja.json
  ja.meta.json

The editable file holds only what a translator changes; the staleness hashes and soft-deletes live in the sibling .meta.json so machine bookkeeping never clutters the file you review.

Prose localization

Beyond the keyed catalogs, free-form prose is localized by file, no extraction needed:

  • Home page — a sibling README.<locale>.md next to your configured README is rendered as that locale's home (falling back to the default README when absent).
  • Docs — a sibling docs.<locale>/ directory overlays your opts.docs per file: a translated page wins, a missing one falls back to the default doc.

Interactive mode

Run clean-jsdoc with no subcommand for a guided menu: a welcome banner, a command picker that shows each command's description, prompts for its options (defaults pre-filled), and an offer to save the equivalent command to your package.json scripts so you can re-run it with npm run <key>.

Read the source

Next