How chentim1011/happynote works
Project type and purpose
• This is a full-stack web application called “HappyNote” for managing knowledge cards and whiteboards.
• Frontend: React (Vite) single-page app that lets users create, edit, and link cards on a whiteboard.
• Backend: Node.js + Express REST API serving card, user, login, and whiteboard endpoints.
• Database: MongoDB for storing users, cards, and whiteboards.
• Goal: Offer a free, core feature–complete alternative to paid tools like Heptabase.
File structure
• Top-level directories:
• docs/planning – design docs and planning artifacts
• src/backend – server code, controllers, models, routes, middleware, config
• src/frontend/react-frontend – React code, components, pages, services, build configs
• Patterns:
• Backend follows an MVC-style separation: models in /models, controllers in /controllers, routes in /routes.
• Middleware layer for rate limiting and sanitization.
• Frontend organized by pages, components (common, specific, UI), interfaces, and services for API calls.
• Config files:
• .env_template/.env.production_template for environment variables
• package.json, Vite and TypeScript configs for frontend build
• package.json for backend dependencies
README for additional insights
• Technical stack callouts: Vite, React, Node.js, Express, Nginx (for reverse proxy / production), MongoDB.
• Team conventions: Git branching, commit messages, coding style.