docs VS website

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.

Oh, just saw this. You wrote your comment while I wrote mine. If you can enumerate specifically what you want to see, please submit it to our issue tracker: https://github.com/caddyserver/website

Generally we encourage examples in our community wiki though: https://caddy.community/c/wiki/13 -- much easier to maintain that way.

Yes, the docs have been updated at https://github.com/caddyserver/website but haven't been deployed yet. There is a new protocols option:

    protocols h1 h2

Could you be more specific about these complaints? What examples don't work? We can't work on improving the docs if we don't get specific and actionable feedback. The docs are found at https://github.com/caddyserver/website if you want to propose any changes.

Protip: you can click almost everything in code blocks in the docs. For example, if you click `[]`, it brings you right to the request matcher syntax section, which explains what you can fill in there.

It would be redundant to write on every page what you can use as a matcher. The Caddyfile reference docs assume you've read https://caddyserver.com/docs/caddyfile/concepts which walks you through how the Caddyfile is structured, and it'll give you the fundamentals you need to understand the rest of the docs (I think, anyway).

If you think we need more examples for a specific usecase, we can definitely include those. Feel free to propose some changes on https://github.com/caddyserver/website, we could always use the help!