What this methodology covers
DocuCraftBox combines automated service checks with non-sensitive Markdown acceptance samples and visual DOCX review. The goal is to verify document structure, file handling, and readable output without using customer documents as test material.
Test samples and syntax groups
| Sample group | What it checks |
|---|---|
| Full acceptance sample | H1-H6, paragraphs, emphasis, lists, task lists, quotes, tables, images, code, footnotes, formulas, Mermaid, captions, citations, and bilingual content. |
| Professional document sample | Front matter, callouts, report blocks, KPI, timeline, risk matrix, SWOT, API, commands, configuration, file trees, page structure, and approval content. |
| Math sample | Inline and display math, matrices, cases, aligned equations, arrays, integrals, limits, sums, products, labels, captions, references, and mixed Chinese-English prose. |
| Complex structure sample | Pandoc-native table forms, nested structures, headings, code variants, and document-layout controls that need more than plain-text conversion. |
Validation process
- Run automated checks for service health, job creation and status, downloads, file limits, ZIP safety, isolated storage, cleanup, template rendering, formulas, diagrams, and error handling.
- Convert the non-sensitive acceptance fixtures with each of the four Word templates.
- Inspect the generated DOCX for editable structure, readable tables, captions, formulas, diagram proportions, code treatment, and avoidable blank pages.
- Record material user-visible changes and limitations in the product changelog before describing them as current behavior.
Primary references used during review
Implementation and compatibility checks refer to the Pandoc User's Guide, Mermaid documentation, and Microsoft Word help where a product claim depends on external behavior.
Compatibility and limits
Representative output is inspected in WPS Office Desktop. DOCX files are designed for Microsoft Word-compatible editors, but fonts, pagination, long formulas, wide or nested tables, remote images, and advanced Mermaid syntax can differ by editor and operating system. Delivery documents should always be checked in the editor used by the recipient.