How suraj4127/pixelforge-dynamic-images works
Webengage Creative Studio lets internal users create layered image templates and render personalized PNGs through a public URL; accounts require email/password and verified mobile numbers. The main workflow is sign in or register, manage a template, then request a render with personalization values. Rendering retrieves template data and background imagery, composites text/image layers, and returns a PNG, with Redis and in-memory caches supporting repeated work. The graph reflects documented capabilities and sampled relationships; unsampled subsystems are included only where the README or source index establishes them.
Main entry points: auth.routes.js Account endpoints · template.routes.js Template endpoints · render.routes.js PNG render endpoint · app.js HTTP app
Components 22
Application entry
- Studio UI
public - Server process
src/server.js - HTTP app
src/app.js
Accounts and access
- Account endpoints
src/routes/auth.routes.js - Access guards
src/middleware/guards.js - Session handling
src/services/sessions.js - Password hashing
src/services/passwords.js - Phone verification
src/services/otp.js - User records
src/repositories/userRepository.js
Template studio
- Template endpoints
src/routes/template.routes.js - Template records
src/repositories/templateRepository.js - Page routes
src/routes/page.routes.js
Personalized rendering
- PNG render endpoint
src/routes/render.routes.js - Image loading
src/services/images.js - Memory caches
src/lib/cache.js
Storage and integrations
- Render metrics
src/lib/metrics.js - Schema setup
src/db/schema.js - MySQL
src/config/db.js - Redis
src/config/redis.js - S3 object storage
src/config/s3.js - WebEngage SMS
src/services/webengage.js
Other components
- Studio user
Connections 34
- Studio user → Studio UI: uses
README.md - Studio UI → HTTP app: requests pages and APIs
- Server process → HTTP app: starts
src/server.js - HTTP app → Account endpoints: mounts routes
- HTTP app → Template endpoints: mounts routes
- HTTP app → PNG render endpoint: mounts routes
- HTTP app → Page routes: mounts routes
- Account endpoints → User records: reads and writes
src/routes/auth.routes.js - Account endpoints → Password hashing: hashes and verifies
src/routes/auth.routes.js - Account endpoints → Session handling: sets and clears sessions
src/routes/auth.routes.js - Account endpoints → Phone verification: issues and verifies codes
src/routes/auth.routes.js - Account endpoints → WebEngage SMS: sends verification SMS
src/routes/auth.routes.js - Account endpoints → Access guards: checks admin access
src/routes/auth.routes.js - Access guards → User records: loads current role
src/middleware/guards.js - Access guards → Schema setup: ensures account schema
src/middleware/guards.js - Session handling → User records: resolves session user
- Template endpoints → Access guards: protects studio routes
src/routes/template.routes.js - Template endpoints → Template records: reads and writes
src/routes/template.routes.js - Template endpoints → Image loading: loads upload background
src/routes/template.routes.js - Template endpoints → S3 object storage: uploads background
src/routes/template.routes.js - Template endpoints → Redis: caches and invalidates templates
src/routes/template.routes.js - Template endpoints → Memory caches: clears image caches
src/routes/template.routes.js - Template records → MySQL: queries template rows
src/repositories/templateRepository.js - PNG render endpoint → Template records: loads template
src/routes/render.routes.js - PNG render endpoint → Schema setup: ensures template schema
src/routes/render.routes.js - PNG render endpoint → Redis: reads and caches renders
src/routes/render.routes.js - PNG render endpoint → Image loading: loads background and overlays
src/routes/render.routes.js - PNG render endpoint → Memory caches: uses image caches
src/routes/render.routes.js - PNG render endpoint → Render metrics: records render metrics
src/routes/render.routes.js - Image loading → Redis: uses shared cache
src/services/images.js - Image loading → Memory caches: uses local caches
src/services/images.js - Schema setup → MySQL: creates and updates tables
src/db/schema.js - Phone verification → Redis: stores verification codes
src/services/otp.js - Page routes → Access guards: gates pages
src/routes/page.routes.js