How adam-3owl/veya-analytics-wiki works
Project type and purpose
• This is a Next.js 13 “App Router” front-end application, branded “Veya Analytics SDK Reference,” whose sole job is to display a searchable reference of all trackable metrics and events. There is no custom backend here; it’s a static/SSR React site optimized for Vercel.
File structure
• Top-level directories:
• app/ – Next.js 13 app directory (layout.tsx, page.tsx, globals.css)
• components/ – UI components (logo, theme-toggle, metrics-table) and a “ui” subfolder of primitives (button, input, tabs, separator)
• lib/ – domain logic (fetch-metrics.ts for loading your metric definitions, utils.ts for shared functions)
• types/ – TypeScript definitions for your metric objects
• Config files: next.config.js, tsconfig.json, postcss.config.mjs
• Build & deploy: package.json scripts, optimized for Vercel continuous deployment
README for additional insights
• Features: search, category filters, theme toggle, responsive
• Deployment: “Deploy with Vercel” button, static hosting with incremental builds
• No mention of a separate API server—the lib/fetch-metrics module likely pulls from a local JSON or the Veya Analytics SDK at build time
Detail without over-engineering
• Break out every logical piece: layout, page, components, lib, types, hosting
• Both build-time (SSR/SSG) and run-time (hydration, filtering) flows