Links in documentation causing 404s

[bquackie]

TanStack Table version

latest

Framework/Library version

Chrome, Safari

Describe the bug and the steps to reproduce it

I don't know if this is the correct way to communicate documentation issues, but here goes:

1. Go to: https://tanstack.com/table/latest/docs/guide/column-filtering
2. Click/Tap on Column Filtering API

Expected: see API documentation Actual: 404 page asking to go back or restart

My guess is that there was a directory or routing change. In re: to the links above, you get routed to https://tanstack.com/table/latest/api/features/column-filtering but you should be routed to https://tanstack.com/table/latest/docs/api/features/column-filtering.

To get to the correct page, I have to manually add docs between latest and api to the URL. Or, Is this just my computers?

Your Minimal, Reproducible Example - (Sandbox Highly Recommended)

https://tanstack.com/table/latest/docs/guide/column-filtering

Screenshots or Videos (Optional)

Actual:

Expected:

Do you intend to try to help solve this bug with your own PR?

No, because I do not know how

Terms & Code of Conduct

• [x] I agree to follow this project's Code of Conduct
• [x] I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

[azeek21]

+1.

Seems like a mass incident with relative links inside /docs directory. Have seen a few PRs (#5945, #5933, #5932, #5918 and so on). I did look around a little bit but couldn't put my finger on exatly what and where went wrong.

Here's some things one can take a look at:

Could be related: 024ecda9f3790e2555410999824173fc5516bfce Where routing happens for docs: https://github.com/TanStack/tanstack.com/tree/main/app/routes/%24libraryId Where links in md files get turned into hrefs (mardown render): https://github.com/TanStack/tanstack.com/blob/main/app/components/Doc.tsx

[ravshan77]

Checking the Documentation Routing Configuration

TanStack documentation might be built using Docusaurus or Next.js. The issue could be caused by an incorrect router configuration.

Open apps/docs/next.config.mjs or docusaurus.config.js and check the following code:

If the redirect configuration is missing or incorrect in next.config.mjs or docusaurus.config.js, it needs to be fixed.