How shaukinkhan477/newsletter-creator-app works
Project Type & Purpose
• This is a full-stack newsletter management platform.
• Frontend: Angular 17 SPA with NgRx, internationalization, accessibility, Cypress e2e and Jest unit tests.
• Backend: Node.js + Express REST API and Apollo GraphQL server, MongoDB (Mongoose), Passport.js for Google OAuth, JWT auth, node-cron for scheduling, Nodemailer for email dispatch.
Main Components
a. Frontend Application
• Angular client served by ng serve or Docker + Nginx.
• Feature modules: Auth, Posts (Newsletters), Subscribers, Templates, Analytics.
• State management via NgRx (store slices: auth, posts, subscribers).
• HTTP interceptor for JWT.
b. Backend Services
• Express + Apollo Server listening on server.js.
• REST endpoints under /api/* (auth, posts, subscribers).
• GraphQL endpoint at /graphql.
• OpenAPI docs served at /api-docs.
• Middlewares: JWT guard, Passport Google OAuth strategy.
• Cron job (cron.js) for scheduled dispatch.
c. Database
• MongoDB via Mongoose models (User, Post, Subscriber).
d. External Services
• Google OAuth (Passport.js).
• SMTP provider (Mailtrap or other) via Nodemailer.
• Optional third-party tracking (Google Analytics, Meta Pixel).
e. DevOps & CI/CD
• Dockerfiles for frontend & backend.
• docker-compose.yaml orchestrating backend, frontend, MongoDB.
• GitHub workflows: ESLint, SonarQube, CI/CD pipeline.
Relationships & Data Flows
• User ↔ Angular SPA: login/signup, dashboard interactions.
• SPA → Backend:
• REST calls for CRUD and scheduler operations.
• GraphQL queries/mutations for per-user data.
• JWT token in Authorization header (via interceptor).
• Backend → MongoDB: data persistence.
• Cron → Backend logic → MongoDB to fetch scheduled posts → Nodemailer → SMTP.
• Backend → External OAuth provider → user profile → JWT issuance.
• Frontend analytics dashboard reads metrics from REST/GraphQL.
Architectural Patterns & Design Principles
• Frontend: Feature modules + shared components, unidirectional NgRx state, HTTP interceptor pattern.
• Backend: MVC/Router-Controller-Service pattern, middleware pipeline, dual API layer (REST + GraphQL).
• Separation of concerns: scheduler isolated in cron.js, auth logic in passport.js & middleware, docs in openapi.yaml.
• Containerization for consistency across environments.