an hour ago
A really solid looking editor! Just a heads up on small, mobile screen sizes: the UI elements of the top row overlap unusably, the rest of the UI seems usable just quite zoomed in and I really had to pan around a lot to do anything. Fundamentally a solid and usable UI, I’d recommend a little more polish on smaller screen sizes. Good work!
an hour ago
Noted, and thanks for the feedback! It's on our roadmap to better support mobile experience
4 hours ago
Hi! I was looking at `@eigenpal/docx-editor-agents`—would that be a viable option for fetching the content of Word docs in agentic workflows? I'm currently using Pandoc to extract an MD version, but I'm not sure how true to the actual document that is (e.g., with comments). Thanks!
2 hours ago
Excellent work
13 hours ago
I’ve built something similar but for PDFs. Know the pain too well. Best wishes!
10 hours ago
Interesting! Would love to check that out as well, have you released it?
9 hours ago
It was an internal enterprise tool that will never be public.
6 hours ago
Thank you!
12 hours ago
Holy shit, this is exactly what I needed for a major client. The track changes specifically, and being able to do it from Typescript. You have no idea how happy you just made me.
Edit: Did you just make this repo public? Last week I was scouring the internet for something like this and couldn't find it.
6 hours ago
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 ?
10 hours ago
This looks amazing!
6 hours ago
Thanks!
12 hours ago
This looks really impressive. How hard was it to implement this in typescript?
6 hours ago
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.