Links with on startpage are problematic when opened as `/docs` (no trailing slash)

[janpio]

If you open the startpage as /docs (note the missing trailing slash) all the links with ./ do not work. These probably need to be absolute.

See part of the source code here:

stroke-linejoin="round"></path><path d="M1.5 11.6666H15.5" stroke="#CBD5E0" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"></path><path d="M6.75 1L5 17" stroke="#CBD5E0" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"></path><path d="M12 1L10.25 17" stroke="#CBD5E0" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"></path></svg>Getting started</a></h3><p class="paragraph">The <strong>Getting started</strong> section contains <em>practical guides</em> to help you get started with Prisma.</p><ul class="list"><li><a href="./getting-started/quickstart">Quickstart</a> (5 min)</li><li>Setup Prisma<ul class="list"><li><a href="./getting-started/setup-prisma/add-to-existing-project">Add Prisma to an existing project</a> (15 min)</li><li><a href="./getting-started/setup-prisma/start-from-scratch-sql-migrations">Start from scratch (SQL migrations)</a> (15 min)</li></ul></li></ul><hr/></section><section><h3 id="understand-prisma"><a class="headings__A-sc-13lpp34-1 kYzUFs title-link" href="#understand-prisma"><svg width="17" height="18" viewBox="0 0 17 18" fill="none" xmlns="http://www.w3.org/2000/svg" class="headings__StyledAnchor-sc-13lpp34-0 gMuomf"><path d="M1.5 6.33337H15.5" stroke="#CBD5E0" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"></path><path d="M1.5 11.6666H15.5" stroke="#CBD5E0" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"></path><path d="M6.75 1L5 17" stroke="#CBD5E0" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"></path><path d="M12 1L10.25 17" stroke="#CBD5E0" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"></path></svg>Understand Prisma</a></h3><p class="paragraph">The <strong>Understand Prisma</strong> section contains <em>conceptual</em> information about Prisma.</p><ul class="list"><li><a href="./understand-prisma/introduction">Introduction</a></li><li><a href="./understand-prisma/why-prisma">Why Prisma?</a></li><li>Prisma in your stack<ul class="list"><li><a href="./understand-prisma/prisma-in-your-stack/rest">REST</a></li><li><a href="./understand-prisma/prisma-in-your-stack/graphql">GraphQL</a></li><li><a href="./understand-prisma/prisma-in-your-stack/is-prisma-an-orm">Is Prisma an ORM?</a></li></ul></li><li><a href="./understand-prisma/data-modeling">Data modeling</a></li><li><a href="./understand-prisma/under-the-hood">Under the hood</a></li></ul><hr/></section><section><h3 id="reference"><a class="headings__A-sc-13lpp34-1 kYzUFs title-link" href="#reference"><svg width="17" height="18" viewBox="0 0 17 18" fill="none" xmlns="http://www.w3.org/2000/svg" class="headings__StyledAnchor-sc-13lpp34-0 gMuomf"><path d="M1.5 6.33337H15.5" stroke="#CBD5E0" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"></path><path d="M1.5 11.6666H15.5" stroke="#CBD5E0" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"></path><path d="M6.75 1L5 17" stroke="#CBD5E0" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"></path><path d="M12 1L10.25 17" stroke="#CBD5E0" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"></path></svg>Reference</a></h3><p class="paragraph">The <strong>Reference</strong> section contains <em>technical</em> information about Prisma.</p><ul class="list"><li>Tools and interfaces<ul class="list"><li>Prisma schema<ul class="list"><li><a href="./reference/tools-and-interfaces/prisma-schema/prisma-schema-file">Prisma schema file</a></li><li><a href="./reference/tools-and-interfaces/prisma-schema/data-sources">Data sources</a></li><li><a href="./reference/tools-and-interfaces/prisma-schema/generators">Generators</a></li><li><a href="./reference/tools-and-interfaces/prisma-schema/data-model">Data model</a></li><li><a href="./reference/tools-and-interfaces/prisma-schema/models">Models</a></li><li><a href="./reference/tools-and-interfaces/prisma-schema/relations">Relations</a></li></ul></li><li>Prisma Client<ul class="list"><li><a href="./reference/tools-and-interfaces/prisma-client/api">API reference</a></li><li><a href="./reference/tools-and-interfaces/prisma-client/generating-prisma-client">Generating Prisma Client</a></li><li><a href="./reference/tools-and-interfaces/prisma-client/configuring-the-prisma-client-api">Configuring the Prisma Client API</a></li><li><a href="./reference/tools-and-interfaces/prisma-client/crud">CRUD</a></li><li><a href="./reference/tools-and-interfaces/prisma-client/relation-queries">Relation queries</a></li><li><a href="./reference/tools-and-interfaces/prisma-client/field-selection">Field selection</a></li><li><a href="./reference/tools-and-interfaces/prisma-client/raw-database-access">Raw database access</a></li><li><a href="./reference/tools-and-interfaces/prisma-client/connection-management">Connection management</a></li><li><a href="./reference/tools-and-interfaces/prisma-client/advanced-usage-of-generated-types">Advanced usage of generated types</a></li><li><a href="./reference/tools-and-interfaces/prisma-client/logging">Logging</a></li><li><a href="./reference/tools-and-interfaces/prisma-client/debugging">Debugging</a></li><li><a href="./reference/tools-and-interfaces/prisma-client/error-formatting">Error formatting</a></li><li><a href="./reference/tools-and-interfaces/prisma-client/transactions">Transactions</a></li><li><a href="./reference/tools-and-interfaces/prisma-client/deployment">Deployment</a></li><li><a href="./reference/tools-and-interfaces/prisma-client/query-engine">Query engine</a></li><li><a href="./reference/tools-and-interfaces/prisma-client/module-

[nikolasburk]

I think we resolved this by always automatically redirecting to docs/. Can you confirm this is still an issue @janpio or otherwise close this issue?

[janpio]

That only works if Javascript is enabled unfortunately. Crawlers like Google (and the tooling that I use to crawl the site from my computer for example) still can visit /docs and will see the links to 404 pages.

Netlify unfortunately does not offer any option to force the / at the end of the URL without side effects we might not want: https://docs.netlify.com/routing/redirects/redirect-options/#trailing-slash If that is the only way, we need to investigate what enabling this option does to out other pages.

[nikolasburk]

Ah I see, thanks for clarifying! I guess another solution would potentially be to use absolute URLs throughout the entire docs then?

[janpio]

Something like that, yes. But that is also problematic if you think about the future when we will want to version the current docs as 2.0.0 in a subfolder for example. @nilubava will have to look into the right thing to do here (which might very well be the Netlify option...).

[janpio]

Unfortunately not fixed: