Skip to content

docs: move website content back to top-level docs/, replace with symlink#4899

Open
mn-ram wants to merge 1 commit intolima-vm:masterfrom
mn-ram:move-docs-back-to-toplevel
Open

docs: move website content back to top-level docs/, replace with symlink#4899
mn-ram wants to merge 1 commit intolima-vm:masterfrom
mn-ram:move-docs-back-to-toplevel

Conversation

@mn-ram
Copy link
Copy Markdown
Contributor

@mn-ram mn-ram commented Apr 28, 2026

Fixes #4686.

Move website/content/en/docs/*docs/* (via git mv, 100% renames, history preserved). website/content/en/docs is now a symlink to ../../../docs, so Hugo continues to find the content tree.

  • 70 files renamed, 0 content change.
  • docs/README.md redirect stub removed (replaced by docs/_index.md).
  • Stale path comment in pkg/driver/qemu/qemu.go updated.
  • docs/images/ and docs/reports/ left untouched.

go build ./... and go vet ./... are clean. Hugo build is verifiable in CI.

Move the Hugo site's documentation tree from website/content/en/docs/
back to the top-level docs/ directory so contributors can find it via
grep / their editor without having to know the website source layout
(per the discussion in lima-vm#4681 and the request in lima-vm#4686).

Hugo continues to find the content via a relative symlink:
website/content/en/docs -> ../../../docs

The existing top-level docs/images/ (used by the Makefile for the
PlantUML sequence diagram) and docs/reports/ (audit reports) are
untouched. The docs/README.md redirect stub is removed, since
docs/_index.md now serves as the documentation root.

Also update a stale path reference in pkg/driver/qemu/qemu.go from
website/content/en/docs/config/vmtype/qemu.md to docs/config/vmtype/qemu.md.

Fixes lima-vm#4686.

Signed-off-by: mn-ram <235066282+mn-ram@users.noreply.github.com>
@mn-ram mn-ram force-pushed the move-docs-back-to-toplevel branch from 0c84f72 to f58a0e8 Compare April 28, 2026 04:13
@mn-ram
Copy link
Copy Markdown
Contributor Author

mn-ram commented Apr 28, 2026

The failed Lints job hit a transient 503 from bestpractices.dev while checking the OpenSSF Best Practices badge link in README.md. The link is live again now (curl -I https://www.bestpractices.dev/projects/6505 returns 302), and the link is unrelated to this PR's changes. Could you please re-run the Lints job?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

git repo: make docs more easily findable

1 participant