Problem
The portfolio is a single page with project thumbnails but no depth. There are no case studies explaining what problems were solved, what decisions were made, or what the outcomes were. A potential client or employer cannot evaluate the quality of work from a screenshot alone.
What needs to change
- Create dedicated case study pages (or sections) for each major project:
- dumuwaks — what it is, the problem it solves, tech stack, key decisions, outcome
- online-shop — same structure: problem, approach, tech, results
- transittag — same structure: problem, approach, tech, results
- Each case study should include:
- Project overview (1-2 sentences)
- The problem / client need
- Approach and key technical decisions
- Screenshots or demo links
- Outcome or current status
- Link from the main portfolio page to each case study
Why it matters
Case studies are what convert visitors into clients. They show you can think, not just code. A single-page portfolio with thumbnails says "I built things." Case studies say "I solved problems." That is the difference between a portfolio and a sales tool.
Problem
The portfolio is a single page with project thumbnails but no depth. There are no case studies explaining what problems were solved, what decisions were made, or what the outcomes were. A potential client or employer cannot evaluate the quality of work from a screenshot alone.
What needs to change
Why it matters
Case studies are what convert visitors into clients. They show you can think, not just code. A single-page portfolio with thumbnails says "I built things." Case studies say "I solved problems." That is the difference between a portfolio and a sales tool.