What needed to change
A convincing technical assessment or prototype needs more than visual polish. It should have organized templates, usable navigation, mobile behavior and a clear way to change content.
How I worked through it
Building a maintainable foundation
I used a local WordPress environment to explore a clean theme structure and reusable frontend patterns rather than stacking everything into a single template.
Paying attention to interaction
The prototype explored responsive navigation, sensible content structure and simple interactive behavior without unnecessary dependencies.
Testing before presentation
Checking mobile experience, page behavior and development workflow was part of the exercise, not an afterthought.
What I learned
The more complicated a website feels to maintain, the more likely it is that the architecture needs simplifying. Good frontend work should be understandable after handover.