How otman-dev/otman-portfolio works
Project type and purpose
• This is a full-stack, content-driven portfolio website built with Next.js 13’s App Router.
• Purpose: serve a dynamically generated, highly interactive portfolio (“frontend”) and power two serverless API endpoints (“backend”):
– AI-powered chatbot (Groq SDK)
– Blog feed integration (RSS2JSON)
File structure
• Top-level config & assets:
– next.config.ts, tailwind.config.js, tsconfig.json – Next.js, Tailwind & TS setup
– public/ – static assets (PDF resume, images, logo)
• src/app/ – App Router entry:
– layout.tsx, globals.css, motion-utils.css – root layout & global styles
– page.tsx – homepage server component
– api/ – serverless functions: /api/blog/* and /api/chat/* (speech, unified)
• src/components/ – React components:
– sections/ – UI for each portfolio section (About, Work, Skills…)
– ChatComponent, SpeechToTextChat – client-side chat UI
– FloatingNavigation – client navigation UI
• src/context/ – React Context (NavigationContext) for state
• src/utils/ – static data (personal, projects, skills, etc.), custom hooks, TS types
README for additional insights
• Tech stack: Next.js 15 App Router, React 19, TypeScript 5, Tailwind 4, Framer Motion
• Architecture highlights: server components vs client components, serverless API routes, context & hooks, static vs dynamic content, AI & RSS integrations