How indiehum/portfolio works
Main Components Structure
a. Portfolio Core
• Root-level components (index.html, StyleSheet, Font, Img)
b. Project Showcase Section
• Each sub-project should be represented as a separate module:
• FakeStore (E-commerce)
• QuizApp
• WeatherApp
• ToDoApp
• RockPaperScissor
• Others
Technical Architecture Elements
For each component, represent:
a. Frontend Architecture
• Static Assets (CSS, Images, Fonts)
• JavaScript Modules
• HTML Structure
• Utility Functions
b. Common Services Layer
• HTTP Request Handlers (httpReq.js)
• Authentication Services (auth.js)
• Utility Functions (validation.js, cookie.js)
Specific Project Patterns
Different architectural patterns used:
• FakeStore & FakeStoreOOP: Highlight both procedural and OOP implementations
• WeatherApp: Show Tailwind integration and build process
• QuizApp: Display multi-page architecture with state management
Component Relationships
Key interactions:
• Main portfolio navigation flow
• Project isolation and independence
• Shared resource usage
• API integrations (Weather API, FakeStore API)
Technical Stack Indicators
• Vanilla JavaScript
• CSS (including Tailwind for WeatherApp)
• HTML5
• External APIs
• Build tools (for WeatherApp)