Restructure “Advanced” docs by merging topics into related sections

[Wadiou]

Describe the change

Please remove the standalone “Advanced” section from the docs and move its pages into the sections they belong to conceptually. For example, “Expanding Type Support for OpenAPI Link” should live under the "OpenAPI" section and etc.

URLs

No response

Additional information

• Would you be willing to help?

[pullfrog]

  ^{｜ Build this ➔ ｜ Make a plan ➔}

[dinwwwh]

But users can be overwhelmed when trying to understand the docs without clearly marking them as advanced. Once users reach an advanced level, though, I don't think they'll have much trouble finding those docs.

[Wadiou]

for me i find something like Coercion isn't an advanced thing and it's instead recommended to use , and even if it's advanced i don't want it to be in a whole separate section but ionstead putting it in an advanced block under it's related section

[Wadiou]

One more docs ux thing: the current sidebar is just a long linear list grouped by headings, and it’s way harder to scan than the old collapsible version
would be nice if the sections were collapsible by default again, with icons on each section so the nav is easier to scan and a bit more visually appealing
when a section gets long, having sub‑groups / labels inside that collapsible section would help a lot instead of one big flat list
the better auth docs sidebar is a good example of the kind of structure and visual hierarchy i mean, with clear grouping and icons that make it easy to navigate

[dinwwwh]

the current sidebar is just a long linear list grouped by headings, and it’s way harder to scan than the old collapsible version

a way to flex how big oRPC is 🙃