Translations, Publish Readiness, and One-Click Postgres Deploys

This week made VibeNest more usable after the first deployment: owners can polish translated pages, understand whether a project is ready to publish, and rely on Postgres auto-attach during real deploys instead of fixing database setup after a crash.

Wiki Translations Are Editable

The wiki editor now has a Translations tab. Owners can inspect AI translations, manually edit title and content, regenerate a translation, mark it outdated, or delete it.

When the source page changes, stale translations are now visible in the UI. The backend already tracked that state; the missing piece was surfacing it where the owner can act on it.

Public wiki pages also gained canonical links that respect the selected language, so translated project pages have cleaner SEO structure.

Platform Language Switcher

VibeNest now has a platform-level language switcher in the header and dashboard layout. It stores the selected language in a cookie, can use the logged-in user's preference, and falls back to Accept-Language.

The interface is still English-first, so non-English options are clearly marked as coming soon. The important part is that the platform now has the plumbing to remember and render language preference consistently.

Publish Readiness Checklist

Project cards now show a publish badge that opens a readiness checklist. The checklist highlights issues such as broken deploys, missing descriptions, missing icons, missing SEO, internal-only mode, blocked status, and projects that have never deployed.

The checklist is advisory. VibeNest does not block publishing because of red or yellow items; it gives the owner a clear list of what might reduce trust or conversion.

Coolify 502s No Longer Mark the Fleet Idle

A transient Coolify API error previously looked like "no resources exist." That could make all live projects appear idle at the same time.

The monitor now distinguishes "Coolify is unavailable" from "Coolify returned an empty resource list." It also requires repeated empty reads before mass-orphan logic can run, and it can reattach orphaned project rows by matching Coolify resource names.

Postgres Auto-Attach Reached the Acceptance Goal

Postgres auto-attach was rebuilt around a tri-state setting: auto-detect, forced on, or opted out. Detection now runs at deploy time, not only during the wizard, and solo deployments gained the same Postgres support as grouped deployments.

The practical result: a Postgres-backed app that previously needed AI Doctor intervention can now go from deploy to running in one click, with DATABASE_URL available before the app starts.

What This Enables

This release moves VibeNest closer to the promise of "deploy and publish without babysitting." Owners get clearer publishing feedback, translated content is maintainable, and database-backed apps can succeed on the first deploy instead of relying on a repair loop.