How mayankaneja837/flownote works
Project type and purpose
• FlowNote is a full-stack note-taking and blogging application.
• The frontend is built with React, TypeScript, Vite, Tailwind CSS, and React Router.
• The backend is a TypeScript Hono (lightweight web framework) service, deployed via Wrangler to Cloudflare Workers, using Prisma ORM and JWT for auth.
• A shared “common” package holds Zod schemas and TypeScript types for cross-cutting concerns (validation, DTOs).
File structure
• Top-level directories:
• Backend/ – server code, API routes (src/routes), Prisma schema and migrations (prisma/), Hono setup, tsconfig.
• Frontend/ – React app (pages, components, hooks), Vite config, Tailwind and PostCSS, ESLint.
• common/ – shared utilities (src/index.ts), build output (dist/), package metadata.
• Architectural hints:
• Backend follows a router-based REST API (blogRouter, userRouter).
• JWT middleware likely injected at the Hono application level.
• “common” is a standalone npm package consumed by both front- and back-end for types/validation.
• Deployment artifacts:
• wrangler.toml – Cloudflare Worker config for the backend.
• Vite’s build config (vite.config.ts) for the frontend static assets.
README for additional insights
• Confirms RESTful user/blog endpoints, JWT auth, Prisma migrations.
• Frontend uses Axios to call API, React Router for navigation, Tailwind for styling.
• Common provides Zod schemas and TS types.
Final recommendations
• Essential elements: UI, API gateway, middleware, routers, database, shared code.
• Avoid over-splitting: group related route handlers (userRouter & blogRouter) under a single “REST API” component, unless you want to detail each endpoint.