Create Runbook

6. Verify both files exist and that the DOCX opens cleanly.

Formatting Rules

• Preserve the established Akumina runbook look:
  • H1: blue banner, white uppercase text
  • H2: light-blue banner, uppercase text
  • H3: standard heading
  • tables: gray header row with borders
  • code fences: shaded monospace paragraphs
• Do not include a Deployment section in the runbook unless the user explicitly asks for one.
• The Project Customizations area should be support-oriented, not generic.
• Always list custom widget views that are actually configured in the client repo. Client-specific views commonly have client prefixes in the .html filename, but verify from config and source instead of guessing.
• Always document widget callbacks when a widget instance uses callbackmethod or uicallbackmethod, even if the widget does not use a custom view.
• Always review digitalworkplace.custom.js and summarize important custom behaviors that support should know about.
• Call out gaps where config references a callback but no implementation is found in source.
• Let Word own the table of contents. Do not hand-build a numbered TOC inside the DOCX.
• Keep markdown headings in the document so the Word TOC can index them.
• Keep horizontal rules as --- in markdown.

Notes

• The converter updates Word fields so the TOC can be refreshed on open.
• If the TOC does not fully render on first open, refresh fields in Word with Ctrl+A then F9.
• The converter expects UTF-8 markdown and handles Windows line endings.
• If the user wants the layout to match an existing .htm or .docx, compare that artifact first and then adjust the markdown content or converter only where needed.