Roadmap Voting, Runtime Logs, Automatic First Pages, and Cleaner SEO

This week focused on making VibeNest easier to steer and easier to trust: users can vote on upcoming features, see live runtime logs, get an automatically generated first project page, and rely on cleaner metadata across public pages.

Feature Voting and a Public Roadmap

VibeNest now has lightweight feature voting. Admins can create predefined feature requests, users can vote or unvote, and each feature can decide whether its vote count is public.

The new /dashboard/roadmap page shows active requests with a simple "I want this" action. The first seeded requests are 2FA and backup-password support for Google users. A reusable feature-vote banner can also appear directly where the feature matters, starting with the hidden 2FA settings page.

For admins, /admin/feature-requests supports creation, active-state toggles, vote-count visibility, voter inspection, CSV export, and deletion with typed confirmation.

Runtime Logs in the Project Panel

The project quick panel now has Build and Runtime tabs. Running projects open directly to Runtime, so owners can tail the live container output without leaving the dashboard.

The viewer supports manual refresh, periodic auto-tail, sticky-bottom scrolling, and a clearer distinction between "the container is quiet" and "Coolify is unavailable."

To prevent log viewing from becoming an accidental load amplifier, VibeNest now throttles on the client and coalesces repeated log requests on the server.

Automatic First Project Pages

New solo projects with a Git repository can now get their first public page generated in the background. VibeNest creates one wiki home page from the repository, beautifies it into HTML, and shows progress on the dashboard while the job runs.

The app deployment flow remains separate. This change is about giving every new project a useful public starting point faster, so owners do not land on an empty wiki after connecting a repository.

Larger Welcome Credits

The welcome credit bonus increased from 2,000 to 5,000 credits. Existing users who registered before the increase can be topped up through an idempotent admin action.

This makes the first automatic page generation more realistic for larger repositories without forcing users to understand credit mechanics on day one.

Account Settings Cleanup

The /Account/Manage area was restyled with the same Tailwind-based visual system as the dashboard. Profile, email, password, external login, passkeys, and personal-data pages now look like part of VibeNest instead of unstyled ASP.NET Identity scaffolding.

Two risky or incomplete paths were hidden from the main navigation: 2FA setup, because the QR-code experience is not ready, and email change, because the production flow still needs dedicated testing. Google-linked users also get clearer copy explaining that their password can be used as a backup while Google sign-in remains the primary path.

Cleaner SEO Metadata and Structured Data

Public pages without a custom social preview now get a default og:image. Wiki articles now emit breadcrumb structured data and use og:type=article, matching the existing article JSON-LD.

Landing and comparison pages gained a reusable FAQ component that renders both the visible accordion and FAQPage JSON-LD from the same source. This avoids the common SEO problem where structured data says a FAQ exists but the page does not show one.

What This Enables

The product now has a feedback loop, better live debugging, a stronger first-project experience, and cleaner public-page metadata. That combination matters for both activation and trust: users can see what is happening, influence what comes next, and share pages that look more complete by default.