Skip to content

ROADMAP.md

Latest commit

 

History

History
38 lines (30 loc) · 2.28 KB

ROADMAP.md

File metadata and controls

38 lines (30 loc) · 2.28 KB

Project Roadmap

Role: Where we are going and status tracking of what is done, in progress, and planned.

This document tracks migration from Word JS API to pure OOXML and the core package extraction track.

Current Phase: Phase 2 (Feature Migration)

✅ Completed (Phase 1: Core Infrastructure)

  • Text Editing: Fully migrated to OOXML pipeline (applyRedlineToOxml).
  • Highlighting: Fully migrated to surgical engine.
  • List Generation: Fully migrated to OOXML pipeline.
  • Table Generation: Fully migrated to virtual grid pipeline.
  • Pure Formatting: Migrated to w:rPrChange surgical engine.
  • Checkpoint System: Uses whole-body OOXML storage.

In Progress (Phase 2: Feature Migration)

  • List Conversion: executeConvertHeadersToList() still uses Word List API for complex conversion.
  • Table Editing: executeEditTable() uses Word Table API for row/column insertion in existing tables.

In Progress (Phase 3: Final Decoupling and Repo Split)

  • Repository Split: AIWordPlugin now consumes external @ansonlai/docx-redline-js.
    • Add-in-specific bridge moved to src/taskpane/modules/docx-redline-js-integration/.
    • Browser demo and MCP service now import from package coordinates.
    • In-repo src/taskpane/modules/reconciliation/ source removed after migration.
  • Context Extraction: Replace Word.Paragraph.load() logic with pure OOXML parsing of the document body.
  • Comment Operations: Replace remaining host-only comment entrypoints with direct OOXML-first flows where applicable.
  • Navigation: Implement OOXML-based position tracking.
  • Search: Implement pure OOXML text search parser.

Planned (Phase 3+: Remaining Host-Decoupling Work)

  • Host Consumer Migration: complete downstream migration away from any legacy bridge-specific fallback surfaces.
  • Repository Separation: split word-addin, browser-demo, and mcp into independent repositories (core already extracted).

Long-Term Vision

  1. Zero Office.js Logic: All document manipulation happens via OOXML.
  2. CLI Utility: Ship the core engine as a standalone .docx repair/edit tool.
  3. Server-Side Integration: Use the engine in a Node.js backend to process large batches of legal documents.