How dendianugerah/reubah works
Main System Components
a) Web Interface Layer:
• Static frontend components (templates directory)
• HTML templates and JavaScript handlers
• TailwindCSS integration
b) Server Layer:
• Main server component (cmd/server)
• Request handlers (internal/handlers)
• Input validation (internal/validator)
c) Processing Layer:
• Document processor
• Image processor
• Background removal service (planned feature)
• Optimization service
d) Storage Layer:
• Temporary storage system (tmp directory)
• "no permanent storage" architecture
Component Relationships
• User → Web Interface → Server Handlers → Processors → Temporary Storage
Specific Implementation Details
a) Document Processing Pipeline:
• Input validation
• Format conversion (show supported formats matrix)
• PDF merging capabilities
• Output delivery
b) Image Processing Pipeline:
• Format conversion
• Optimization
• Batch processing
• Background removal (marked as future feature)
Technical Stack Representation
Technologies:
• Go (1.22+)
• LibreOffice integration
• Docker containerization
• TailwindCSS
• Native JavaScript
Architectural Patterns
Emphasize:
• Clean architecture (internal/pkg separation)
• Handler-Processor-Validator pattern
• Stateless processing model
• Containerized deployment
a) Frontend Components:
/templates
• components/
• pages/
• js/
b) Backend Services:
/internal
• handlers/
• processor/
• validator/
c) Supporting Infrastructure:
• Docker container
• Temporary storage volume
• LibreOffice service
Important Notes
• Isolated processing environment
• Immediate delivery mechanism
• Cleanup processes
• Validation checkpoints
This system design should emphasize the project's core strengths: its clean architecture, efficient processing pipeline, and security-conscious design with no permanent file storage.