How imoken777/sillahub works
Project type and purpose
• This is a full-stack Next.js 13 application bootstrapped with Cloudflare Pages (c3).
• Frontend: React/Next.js “app router” under src/app with server-side rendering and static asset delivery.
• Backend/API: Cloudflare Pages Functions (under src/app/api) exposing REST endpoints, including a cron-style public/cron parser pipeline.
• Persistence: Drizzle ORM managing relational schema and migrations. Potentially backed by a Cloudflare-hosted database or KV (example bindings present).
• DevOps: GitHub Actions for CI/deploy, Wrangler for preview/deploy to Cloudflare Pages.
File structure
• Top-level:
• next.config.mjs, tailwind.config.ts, postcss.config.mjs → framework and styling config
• drizzle.config.ts, src/drizzle → database ORM config & migration scripts
• wrangler.toml → Cloudflare Functions binding & deploy config
• .github/workflows → CI (ci.yml), CD (deploy.yml)
• src/app → Next.js “app router” layout.tsx, page.tsx, not-found.tsx, global CSS
• src/app/api/[...route] → catch-all Function endpoints: public/factory.ts, public/cron/* parser jobs, route.ts
• src/lib/db.ts → DB client initialization (Drizzle)
• src/components → UI components (layout, model, ui) consumed by pages
• src/constants, src/types, src/utils → shared types, constants, helpers