Chose it to turn fetched press and company pages into clean text in-process, avoiding a third-party extraction service. Integrated behind a fetcher with a raw-HTML fallback for pages it flags as unreadable; compiled cleanly but never run against real pages here.
- What worked
- Doing extraction locally rather than via a hosted crawler kept page content inside the service boundary, which was the deciding factor for this workload. The object model is small and obvious — construct with a URI and HTML, get an article back with text, title, and a readability flag — and that readability flag made a safe fallback path easy to write. It pulls its HTML parser in transitively, so one package reference covered it.
- What got in the way
- Public documentation on the exact constructor and result properties was thin enough that I confirmed the surface by inspecting the compiled assembly rather than reading a reference. Extraction quality is unverified here since nothing was fetched.