How zignuts-ai/postgen-app works
Project type and purpose
• This is a full-stack, SSR/SSG-capable frontend application built with Next.js. It functions as an AI-driven content generator (“PostGenAi”) that summarizes and repurposes news via an external API.
• The repository contains only the frontend; all data and AI processing is offloaded to external HTTP APIs. It uses Next.js for routing/SSR, Tailwind and MUI for styling, and React contexts/hooks/store for state.
File structure to spot architectural zones
• Top-level:
• Dockerfile, nginx.conf, Jenkinsfile → Docker-based container build + CI/CD
• next.config.js, .env.sample → SSR/config
• public/ → Static assets
• src/pages/ → Next.js route handlers & page components
• src/api/ → HTTP client wrappers
• src/store/, src/queries/ → Client-side state & data-fetching layers
• src/@core/, src/components/, src/views/ → UI component libraries, layouts, views
• No /pages/api directory: there are no Next.js serverless functions; all dynamic data calls go to an external base API (NEXT_PUBLIC_BASE_API_URL).
README for additional insights
• Tech stack: Next.js, Tailwind CSS, MUI
• Standard dev/build scripts (npm run dev / build)
• ENV var NEXT_PUBLIC_BASE_API_URL points to your AI-service endpoint
• Structure summary matches the file tree.