# Public user help The guide covers CodeNomad with OpenCode V2. Assume readers already know OpenCode: document CodeNomad's controls, workflow differences and state/scope boundaries instead of teaching agents, prompts, Git or MCP. Keep pages focused and link to the official V2 docs for native configuration details. ## Sources and navigation - `docs/help/site.json`: the ten app locales and the ordered section/page list. Section ids are `start`, `workflows`, `opencode-setup`, `remote-access`, `customize`, `extensions`, `desktop`, `help`. The approved 28 pages each appear once; `index` comes first, then `download`, which the header **Download** link (`download.label`) opens on every page. The `help` section ends with `support` (bug reports and source builds) and `sponsor` (**Support CodeNomad**: why and how to fund development). - `docs/help//.md`: one H1 supplies the title and navigation label. Locales are `en`, `fr`, `de`, `es`, `he`, `ja`, `ne`, `ru`, `tr`, `zh-Hans`. - `docs/help/i18n/.json`: translated site chrome, section labels, release strings, download-button and funding labels. Keep the same non-empty keys in every language. Page titles belong in Markdown, not here. - `docs/help/help.css`: square, responsive chrome, light/dark palettes and logical properties for Hebrew RTL. Never import application styles/runtime. Every H2/H3 (and deeper heading, if used) needs an explicit ASCII kebab-case id: ```md ## Answer requests {#answer-requests} ### Permissions {#permissions} [Another page](permissions.md#answer-requests) [This page](#permissions) ![Workspace](../../screenshots/workspace-0.20.png) ``` The builder strips the suffix and assigns the id. Do not translate or reorder ids: every translated page must have exactly the English ordered (level, id) list. The single H1 is the page title, without an explicit id; an H1 `{#id}` is an error, never silently discarded. Link to an H2 section instead. Ids are unique within a page; `content`, `help-query` and `help-results` are reserved for site chrome. Avoid raw HTML headings or images: Markdown supplies the metadata needed for validation. Inter-page Markdown links become same-locale HTML links with their anchors intact. HTTPS links stay unchanged. Relative repository-reference links outside the guide become GitHub links; relative images (whose real path must stay inside the repository) are copied once into shared `assets/media/`, not fetched from remote hosts. Use paths relative to the source page, including the locale directory. ## Release links and generated blocks `docs/help/downloads.json` (untranslated, read from this repository even with `--content`) lists the stable release assets in display order, Tauri first: each entry has `id`, `platform` (`windows`/`macos`/`linux`), `host` (`tauri`/`electron`), `arch` (`x64`/`arm64`) and an asset-name `template` with one `{version}` (the tag without its `v`). Templates must match the real asset names of a published release. `[label](release:)` links to that asset. With release data the link is the exact download URL followed by ``, decimal megabytes formatted for the page locale; without release data (local and pull-request builds) every release link opens `releases/latest` without a size. An id missing from `downloads.json` is an `unknown-release-asset` problem. A directive is a top-level paragraph containing only `{{name}}`; the builder replaces it with generated HTML that has no headings and never becomes the meta description. `{{release}}` renders a `release-line` paragraph from the `release.published` chrome string (version and a long UTC date for the page locale) or, without release data, `release.unavailable` linked to the latest release. `{{download-button}}` is allowed only on `download.md` (elsewhere `misplaced-directive`) and makes that page load `help-download.js` (see below). It renders a hidden `div.download-primary` holding one hidden `data-download-os` block per target (`windows`, `macos`, `linux`, `mobile`), each with its final `a.download-main` label and href: the Tauri Windows x64, macOS arm64 and Linux x64 assets from `downloads.json` with a detail line and size, a secondary Intel Mac link (macOS x64), and `mobile.html` for phones and tablets. Without release data the desktop targets open `releases/latest`. Labels are the `download.*` chrome strings; search excerpts omit the hidden block. `{{tour-video}}` is allowed only on `index.md` and renders `figure.tour`: a silent `