feat: update 9Ruby site structure

Author: vishnu-madhavan-git

.env.example

@@ -0,0 +1,20 @@
+ELEVENLABS_AGENT_ID=agent_your_public_or_secured_agent_id
+ELEVENLABS_API_KEY=your_elevenlabs_api_key
+OPENROUTER_API_KEY=your_openrouter_api_key
+OPENROUTER_MODEL=openrouter/free
+GROQ_API_KEY=your_groq_api_key
+GROQ_MODEL=llama-3.1-8b-instant
+GEMINI_API_KEY=your_gemini_api_key
+GEMINI_MODEL=gemini-2.5-flash-lite
+
+# Supabase CMS / directory data layer
+NEXT_PUBLIC_SUPABASE_URL=https://your-project-ref.supabase.co
+NEXT_PUBLIC_SUPABASE_ANON_KEY=your_supabase_anon_key
+SUPABASE_SERVICE_ROLE_KEY=your_supabase_service_role_key
+
+# Product analytics and heatmapping
+# Keep disabled until the official project IDs are configured.
+NEXT_PUBLIC_ANALYTICS_ENABLED=false
+NEXT_PUBLIC_POSTHOG_KEY=phc_your_posthog_project_key
+NEXT_PUBLIC_POSTHOG_HOST=https://us.i.posthog.com
+NEXT_PUBLIC_CLARITY_PROJECT_ID=your_microsoft_clarity_project_id

.gitignore

@@ -28,12 +28,14 @@
 npm-debug.log*
 yarn-debug.log*
 yarn-error.log*
+*.log
 .pnpm-debug.log*
 .codex-screens/
 .codex-dev-*.log
 
 # env files (can opt-in for committing if needed)
 .env*
+!.env.example
 
 # vercel
 .vercel
@@ -45,7 +47,10 @@ graphify-out/
 
 # local runtime lead captures
 /data/audit-intake/
+/data/blog-events/
+/data/blog-subscribers/
 /data/income-leads/
+/data/revenue-score/
 
 # typescript
 *.tsbuildinfo

docs/ai/PLG_HUB_INFRASTRUCTURE.md

@@ -0,0 +1,28 @@
+# 9Ruby PLG Hub Infrastructure
+
+Date: 2026-05-27
+
+## Direction Captured
+
+9Ruby is moving toward a product-led growth and media hub model: AI tool directory, free utilities, wiki/docs, news, and services as the soft upsell. The current visual site should stay intact until the page architecture is approved.
+
+## Installed Prerequisites
+
+- Supabase client support was already present; `@supabase/ssr` and the Supabase CLI are now installed for the CMS/data layer.
+- PostHog and Microsoft Clarity are installed for analytics, heatmaps, session replay, and search/intent tracking.
+- `pdfjs-dist`, `@ffmpeg/ffmpeg`, and `@ffmpeg/util` are installed for future browser-based PDF/media utilities.
+
+## Non-Visual Runtime Setup
+
+- `src/instrumentation-client.ts` initializes PostHog and Microsoft Clarity only when `NEXT_PUBLIC_ANALYTICS_ENABLED=true` and the relevant project IDs are present.
+- `.env.example` documents the required Supabase, PostHog, and Clarity variables without storing secrets.
+- `supabase/config.toml` exposes the future `plg` schema locally.
+- `supabase/migrations/20260527000000_plg_hub_foundation.sql` creates the first data model for tools, categories, news, wiki guides, comparisons, service offers, search events, and intent events.
+
+## Still Needed Before Production Activation
+
+- Create or link the official Supabase project under the 9Ruby organization.
+- Add real Supabase URL, anon key, and service role key in Vercel/project environment variables.
+- Create the official PostHog and Microsoft Clarity projects, then add their public IDs to Vercel/project environment variables.
+- Decide consent behavior before enabling tracking on production traffic.
+- Apply the Supabase migration to the official project after reviewing the schema.

docs/ai/source-reports/9ruby-Website Launch Strategy.txt

@@ -0,0 +1,52 @@
+This is the exact blueprint to take 9Ruby from an agency site to an elite, product-led AI hub (think Futurepedia meets There's An AI For That, but with a built-in agency backend).
+Since you are running on Vercel, Supabase, and PostHog, you have the absolute best modern stack to execute this efficiently and for practically zero cost on the infrastructure side.
+Here is the master plan for your UI, architecture, database, and SEO to make 9Ruby dominate.
+1. Global UI & Layout Architecture
+To handle massive amounts of data without looking cluttered, we will use a Sidebar + Main Content layout (like Stripe or high-end SaaS dashboards). You mentioned using clean, minimal icons (like Lucide React)—this is perfect for the sidebar.
+The App Store & Directory Structure
+Separate your directories clearly so users know exactly what they are looking at:
+The Hub (Homepage): A massive search bar ("What do you want to automate today?") surrounded by trending categories.
+AI Tools Directory: For SaaS products (ChatGPT, Midjourney, Vapi).
+App Store (Free Utilities): Your in-house, white-labeled mini-apps (PDF tools, JSON formatters).
+Open-Source Repos: A wiki-style section for local models and GitHub setups.
+Page-by-Page Layout Map
+Page Type
+Layout & Key Elements
+Category Page
+Grid layout. Filters on top (Free, Freemium, Paid). Sort by (Trending, Newest).
+Single Tool Page
+Tool Name, Pricing Tag, "Visit Site" button. Below: Description, Pros/Cons, and an embedded YouTube review.
+App Store (In-House)
+Card layout. "Launch App" button. A subtle upsell: "Need this integrated into your CRM? Hire 9Ruby."
+AI News / Blog
+Feed style. "TL;DR" summary bullet points at the top of every article for scannability.
+2. The Database Schema (Supabase)
+To scale to thousands of tools and apps without breaking a sweat, your relational database needs to be pristine.
+Key insight: By linking Categories to both Tools (external SaaS) and Apps (your internal utilities), you can dynamically query Supabase to show "Related Free Apps" on every external tool page.
+3. The SEO & AEO (Answer Engine Optimization) Blueprint
+Google search is changing. People are using Perplexity, ChatGPT, and AI Overviews. You must optimize for AEO (Answer Engine Optimization). Answer engines don't read "fluff"; they read structured data and semantic HTML.
+AEO Architecture (How to feed the AI bots):
+The "TL;DR" Block: At the top of every single Tool Page and Blog Post, include a <div id="summary"> with 3 bullet points summarizing the page. AI bots scrape this first.
+Semantic HTML: Do not use <div> for everything. Use <article> for blog posts, <aside> for related tools, and <nav> for your Lucide icon sidebar.
+Programmatic SEO: Use Next.js dynamic routing ([category]/[tool].tsx) to generate thousands of pages from your Supabase database automatically.
+Example URL: [9ruby.com/tools/ai-voice/vapi](https://9ruby.com/tools/ai-voice/vapi)
+Comparison URL: [9ruby.com/compare/vapi-vs-retell](https://9ruby.com/compare/vapi-vs-retell) (This generates dynamically based on tool tags).
+Schema Markup (JSON-LD)
+Inject this into the <head> of your pages using Next.js Metadata:
+Tools: Use SoftwareApplication schema.
+Blog: Use NewsArticle schema.
+Guides: Use HowTo schema (This is how you get the step-by-step rich snippets on Google).
+4. Analytics & Monetization (PostHog + Vercel)
+Since you are using PostHog and Vercel, your stack is perfectly primed for "Product-Led Upselling."
+1.Set Up PostHog Event Tracking:Track user frustration.
+Set custom events for copy-pasting code, failed app launches, or spending more than 2 minutes on a GitHub installation guide.
+2.Create the 'Frustration Funnel':
+When a user triggers the "stuck" event from Step 1, trigger a Next.js / PostHog conditional modal: "Open source is hard. Let 9Ruby's team deploy this for you securely for $X."
+3.Vercel Edge Caching:
+Because you will have thousands of tool pages, use Vercel's Edge CDN (stale-while-revalidate) to cache your Supabase queries. Your site will load in under 100ms globally, which is a massive ranking factor for Google.
+5. The "Best-in-Class" Blog Structure
+To beat competitors, your blog cannot just be a wall of text. It must be an interactive workspace.
+Floating Table of Contents: On the left sidebar (using Lucide icons).
+Inline Tool Hover: When an article mentions a tool like "Midjourney", hovering over the word should fetch a quick summary card from your Supabase database via a Vercel Edge function.
+The "Run This Prompt" Button: If your blog has a prompt tutorial, include a button that copies the prompt directly to the user's clipboard and redirects them to ChatGPT/Claude.
+By building this exact structure, you stop being an "agency looking for clients" and become a platform that clients use daily, capturing their intent the moment they decide a project is too technical to do themselves.