Clarify public project navigation and standalone WebUI setup #304

Merged
karsten merged 1 commit from docs/public-repository-navigation into main 2026-11-08 09:39:28 +00:00
Owner

Correct the stale Plugins/webui README link, link the public standalone WebUI, distinguish the legacy bundled loopback UI from the current independent frontend/backend setup, and clarify optional rather than bundled integrations. Keep existing compatibility instructions and license. Normal build and five product/starter documentation tests passed; no runtime behavior or configuration changes.

Correct the stale Plugins/webui README link, link the public standalone WebUI, distinguish the legacy bundled loopback UI from the current independent frontend/backend setup, and clarify optional rather than bundled integrations. Keep existing compatibility instructions and license. Normal build and five product/starter documentation tests passed; no runtime behavior or configuration changes.
Author
Owner

Normal build and complete Core suite on exact source candidate passed:1605 tests passed, one existing optional skip, zero failures. This PR changes only README navigation, no executable source or dependencies.

Normal build and complete Core suite on exact source candidate passed:1605 tests passed, one existing optional skip, zero failures. This PR changes only README navigation, no executable source or dependencies.
karsten deleted branch docs/public-repository-navigation 2026-11-08 09:39:29 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
harness/core!304
No description provided.