How abdul-ahad2/plagiarism_detection_frontend works
Project type and purpose
• This is a full-stack web application built with Next.js (using the new App Router).
• The README confirms it’s a Next.js app bootstrapped via create-next-app, intended for user authentication (login/register) and a role-based dashboard (researcher, student, teacher).
File structure
• Top-level:
• package.json, next.config.mjs, eslint.config.mjs, etc. – configuration & build scripts.
• public/ – static assets (images, fonts).
• src/app/ – Next.js App Router directory.
• Inside src/app/:
• (public)/ – root-level public pages (login, register, landing).
• dashboard/ – protected area with sub-folders per user role: researcher, student (with analytics, report, upload, settings), teacher.
• layout.js files define shared UI wrappers at each route segment.
• page.js files are route entry points.
• src/components/ – reusable React components (navbars for each role, report cards, footer, etc.).
README
• Confirms Next.js, dev commands, use of next/font for font optimization.
• Mentions Vercel as a preferred deployment target (implying serverless functions / ISR possible).
Elements
• Labels: Client, Next.js App, CDN, Auth Service, Database
• Request/Response flows (Client → App → Data Services → App → Client)
• Static asset retrieval (App → CDN → Client)
• Frontend/UI (e.g., blue rectangles)
• Server / Business Logic (e.g., green rectangles)