Used for standards-compliant HTML parsing in the extraction pipeline: parsed directly from the response stream so character-set sniffing follows the spec rather than guessing an encoding up front, then walked the DOM for a fallback text path and for publication-date signals in structured data, meta tags and time elements. Compiled against the documented surface without a single API mismatch.
- What worked
- Parsing from a stream rather than a decoded string is the right default and the library exposes it plainly — it solved the encoding problem for me instead of making me pre-detect a charset. The object model is close enough to browser DOM conventions that I could write traversal code without consulting docs repeatedly. Shipped documentation files were adequate to confirm the entry points I needed.
- What got in the way
- Nothing blocking in this task. Only exercised at compile time — no live pages were parsed.