odoo-doc-illustration

Role

Front door for the documentation that ships inside Odoo modules (doc/index.rst, the App Store page static/description/index.html), illustrated with live screenshots. A product documentation site kept in its own repository is odoo-doc-site. It settles the tree the docs land in, plans the instances a multi-module package needs, provisions each instance, launches per module ONE odoo-doc-writer (MODE: full, the user guide) and then ONE odoo-marketer (MODE: landing, the App Store page, from the writer's catalog, facts and captures), verifies the references, commits per module and releases what it leased.

Out of Scope

• Record a video or GIF walkthrough -> odoo-demo-recording
• Rate or audit a rendered screen (aesthetics, a11y, Lighthouse) -> odoo-ui-review
• Pure text draft (blog post, marketing copy, no capture) -> odoo-content-draft
• Spec or outline before any code or doc exists -> odoo-solution-design
• Compare two builds for visual drift -> odoo-visual-regression
• Write or fix frontend source -> odoo-coding
• The catalog, role map or walkthrough text alone, no browser -> odoo-doc-feature-map
• A product documentation site (its own repository, a branch per series) -> odoo-doc-site

Inputs

TARGET: one module (name or path), or local, worktree:<abs-path>, repo:<abs-path> for a multi-module package. Optional axes, per module or for the run: DOC LAYER (userguide, appstore, both; default both), DOC SCOPE (screenshot-doc default, full-guide), CAPTURE MODE (screens default, scenarios), BROWSER MODE (headless default), LANGUAGES, TARGET MARKET, and CHANGE: the path of a change file (<ISOLATE_DIR>/docs/change-<slug>.md, one line per added, changed or removed user-visible feature with its module and UI label) or whole; a module's feature list is the lines of that file that name the module. CHANGE is the one update input: with a feature list the writer rewrites only the affected sections and recaptures only the affected screens; whole documents the module again from scratch; absent, a module that already ships docs is left alone (doc:false, step 3). A caller may supply per-module FEATURE CATALOG, ROLE MAP, WALKTHROUGH, MARKETING COPY, BUYER PROFILE; each is forwarded and never rebuilt. INSTANCE_HANDLE (optional): a demo build the caller already holds; when its addons_path covers doc_root, demo is true and languages_loaded holds every resolved language, the run captures on it and provisions nothing (${CLAUDE_PLUGIN_ROOT}/snippets/docs-after-change.md § One capture instance).