The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
To what end?
I've always been one of those guys for whom IE "just works" well enough to never really have committed to any of the alternatives, but given that even some MS sites no longer work with it nowadays, even I now have Chrome/Firefox installed, and would be okay if CP forced me to switch to something else.
There, I just gave you permission to break IE compatibility. I hope you weren't waiting for my blessings...otherwise...sorry about your afternoon.
I'd do it as two articles, each focusing on the relevant bit. Even though the solution is a single product, there are two distinct topics to cover. Information is more readily absorbed in small chunks, like chocolate.
However, there is a JsonTextReader that works a lot like XmlReader but it does have extremely fast skip mechanisms, including "SkipToField" that only do a partial parse.
You can use the reader to navigate to the node you want, and then you can call ParseSubtree() to only load that subtree into memory, and then you can use JSON path on that.
The trouble is I didn't implement the JsonPath, someone else did under the MIT license and I'm using it in my code. It's quite cryptic and undocumented so I think i might be able to modify it eventually, but not at the moment. It only works on an in memory model.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
I'd be in favor of two articles. One article that goes into all details just might prove to be too much for someone who's only interested in one part or the other. I'd say, write an article that dives into the details of your library, and then the second article (which can link to it) can focus on demonstrating how to use the library in your real-world app.