How comppsyunion/nottinghamwall works
Project type and purpose
• This is a full-stack “University Campus Wall” application with three distinct clients—
– A WeChat Mini-Program (uniapp folder) for students and public users
– A Vue-based Admin Dashboard (admin folder) for management
– A Java Spring Boot Backend (backend folder) exposing REST APIs
• Purpose: allow students to post topics, comments, reports, orders, and admin to manage users, topics, comments, etc.
File structure
• Top-level modules:
– backend/ (three Maven modules: wall-common, wall-pojo, wall-server)
– admin/ (Vue3 + Vite web app)
– uniapp/ (Vue-style UniApp mini-program)
• backend: layered MVC
– wall-common: shared constants, exceptions, utilities (JWT, AliOSS, HTTP client)
– wall-pojo: DTOs, Entities, VO classes, MyBatis type handlers
– wall-server: Spring Boot app with config (Redis, OSS, Web MVC), controllers (admin/student), service interfaces & impl, mappers, interceptors (JWT), aspects, global exception handler, MyBatis XML mappers
• admin & uniapp:
– /src/api modules encapsulate HTTP request functions
– /src/views or /src/pages implement UI components, router definitions, Vuex/Pinia store (admin uses Vuex)
• Configuration & deployment: GitHub Actions workflows, pnpm/NPM lockfiles, Vite configs, docs in docs/ (VitePress-based documentation)
README for insights
• Confirms 3 parts: server-side, mini-program, management side
• Mentions external dependencies: WeChat Mini-Program test account, business reviews
• Provides API base URL, high-level snapshots of UI
• Points to deployment guides in docs/
Don’t overthink—capture every logical component
• Each Vue client’s router/store/api layers
• Each backend Maven module
• All external integrations (Redis, OSS, WeChat)
• JWT auth flow and AOP flow