[Bug] /docs/ route renders an empty landing page instead of a useful docs entry point

[Suhani95]

Page link

https://kyverno.io/docs/

Description

The /docs/ route currently provides a poor user experience for users who directly navigate to the documentation root.

At the moment, the page appears mostly empty and does not provide a clear onboarding path, navigation guidance, or documentation overview for new users.

Since many users may reach /docs/ through bookmarks, search engines, shared links, or manual navigation, the current experience can feel unfinished and confusing.

Why this matters

• /docs/ is commonly expected to be the primary documentation entry point.
• New users may not know where to start.
• The current page lacks discoverability for major documentation sections.
• This impacts onboarding and overall documentation usability.

Possible Improvements

Potential improvements may include:

• Redirecting users to a more useful entry page temporarily
• Creating a dedicated documentation landing page
• Adding quick start links and onboarding paths
• Providing links to major documentation sections
• Adding role based navigation for different audiences
• Improving overall documentation discoverability and UX

Possible Files

• src/content/docs/docs/index.md
• astro.config.mjs

Expected behavior

Visiting:

https://kyverno.io/docs/

should provide a clear and useful documentation entry experience instead of an almost empty page.

Users should either:

• be redirected to an appropriate starting page, or
• see a dedicated documentation landing page with meaningful navigation and onboarding content.

Slack discussion

No response

[lucchmielowski]

@Suhani95 as discussed during the community meeting, this behaviour has changed because of #2045, /docs is now redirected to /docs/introduction using Netlify.

Feel free to update the behaviour if you think it should be done differently.

[Suhani95]

@lucchmielowski Thanks! One thing I was wondering, why are we handling this redirect only at the Netlify/deployment level and not inside astro.config.mjs as well? I feel local dev should ideally match production behavior too.

Maybe one clean approach could be making /docs the actual docs home (docs/index.md) by moving the current introduction content there, and then keeping /docs/introduction as an alias/redirect for backward compatibility.

Otherwise, a temporary Astro level redirect for now could also work.