beleyBlog VS docs

How does having the "BSD Zero Clause" with your content work? I open sourced my blog's software, but I still keep all the actual content in a separate private repo, since I don't want my written content distributed under the same license. Also works out well, since I have the github action automation in the private content repo.

I can still easily change the private flag down the road if I were to decommission it (though, unlikely -- I'd just archive it somewhere).

I'm also using Gatsby if anyone is curious (https://github.com/cbeley/beleyblog & https://chrisbeley.com).

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.