OOXML Office
Every app in one workspace, with a shared file library, tabs, search and an assistant. Installs as an app and runs offline.
OOXML Office is a set of Office editors that run in the browser: Word, Excel, PowerPoint and Visio files, plus a team workspace. There are three ways in. Use the apps as they are, embed one editor in your own site, or build on the library underneath them.
Every app in one workspace, with a shared file library, tabs, search and an assistant. Installs as an app and runs offline.
Write and format documents with a ribbon, print layout, tracked changes and comments.
Workbooks with formulas, charts, conditional formats, sorting and filtering.
View, edit and present slide decks, and work on one deck together.
Open diagrams and flowcharts: pages, shapes, connectors and text.
Channels, chat, presence and calls on a server you run, with Office files in the conversation.
The <docx-editor> element. Install the package for your framework;
it brings the editor and the document model with it.
The <xlsx-editor> element, with the same six framework packages.
Rendering, editing, presenting and collaboration for React, Vue, Angular, Svelte and plain JavaScript.
The <visio-viewer> element: local-first, six framework packages.
The <teams-app> element, framework packages with raw hooks, and a
small reference server.
The ribbons, menus, dialogs and status bars every editor is built from, published as
ooxml-ui, themeable through one set of tokens.
Parse, edit, validate and write every Office format with no UI: documents, workbooks, decks and diagrams, charts, SmartArt, maths, encryption and collaboration.
One Model Context Protocol server for every format, so an agent can read, create and change files, plus the headless operations it runs on.
The sibling package reads .doc, .xls and .ppt and the compound-file container; the editors inline it, so legacy files open without an extra install.
One monorepo holds every package and app. The roadmap lists what each app still lacks against the Office applications and in which order it is planned.
Commit conventions, the checks that run before a push, and how a change becomes a release. Every package is versioned from its commits and published with provenance.
Discussions for questions and ideas, issues for bugs and requests. Everything is Apache-2.0.