docs: merge duplicate README.md into _index.md, add missing mongodb horizon image

The welcome, guides, and selfhost-setup sections each had a leftover
README.md from the VitePress migration sitting alongside the real
Hugo _index.md, silently colliding on the same URL and breaking
navigation on those pages. Merge README.md content into _index.md
(porting aliases) and drop the duplicates.

Also add the missing db-create/mongodb/horizon.png referenced by the
mongodb+srv DNS docs, and document the extra-'../' link convention,
liche's -s flag, and this README/_index collision pattern in
CLAUDE.md so it doesn't need re-explaining.

Signed-off-by: Arnob kumar saha <arnob@appscode.com>

Author: ArnobKumarSaha

CLAUDE.md

@@ -0,0 +1,43 @@
+# Docs repo notes
+
+Migrated from VitePress to Hugo (`98965f8`). Content lives under `docs/platform/`.
+
+## The extra `../` convention (intentional, do not "fix")
+
+Every relative link/image in this repo needs **one extra `../`** beyond what the
+real filesystem nesting implies — this applies uniformly to `_index.md` section
+pages AND regular leaf `.md` pages, even for files in the *same* directory
+(e.g. `cluster-overview.md` links to its sibling `images/` dir as `../images/...`).
+This is real, required Hugo behavior on the live site — verified by checking
+which files actually 404 vs render. Don't "correct" it back to matching disk
+paths; that breaks the live site even though it looks more "correct".
+
+Plain file links keep the `.md` extension (e.g. `../mongodb.md`) — this is fine,
+Hugo resolves it. Only anchor links were converted from `.md#anchor` to `/#anchor`
+form (`#134`), because `.md#anchor` doesn't resolve but `.md` alone does.
+
+## liche (CI link checker)
+
+CI uses a custom fork (`appscodelabs/liche`, branch `arnob-strip-prefix`) with
+an extra flag: `-s, --strip-relative-prefix` — strips one leading `../` from
+each relative link before checking it against the filesystem. This exists
+*because* of the extra-`../` convention above: it lets the checker validate
+against real on-disk paths without every link failing.
+
+To check a file the same way CI does:
+```
+liche -p -h -l -s <file.md>
+```
+Never validate without `-s` and conclude links are broken — that check
+deliberately ignores the site's real routing.
+
+## README.md vs _index.md — do not let both exist in one directory
+
+Hugo uses `_index.md` as a section's real index page. A few directories still
+had a leftover `README.md` from the VitePress days, front-matter-spoofing the
+same URL (or aliasing to it) — the two pages silently collided and broke
+navigation only on those pages, even though every relative-link rule above
+was followed correctly. If you find a directory with both, merge `README.md`'s
+body into `_index.md` (keep `_index.md`'s frontmatter, port any `aliases:`),
+then delete `README.md`. `docs/platform/`, `docs/platform/guides/`, and
+`docs/platform/selfhost-setup/` already went through this fix.

docs/platform/README.md

@@ -7,4 +7,23 @@ menu:
     name: Welcome
     weight: 10
 menu_name: docsplatform_{{.version}}
+aliases:
+- /docs/platform/{{.version}}/welcome/
+- /docs/platform/{{.version}}/README/
 ---
+
+# KubeDB Platform Documentation
+
+This page is the entry point for KubeDB Platform documentation.
+
+## Core sections
+
+- [Selfhost Setup](../selfhost-setup/)
+- [Guides](../guides/)
+
+## Contributor resources
+
+- [Contributing](../contributing.md)
+- [Support](../support.md)
+
+Use [Guides](../guides/) for day-to-day workflows, then continue to [Selfhost Setup](../selfhost-setup/) for deployment-specific instructions.

docs/platform/_index.md

@@ -7,4 +7,24 @@ menu:
     weight: 30
 menu_name: docsplatform_{{.version}}
 section_menu_id: guides
+aliases:
+- /docs/platform/{{.version}}/guides/README/
 ---
+
+# Platform Guides
+
+This section contains practical, task-oriented guides for operating and managing the platform.
+
+## Guide categories
+
+- [Account Management](../account-management/)
+- [Billing and Usage Guide](../billing-and-usage-guide/)
+- [Cluster Management](../cluster-management/)
+- [Database Management](../database-management/)
+- [Get Started](../get-started/)
+- [Integrations](../integrations/)
+- [License Management](../license-management/)
+
+## Recommended path
+
+For first-time users, start with [Get Started](../get-started/) and then move to the specific management areas relevant to your workflow.

docs/platform/guides/README.md

@@ -7,4 +7,29 @@ menu:
     weight: 20
 menu_name: docsplatform_{{.version}}
 section_menu_id: selfhost-setup
+aliases:
+- /docs/platform/{{.version}}/selfhost-setup/README/
 ---
+
+# Host KubeDB Platform as Your Own
+
+Welcome to KubeDB Platform's Self-Hosted deployment! Whether you're looking for a quick trial in "Self Hosted Demo" mode or gearing up for a production-ready environment (`Self Hosted Production`), you're in control.
+
+Navigate to [KubeDB Platform Self-Hosted](https://appscode.com/selfhost). Here you will find your previously generated self-hosted installers.
+
+![Installer Home](../images/installer-home.png)
+<br/>
+
+<br/>
+
+Click on the `Create New Installer` button to get started. You can choose various deployment types including `Cloud Demo` or `Self Hosted Production`. Provide the required data and click `Done` button to generate the installer. Upon generation of the installer, you will get the documentation how to host KubeDB Platform Server on your own.
+<br/>
+
+<br/>
+
+To get detailed documentation on `Cloud Demo` installer, head over to [Demo Deployment](../install/cloud-demo.md).
+<br/>
+
+<br/>
+
+To get detailed documentation on `Self Hosted Production` installer, head over to [Production Deployment](../install/selfhosted-production.md).