How oanaspatacean/bookishhub works
Project type and purpose
• From the file tree and minimal README, we see “BookishHub” is a full-stack Next.js application.
• It provides user-facing pages (PDF upload/breakdown, language lessons, account management) and an admin console (user, PDF, lesson, assessment management).
• It exposes numerous RESTful API routes under app/api/... for language processing, authentication, payments, PDF summarization, etc.
File structure
• Top-level “bookishhub/app” holds Next.js “app router” pages. Subfolders divide into public routes (page.tsx) and dynamic routes ([fileId], [languageId], etc).
• The “app/api” directory defines API endpoints—grouped by feature (auth, payment, language, admin, PDF).
• “components” contains reusable React UI pieces. “lib” contains server-side utility modules (database, authentication, OpenAI, S3, payment).
• “prisma/schema.prisma” defines the database. Config files include Next.js, Tailwind, ESLint, TS.
Additional README insights
• Although the README is empty, the file names imply integration with:
• A relational database via Prisma
• AWS S3 for PDF storage
• OpenAI for summaries, translations, pronunciations
• Stripe (or similar) via lib/payment.ts for membership
• Unsplash / YouTube for media