This is a really interesting approach, I hadn't thought of this!
Just out of curiosity, do you think the separate documentation page has better conversion than if you were to, say, include the ad directly into the readme inside the repo?
You have less control over formatting and ad placement in the README file, as rendered markdown offers only limited options. With a dedicated documentation website, it’s much easier.
It’s also a question of sovereignty. If your documentation is in the README, then GitHub owns the audience. If they, for some reason, close your project, you’re finished. With your own documentation page, the risk is much lower.
Just out of curiosity, do you think the separate documentation page has better conversion than if you were to, say, include the ad directly into the readme inside the repo?