How johan-smal/dev-portfolio works
Main Components
A. Frontend Layer:
• Static Assets (HTML, CSS, JS)
• HTMX for dynamic interactions
• TailwindCSS + DaisyUI for styling
• React/TSX templates for component structure
B. Infrastructure Layer:
• AWS Lambda for serverless compute
• API Gateway for request handling
• S3 for static file hosting
• Route53 for DNS management
• CloudFront (implied by the infrastructure setup)
C. Build/Development Layer:
• LocalStack for local development
• esbuild for bundling
• Terraform for infrastructure management
Rectangle with rounded corners: AWS Services
Hexagons: Build tools
Rectangles: Application components
Diamonds: External services/tools
Component Relationships to Highlight
Client Browser
• ↓ ↑
CloudFront
• ↓ ↑
API Gateway ←→ Lambda Function (Hono.js Server)
• ↓ ↑ ↓
Route53 S3 Bucket (Static Assets)
Important Architectural Patterns to Emphasize
• Serverless Architecture
• JAMstack approach (JavaScript, APIs, Markup)
• Infrastructure as Code
• Component-based frontend structure
Create three main sections:
Additional Notes
• Version/technology badges where relevant
• Separation between local development and production environments
• Role of Terraform in managing infrastructure
Remember to include annotations for:
• Security groups and IAM roles
• Environment variables and configuration
• Build and deployment workflows
• Local development setup with LocalStack
This will provide a complete picture of both the runtime architecture and the development experience.