Skip to main content

v0.1 - Portfolio Foundation

Setting up the foundational structure for a developer portfolio with Hugo

April 28, 2024 – Version 0.1.0

What if every website we built was a reflection of our values, not just our skills?

That’s the question that led me to start from scratch on this portfolio – not because the old one was broken, but because it wasn’t saying what I wanted to say. In a world where every digital interaction shapes how we think and feel, the platforms we build matter more than we realize.

You know that feeling when you’re staring at a blank canvas, excited and ready to create? That was me this week. But the challenge wasn’t just technical, it was realizing that every design decision, every color choice, every interaction pattern sends a message about what I value as a developer and as a human being.

Added

  • Base structure: Hugo foundation for speed, simplicity, and static site generation
  • Dark mode support: System preference detection to respect user comfort and reduce eye strain
  • Navigation: Main pathways About, Projects, Blog, Contact designed for clarity and purpose
  • Project structure: Content organization mapped for scalability and maintainability

Improved

  • Theme integration: Eliminated flash of unstyled content between pages with inline script placement
  • Performance: Streamlined CSS variables and removed redundant code for faster loading

Learned

  • Hugo theme customization: Direct template editing versus theme hooks, both approaches have trade-offs in maintainability and flexibility
  • Dark mode implementation: Complex interaction between localStorage, system preferences, and user choice requires careful state management
  • CSS architecture: Balance between reusable components and specific implementations, ongoing optimization for maintainability

Reflection

So here’s what really happened: I initially thought this would be about building a better portfolio. But it became about building a better digital experience.

The breakthrough came when I realized that every technical decision has a human impact. Dark mode isn’t just about aesthetics, it’s about respecting user preferences and reducing eye strain. Performance isn’t just about speed, it’s about not wasting people’s time or battery life. Accessibility isn’t just about compliance, it’s about ensuring everyone can access the information they need.

What fascinates me is how such seemingly simple features touch on fundamental questions about how we treat the people who use our software. Every line of code, every design choice, every interaction pattern sends a message about what we value.

The question isn’t whether we can build better websites – it’s whether we have the courage to care about the people who use them.

Next Steps

  • Responsive layouts optimized for all devices
  • Content development for About section
  • Project templates designed to showcase work effectively
**Every website we build is a statement about what we value.** What ethical considerations do you think about when designing digital experiences? How do you balance aesthetics with accessibility, performance with functionality? I'd love to hear your thoughts on how we can build websites that respect both users and the planet.