go-readability VS docs

https://github.com/go-shiori/go-readability https://github.com/mauidude/go-readability

In terms of extracting the actual blog content from pages, there is a go library that implements the readability algorithm:

https://github.com/mauidude/go-readability

This is the kind of thing pocket/instapaper do to extract the main content from a page in a format that's easier to read (and also probably to programmatically modify)

here's the official guide/documentation: https://docs.libretro.com/

We'll deal with it. Looks like it's just the web host, so not that big of a deal. docs.libretro.com and buildbot.libretro.com should still be fine.

I just PRed a blurb that outlines that process based on your comment. Does this look right to you? https://github.com/libretro/docs/pull/840

So, what have you tried for the cheats? Did you make sure the core you're using is compatible with RetroArch's cheats (you can find this information on the cores' pages at docs.libretro.com)?

Sure. You can send PRs to the docs repo https://github.com/libretro/docs/

A log would tell us more, but did you do any of the required setup for those cores? They need BIOS images to function. See the cores' pages on docs.libretro.com for more details.

Emulation Wiki and Libretro docs.

So starting in August 2017, there was a repository called (https://github.com/libretro/docs/) that I contributed frequently to.