Docx to markdown is a lossy conversion, so getting .docx back is possible but will lose most formatting details

In this case, I would imagine two scenarios

1. I have markdown, I want a docx version, that is equivalent to html rendering, markdown's whole point, almost certainly many options out there

2. I have docx, I want to make edits in markdown (because vim motions), need to sync those edits back. Ideally just some value swaps in the "DOM"

It may very well be the case that Office now supports Markdown natively. I seem to recall possibly seeing that. Google Workspace is as well iirc. One of the two already had support, the other was just releasing the first takes (back when I last looked )

Thanks! Our core product is a Word editor that you can embed in your React / Vue app. So we just repurposed the layout engine to be an accurate converter. You can see how our layout engine "sees" the document in the left tab of the demo.

I'm working on https://docx-editor.dev/, open-source, .docx editor library for building document apps.

Thanks for reporting! We do have perf tests for editing docs over 50 pages, but something in the demo doc must indeed be slowing edits down, this is not expected behaviour. Filed an issue https://github.com/eigenpal/docx-editor/issues/590

Noted, and thanks for the feedback! It's on our roadmap to better support mobile experience

Happy to hear that! :)

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 ?

I had been having claude/openAI do web search for typescript docx libraries.

Thanks!

Thank you!

Thanks! The hard here part is not typescript implementation but it's catching Word undocumented quirks.

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.

I'm working on https://docx-editor.dev/, the open-source, mit licensed word editor library.

We are building this because we such library it in our core business, and a lot of other engineers seem to need it too. We have contributors showing up with bug reports and fixes, and real interest from people building apps around .docx docs.

My previous show hn post (https://news.ycombinator.com/item?id=46947229) got a lot of skepticism because we're developing heavily with AI, but with active community feedback and proper ai oversight (mostly me), I'm super proud of what we have now.