A lot of existing approaches convert .docx into HTML and lose document semantics along the way. Our editor parses OOXML directly and uses its own rendering+layout engine to produce paged documents with html/css. Edits round-trip back to .docx, so you’re always editing the document, not its representation.
The core rendering engine is framework agnostic, with React and Vue ui adapters on top.
It’s Apache 2.0. Happy to answer questions.
Edit: Did you just make this repo public? Last week I was scouring the internet for something like this and couldn't find it.
The repo has actually been public for ~3 months, but we only launched the project homepage https://www.docx-editor.dev recently, so search engines are still catching up.
> I was scouring the internet for something like this and couldn't find it.
Interested to hear how can we make it more discoverable? What keywords were you searching for ?
The OOXML spec gets you far but doesn't cover 100% of how Word renders things. Community feedback has helped a lot here, users attach docs (in gh issues) that break rendering, we can reproduce against Word, fix the engine, and keep tightening fidelity.