OfficeIMO Capability Catalog
Edit on GitHubNavigate the complete managed document platform by workflow, component family, generated API, and validation evidence.
OfficeIMO is a modular document platform, not a single basic DOCX helper. The repository currently contains 89 production libraries, adapters, renderers, and tools, backed by 29 test projects, 12 benchmark projects, and dedicated validation applications.
Choose the right depth
| Need | Start here |
|---|---|
| Build or edit a document | Use the Word, Excel, PowerPoint, PDF, email, OneNote, OpenDocument, Markdown, CSV, or Visio guide. |
| Move content between formats | Open the conversion map to choose the source package, destination adapter, and expected loss policy. |
| Normalize mixed documents | Start with Reader and add only the format adapters your application needs. |
| Automate from scripts | Use PSWriteOffice and its manifest-derived 464-command catalog. |
| Inspect exact members | Move from a conceptual guide into one of the generated API references. |
| Evaluate deployment constraints | Use the validation and AOT pages for executable evidence and known boundaries. |
Component families
- Extraction and ingestion: 28 focused components
- Formats and interoperability: 11 focused components
- Foundations and integrations: 11 focused components
- Google Workspace: 4 focused components
- Office documents: 17 focused components
- Publishing and conversion: 15 focused components
- Rendering surfaces: 3 focused components
The complete package and component index is generated from project metadata, so descriptions, source links, API availability, and test-reference counts stay aligned with the repository.
Evidence, not blanket promises
Support is stated at the scenario level. A package can be cross-platform while a renderer, OCR provider, browser runtime, authentication provider, or NativeAOT path has additional constraints. The validation guide separates source compatibility, automated tests, published artifacts, and executed deployment paths.