How tekdi/all-saas-admin works
Project Type and Purpose
• From the README (“Shiksha is a next-generation scalable open-source learning solution for teachers”) and the file tree (Next.js app, pages/, pages/api/, React components, services), this is a full-stack (mainly front-end with a thin Next.js API layer) Admin application.
• It is built with Next.js (React + Node) and TypeScript, serving server-side‐rendered and client‐side pages and exposing serverless API routes for authentication, file uploads, and proxying requests to backend services.
File Structure
• Top-level config: .env, next.config.mjs, next-i18next.config.js, app.config.ts – environment, i18n, build targets.
• /src/pages – Next.js pages for UI (SSR/SSG) plus /api subfolder for serverless functions.
• /src/components – Presentation/UI layer (modals, tables, forms, layout).
• /src/services – Client abstractions (RestClient + interceptors) and hooks/ methods calling external backend microservices (CohortService, UserService, MasterDataService).
• /src/store – Client state via Zustand/React context (AuthContext, stores for user, course planner, taxonomy).
• /public – Static assets and locale JSON for i18n.
• /__tests__ + jest.config.ts – Unit tests for components and helpers.
• CI/CD: GitHub workflows in .github/workflows for dev, staging, prod deployments.
README for Additional Insights
• Confirms Next.js boilerplate, Node v18+, npm v10+.
Elements
• From Browser to Next.js Pages & API routes.
• From API routes to External Backends.
• From Services to Stores & Components.
• Blue for UI components
• Green for server‐side functions/API
• Orange for external services/datastores
• Purple for CI/CD pipeline
Final Advice
• Be exhaustive: include i18n, theming, testing, and CI/CD workflows as separate side‐bars or callouts.
• Review with the team to ensure each external microservice is represented and that environment variables (.env) point to the right endpoints.