How done-0/jank works
Project type and purpose
• This is a full-stack, modular blog system called “Jank”
• Backend: Go + Echo framework
• Frontend: React + TypeScript + Vite + TailwindCSS
• Purpose: provide a lightweight, extensible, JWT-secured blog with posts, categories, comments, accounts, plus caching, OpenAPI docs, containerized deployment.
File structure
• Top-level:
• Dockerfile / docker-compose.yml / nginx.conf → containerization & reverse proxy
• configs/ → runtime & hot-reload (Air) settings
• cmd/ & main.go → server bootstrap
• internal/ → core backend modules (low-level, non-exported)
• db (database connection, migrations)
• redis (cache layer)
• logger, error, global → foundational services
• middleware → CORS, JWT auth, logging, recover, CSRF, XSS, Swagger
• model → ORM entities for account, post, comment, category, associations
• utils → reusable helpers (JWT utils, markdown renderer, email, validation)
• pkg/serve/ → high-level HTTP handlers
• controller (DTOs + request handling)
• service (business logic)
• mapper (convert model→VO)
• pkg/router/ → Echo routing setup & grouping
• vo/ → view objects (response payloads)
README for additional insights
• Confirms layered design (router → controller → service → data layer)
• Lists external services: SMTP email, object storage (MinIO), Redis cache
• Mentions security: JWT auth, CSRF, XSS protection, CORS
• Highlights extensibility (plugin system forthcoming)