retroachievements / docs Goto Github PK

Can be omitted from the page using frontmatter
https://docs.retroachievements.org/developer-docs/minimum-required-versions-for-logic-features.html#minimum-required-versions-for-logic-features

https://vitepress.dev/reference/frontmatter-config#aside

The hits column is still being truncated / requires horizontal scrolling.

Let's have a custom Trigger viewer component for our dev docs. Not sure how feasible this is, but something like this would be great:

::: trigger

| ID  | Flag      | Type  | Size   | Memory | Cmp | Type | Size | Mem/Val | Hits |
| --- | --------- | ----- | ------ | ------ | --- | ---- | ---- | ------- | ---- |
| 1   | SubSource | Delta | 16-bit | 0x1234 |     |      |      |         |      |
| 2   | Remember  | Mem   | 16-bit | 0x1234 |     |      |      |         |      |

:::

Then the table would receive special formatting.

No longer exists in the nav, only contains two sentences, and only can be directly hyperlinked to.

https://vitepress.dev/guide/frontmatter#frontmatter

This page is from an older period in the docs where logic links didn't exist in the nav. There is no way to navigate to this page through the traditional docs nav - it can only be reached via a direct hyperlink.

It's largely redundant at this point.

From the index, there should be a giant link that users can press which walks them through making an account, downloading an emulator, and hopping into a (popular) game and playing as quickly as possible.

Currently a user can only land on this page through 1 buried link in the docs, or if they enter the page sideways via some direct URL. If the page is important enough to be in the docs, we should let users generally navigate to it.

We get an ungodly amount of traffic from Google for queries related to this, generally landing on random forum threads and then instantly bouncing.

We should add a dedicated page in our docs for how to set up turbo on some of the emulators we support (RetroArch, etc).

Currently a user can only land on this page through 1 buried link in the docs, or if they enter the page sideways via some direct URL. If the page is important enough to be in the docs, we should let users generally navigate to it.

While we don't support an offline mode, emulators can detect when users go offline and will resync when a connection to the server can be reestablished. We get a lot of questions about this - it probably warrants adding something to our FAQs.