Connect Discover: make connect.minekube.com a public server directory

[robinbraemer]

Human need

People should be able to discover and share Connect servers from any browser before installing anything. Endpoint owners should receive a durable public page instead of depending on screenshots and copied addresses.

Outcome

Turn connect.minekube.com into a first-class consumer of the canonical Connect Discover API with a public server directory and shareable endpoint pages.

Primary implementation repo: minekube/connect (.web). Authenticated editing remains in minekube/website.

Experience

• Public /servers discovery route with fast search, fixed filters, sort, online/freshness state, compatibility, and pagination.
• Stable public endpoint pages with verified join addresses, media, description, compatibility, categories, language, public status/votes, owner-provided links, report action, and last-updated/freshness cues.
• One primary Play/Join action: open the Connect mod deep link when supported, otherwise copy the verified address and explain the minimum next step.
• Social/SEO metadata and canonical URLs without leaking private control-plane fields.
• Helpful offline, unknown, suspended, unpublished, and not-found states.

Accessibility and performance

• Server-rendered, progressively enhanced, mobile-first, keyboard and screen-reader accessible.
• Usable without JavaScript for core browsing/copying.
• Respect reduced motion, contrast, text zoom, localization expansion, and low-bandwidth/data-saver conditions.
• Cache public data at the edge while honoring publication/moderation purge bounds.

Acceptance criteria

• Directory and detail pages consume only the documented public API, not private database access or duplicated listing logic.
• Search/filter state has shareable URLs and correct canonical metadata.
• Core content, verified address, and copy action work without JavaScript.
• Deep-link fallback is understandable on unsupported browsers/devices.
• Online/stale/offline and compatibility information agrees with the mod and Browser Hub for the same API snapshot.
• Unpublish/moderation removal updates generated pages, caches, sitemaps, and social previews within the documented bound.
• Automated accessibility checks plus keyboard/screen-reader manual smoke tests pass.
• Performance budgets cover HTML, media, API latency, Core Web Vitals, and low-bandwidth behavior.
• Browser E2E publishes a dedicated test listing, finds it, opens it, copies/launches the verified join target, then proves removal after unpublish.

Non-goals

• Making the public docs site an authenticated listing editor.
• Maintaining a second server-list database.
• Publishing endpoints that have not explicitly opted in.