feat(superadmin): migrate internal docs from docusaurus to guava kb

docs/ops/deployment/dokploy.md

@@ -121,9 +121,8 @@ Only SuperAdmins should have access to these widgets. If you rotate the API key,
 
 With this setup the Fotospiel team can manage deployments, restarts, and metrics centrally through Dokploy while Laravel’s scheduler and workers continue to run within the same infrastructure.
 
-## 8. Internal docs publishing in Dokploy
+## 8. Internal docs in Dokploy
 
-- Build the static docs site during CI/CD by running `./scripts/build-docs-site.sh`. Upload the resulting `docs/site/build` directory as part of the deployment artifact or copy it into the Dokploy server before redeploying the stack.
-- `docker-compose.dokploy.yml` mounts that directory into the Nginx container and exposes it at `/internal-docs/`, protected by HTTP Basic Auth.
-- Update `docker/nginx/.htpasswd-docs` with production credentials (use `htpasswd -c docker/nginx/.htpasswd-docs <user>` locally, then redeploy). The repository ships with a weak default only for development—always override it in Dokploy.
-- If Dokploy builds the image itself, add a post-build hook or automation step that runs the docs build and copies it into the shared storage volume before restarting the `web` service.
+- Internal operations/admin documentation is served from the SuperAdmin panel itself via the Guava Knowledge Base.
+- Access path: `/super-admin/docs` with normal SuperAdmin authentication (`super_admin` guard).
+- No dedicated documentation build container or static docs artifact is required in Dokploy.