v1.0.0 InDesign panel 1.0.0 · this build What changed

Install — about ten minutes

  1. Fonts first: install Open Sans (Regular / Italic / Bold / Bold Italic / Semibold / Light), Montserrat (Medium / SemiBold / Bold) and Minion Pro (Regular). The panel audits fonts after every convert and reports anything missing.
  2. Download the plugin with the button above, then double-click the .ccx. The Creative Cloud desktop app installs it — accept the “unverified developer” prompt (expected for internal plugins).
  3. Restart InDesign (2026 / v21 or newer) → open Plugins → Dinno Executor. The plugin loads with InDesign automatically from now on.
  4. Bring a book in: from Word, press Typeset and then Start on the panel’s Transfer tab — the Official Book guide walks through it. Don’t work in InDesign during the run. The Convert wizard (below) still works, but Convert is deprecated in 0.8.0 and removed in 1.1.
  5. Export to PDF: use Compatibility = Acrobat 7 (PDF 1.6), Standard = None, Fast Web View off. The output is transparency-free, so any preset works — including High Quality Print.
Enterprise note: if Creative Cloud is managed and blocks the install, IT can allow non-Adobe plugins in the Admin Console, or mass-install silently with UnifiedPluginInstallerAgent.exe /install Dinno-Executor-<version>.ccx.
Alternative install via UXP Developer Tool (fallback)
  1. Install UXP Developer Tool from the Creative Cloud app.
  2. Copy the executor-uxp-vue/dist folder from the repository to the machine.
  3. UDT → Add Plugin → select manifest.json → with InDesign running, Load.
  4. Note: with this method UDT must stay running while you use the panel, and after pulling a new build use Unload + Load (a plain Reload does not refresh the manifest/icon).

Using the panel — the convert wizard

Top to bottom (with Split on, a Chapters step appears in between). Every run also writes a live log file to disk (Settings → Diagnostics), which survives a crash.

The convert wizard is deprecated in 0.8.0 and removed in 1.1. It still works in 0.8.0 and says so at the top of its tab. Use the Word transfer (Typeset in Word, Start on the Transfer tab) or Send from the Word pane; a Learner Workbook or Trainer Guide comes from the PowerPoint pane.
1

Document

Pick the Word .docx — the manuscript exactly as authored, any size (large files upload in chunks automatically).

2

Options

Convert into the open document = template mode: respect your open template's preset styles.

Split into chapters = one .indd per chapter (front matter combined or separate), saved to your output folder as NN-title.indd.

Create InDesign Book (.indb) — collect the chapters into one Book: book-wide contents, one page-number stream, synchronised styles.

Figures folder (optional) — link the design team's original vector figures instead of the embedded PNGs. Naming convention, formats and worked examples: How to use → Link the original .ai figures.

3

Chapters (Split only)

The exact documents the split will create, before anything runs. Check only what you need — a single chapter converts in ~20 seconds, perfect for proofing a change. All / None shortcuts included; file numbering matches the full split.

4

Run

A per-chapter checklist (pending → converting → saved) with an overall progress bar, plus the live stages: parse → figures → apply → layout → done. Hands off InDesign while it runs. Green = clean; amber = finished with skipped ops (check the log); red = aborted.

5

Done

Single mode leaves the styled document open; Split mode reports “N chapters saved to …” and, with Book on, opens the assembled .indb. “Convert another” resets the wizard — and if a run errors, “Reset & start over” recovers without reloading the panel.

Best practice for full-book converts: start from a freshly opened InDesign. Repeated full-book runs in one long InDesign session can stall mid-run (the panel warns from the second convert onwards) — a fresh session per full convert is fast and reliable; short single-chapter previews are unaffected.
Update available banner: when a newer panel is published, an amber strip appears at the very top of the panel. Tap it to download the new .ccx, then reinstall (double-click) and restart InDesign.

Troubleshooting

SymptomWhat it means / what to do
“Not reachable — check the target” The panel can’t see the engine. Settings → Engine: pick Azure (default) or your custom URL, then watch for “Connected · build …”. The engine’s own status: /healthz.
Fonts flagged after a convert The font audit lists exactly which faces were substituted. Install the listed fonts (see Install step 1) and convert again.
Run seems stuck The console logs every operation — note the last line (it names the op) and report it with the log file. Don’t click inside InDesign during a run; the composer needs the app to itself.
Convert failed with an error The message is shown on the Run step. Use “Reset & start over”, try again, and if it repeats, send the log + the Word file via the form.
“SAVE ERROR” during Split A chapter file could not be written. Choose an output folder you can write to (not a synced/locked location) and re-run; the log names the exact file that failed.
Panel icon looks generic (not the Dinno mascot) Icons are read at install/load time. Installed .ccx: reinstall the current version. UDT: Unload + Load the plugin (Reload alone doesn’t refresh the manifest).
Where is my log? Settings → Diagnostics shows the live log file path (written as you work) and a “Save a copy…” button for attaching to a report.

FAQ

Does the Word file need cleaning up first?

No. Dinno is built for messy, real manuscripts — inconsistent styles, floating objects, huge files. Convert it as-is; the engine normalises what it needs.

Which InDesign versions are supported?

InDesign 2026 (v21) or newer, Windows or macOS, with the Creative Cloud desktop app for the one-click install.

Where does my document go?

To the PeopleCert-internal Dinno engine (Azure, EU region) for parsing, and back to your InDesign as a layout plan. Nothing leaves PeopleCert infrastructure.

Can I work in InDesign while it converts?

No — the panel drives InDesign’s composer during the run. Grab a coffee; the full ITIL book takes about five minutes, of which three to six are drawing and vary with InDesign’s own state.

Single document or Split — which should I use?

Split is recommended for full books: per-chapter files are smaller, faster and more stable, and the InDesign Book assembly builds on them — the .indb is written next to the chapter files, with ordered contents and book-wide page numbering (roman front matter, then one arabic stream across chapters). Single-document mode remains the default for quick checks and small documents.

What stays manual on purpose?

Front-matter composition (cover, welcome, acknowledgements), chapter-opener art placement, and final polish (margin-icon nudges, flagged table cells). Dinno places the materials; those calls are yours.

Still stuck?

Send the run log, the Word file and a screenshot — that’s everything we need to reproduce and fix it.

Report a problem