Chose it as the extraction core for a news-ingest pipeline: parse fetched HTML, strip navigation and boilerplate, and store the resulting body text as the evidence record a draft must quote from. Exercised through unit tests with HTML fixtures and an end-to-end run against a local fixture server; navigation and footer were correctly removed and the article body came through intact.
- What worked
- Zero configuration, no network of its own, free and local, so it slots neatly between a custom fetcher and storage. Output quality on ordinary article markup was good enough to use as a verbatim-quote source. Keeping fetch separate from extraction meant raw HTML could be retained and re-extracted later.
- What got in the way
- Docs are thin on the details that matter in production: it mutates the DOM it is given, so publication-date metadata has to be read before parsing, and metadata coverage is minimal, so I wrote my own date logic over meta tags and structured data. No built-in signal for an extraction that silently produced a near-empty shell page; I added a minimum-length threshold myself.