How mynameiskayky/project-cubevis works
Project type and purpose
• This is a full-stack (in this case, front-end–focused) React application built with Next.js (v13+) and the App Router.
• Its purpose is to manage “projects” and “tasks,” with UI modals for creating sections, tasks, subtasks, attaching links/images, and commenting.
File structure
• Top-level config files: next.config.js/ts, tsconfig.json, tailwind.config.ts, eslint.config.mjs, postcss.config.mjs
• “public”: static assets
• “src/app”: Next.js App Router directory, with route segments:
• layout.tsx – global layout (header/sidebar/globals.css import)
• page.tsx – landing page
• /projects/page.tsx – projects list
• /projects/[id]/page.tsx – project detail view
• “src/components”:
• project/* – components for project pages (headers, sections, tasks, modals)
• task/* – components for task items (cards, subtask lists, comment lists, modals)
• ui/* – generic UI primitives (buttons, dialogs, inputs, sidebar, tooltip, etc.)
• “src/contexts”: ProjectContext.tsx – React Context for project/task state and actions
• “src/hooks”: custom hooks (e.g., useMobile)
• “src/lib”: utilities (utils.ts)
• “src/types”: TypeScript types
• No backend code or API routes in this repo—data likely comes via external API or local storage (to be confirmed or stubbed).
README for additional insights
• Standard Next.js boilerplate README
• Deployment target: Vercel
Elements
– Clear labels: “App Router,” “Layout,” “ProjectsList Page,” “ProjectContext,” etc.
• Browser → App Router
• Router → Layout → Page → Components → Context/API
• Purple for Context + Hooks
Detailed capture of essential elements
• Break the “Components” group into sub-areas: project vs. task vs. ui
• Call out modals and overlay components as part of the UI layer
• Global CSS and Tailwind as a separate styling cross-cutting concern
• If an external API exists, show it as a separate service (or placeholder)