How strange500/nextportfolio works
Project type and purpose
• This is a full-stack (mostly frontend-heavy) portfolio web application built with Next.js (React) for server-side rendering and static site generation. It showcases projects and personal info, deployed via Docker on a home server.
File structure
• Top-level:
• app/ – Next.js 13 “app router” pages and global layout, CSS imports
• components/ & components/ui/ – React UI components and primitives
• lib/ – shared utility functions
• public/ – static assets (logo, images)
• Dockerfile, compose.yml, devbox.json, shell.nix – containerization & reproducible dev environment
• next.config.ts, tailwind.config.ts, postcss.config.mjs, tsconfig.json – framework and build configs
• Notice no backend API folder, so the “server” is the Next.js runtime serving pages and assets.
README for additional insights
• Frameworks: Next.js, React, Node.js
• Styles: CSS Modules, Tailwind CSS
• Deployment: Docker on a personal server
• No external database—static content or markdown/docs images under docs/.
Detail is key
• Both build-time (Tailwind compilation, PostCSS, TypeScript compilation) and run-time (Node.js serving pages) steps
• Do not oversimplify: show public assets, docs folder, theming provider, utility library