Can I vibe code HelpDocs?

Build a self-hosted HelpDocs alternative using Next.js App Router, Tailwind CSS, and Supabase. 

1. DATA MODEL:
Create a Supabase PostgreSQL schema with tables: 
- `categories` (id, title, slug, description, parent_id, position)
- `articles` (id, title, slug, content_markdown, category_id, locale, status, helpful_count, unhelpful_count, created_at, updated_at)
- `search_logs` (id, query, results_count, created_at)
Add a PostgreSQL `tsvector` column and automated trigger on `articles` for full-text search indexing across title and content.

2. PUBLIC HELP CENTER SITE:
Implement static and ISR routes at `/kb/[category]/[slug]`.
Render markdown using `next-mdx-remote` or `marked`.
Include category navigation, table of contents, helpfulness voting buttons (AJAX call to increment counts), and full-text search bar with live auto-complete.

3. EMBEDDABLE STOREFRONT WIDGET:
Create a lightweight Web Component bundle using Vite (`widget.js`).
Use Web Components with Shadow DOM to prevent CSS leaks into host ecommerce stores.
The widget must render a floating trigger button at bottom-right, expandable search bar, instant article slide-over viewer, and fallback ticket contact form.

4. ADMIN CMS DASHBOARD:
Build a protected internal layout at `/admin` using NextAuth or Supabase Auth.
Include Tiptap or a Markdown visual editor for article management, drag-and-drop category ordering, and search analytics displaying top queries without results.

5. EDGE CASES & SCOPE:
Handle fallback routing for missing translations, slug sanitization, full-text term normalization, and CORS domain whitelisting for the embedded widget bundle script. Out of scope: enterprise SAML SSO and native mobile SDKs.

$ each button prefixes agent-specific run instructions · build your own product, never copy proprietary code, trademarks or designs