harness-book-best-practice

To export Honkit books to PDF, apply the shared tooling from tools/book-kit to run Pandoc and XeLaTeX, ensuring source assets remain separate from generated outputs. This workflow enforces consistent release metadata and proper build cleanup.

Fixing TOC issues in Honkit requires applying TOC stability best practices during editing and restructuring. Use the shared book-kit tooling to enforce naming conventions and maintain consistent navigation structure across book1-claude-code and book2-comparing.

Keeping source assets separate from generated HTML exports involves using shared tooling under tools/book-kit. This documentation workflow enforces build cleanup and consistent release metadata management to prevent drift between source files and print HTML outputs.

Pandoc and XeLaTeX PDF export works with Honkit navigation when applying shared book best-practice workflows. The tools/book-kit ensures TOC stability and proper build cleanup, maintaining consistent book structure throughout the export process.

Honkit book builds fail after restructuring due to TOC instability and naming convention drift. Apply the book best-practice workflow to align process, tooling, and metadata, preventing structural inconsistencies across book1-claude-code and book2-comparing.

Yes, tools/book-kit provides shared tooling required before editing Harness books. This prerequisite environment setup ensures consistent book structure, proper HTML and PDF export workflows, and release discipline across both book repositories.