Skip to content

chore(seo): rich root metadata + per-route layouts + production README#147

Open
zsklav wants to merge 1 commit intoFlashl3opard:mainfrom
zsklav:polish-meta-tags-readme
Open

chore(seo): rich root metadata + per-route layouts + production README#147
zsklav wants to merge 1 commit intoFlashl3opard:mainfrom
zsklav:polish-meta-tags-readme

Conversation

@zsklav
Copy link
Copy Markdown
Contributor

@zsklav zsklav commented May 4, 2026

Root layout (app/layout.tsx)

  • metadataBase, title template ("%s · VibeXcode"), keywords, authors
  • Open Graph (type=website, siteName, url, locale)
  • Twitter Card (summary_large_image)
  • canonical URL
  • robots index/follow
  • SITE_URL pulled from NEXT_PUBLIC_APP_URL with a sensible fallback

Per-route layouts (8 routes)

  • /playground, /Dashboard, /Forums, /community, /Profile, /login, /signup, /Leaderboards each get a thin server-component layout.tsx that exports a route-specific title + description.
  • Combined with the root template, link previews and search results now read "Playground · VibeXcode" with a page-specific blurb instead of the site default.

README.md

  • Replaced the boilerplate "Features" list with a stack table that explains the why of each choice.
  • Added "What's interesting" section walking through the three decisions reviewers actually probe: Judge0 sandboxing, real-time chat with persistent history, and the auth consolidation onto Firebase.
  • Project structure tree, running locally, deploying.
  • Honest "Known issues" section (Socket.IO on serverless, Judge0 polling, reset password URL, no DB migrations, no rate limit).
  • "Things I intentionally did not build" — design system, multi-tenant auth, premature abstractions.
  • Closes with a one-paragraph framing of the depth-vs-breadth trade-off so a reader understands the project's intent.

Root layout (app/layout.tsx)
  - metadataBase, title template ("%s · VibeXcode"), keywords, authors
  - Open Graph (type=website, siteName, url, locale)
  - Twitter Card (summary_large_image)
  - canonical URL
  - robots index/follow
  - SITE_URL pulled from NEXT_PUBLIC_APP_URL with a sensible fallback

Per-route layouts (8 routes)
  - /playground, /Dashboard, /Forums, /community, /Profile,
    /login, /signup, /Leaderboards each get a thin server-component
    layout.tsx that exports a route-specific title + description.
  - Combined with the root template, link previews and search results
    now read "Playground · VibeXcode" with a page-specific blurb
    instead of the site default.

README.md
  - Replaced the boilerplate "Features" list with a stack table that
    explains the *why* of each choice.
  - Added "What's interesting" section walking through the three
    decisions reviewers actually probe: Judge0 sandboxing, real-time
    chat with persistent history, and the auth consolidation onto
    Firebase.
  - Project structure tree, running locally, deploying.
  - Honest "Known issues" section (Socket.IO on serverless, Judge0
    polling, reset password URL, no DB migrations, no rate limit).
  - "Things I intentionally did not build" — design system, multi-tenant
    auth, premature abstractions.
  - Closes with a one-paragraph framing of the depth-vs-breadth
    trade-off so a reader understands the project's intent.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@netlify
Copy link
Copy Markdown

netlify Bot commented May 4, 2026

👷 Deploy request for vibexcode pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit 4db0a19

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant