© Manish Choudhary. All rights reserved.

    All posts
    portfolio
    frontend
    animation
    engineering

    Building an Interactive Portfolio Without Losing the Engineering

    Manish Choudhary
    Thursday, October 22, 2026
    2 min read

    Building an Interactive Portfolio Without Losing the Engineering

    I wanted my portfolio to feel like more than a standard hero section followed by a grid of project cards. The challenge was to create a distinctive experience while still making the important information—my work, technical skills, and contact details—easy to find.

    The Goal

    The visuals should support the content, not compete with it. I experimented with an interactive keyboard, animated section transitions, project imagery, and motion that responds to the user's interaction.

    The keyboard concept gives the page a connection to software development: the keys represent technologies, while the rest of the site explains what I've actually built with them.

    Animation Is a Trade-Off

    Animations can make an interface feel considered, but every effect adds complexity. Several effects running at once can create jank, especially on less powerful hardware. A hover animation that looks great in isolation can also become distracting when repeated across an entire page.

    My approach is to keep motion purposeful, test interactions in the real page, and avoid changing unrelated effects when fixing a visual bug. That last part matters: a small styling fix should not break the keyboard animation, light theme, or responsive layout.

    What I'm Paying Attention To

    • Performance: keep animations smooth and avoid unnecessary work during pointer movement and scrolling.
    • Usability: make navigation and project details clear even when users ignore the visual effects.
    • Consistency: ensure the light and dark themes both feel intentional.
    • Maintainability: keep project content and shared configuration in data files where possible instead of duplicating it across components.

    What I'd Improve Next

    I'd keep testing on different screen sizes and lower-powered devices, simplify any effect that does not add much value, and make sure project descriptions reflect real implementation details rather than marketing language.

    A portfolio is itself a software project. It deserves the same debugging discipline as the applications it showcases.

    Back to all posts