Web engineering / Personal project
An engineering portfolio
This portfolio brings selected work, engineering capabilities, and contact information into a single reading path. The redesign replaces a service-package landing page with a personal engineering website, while retaining its existing PHP foundation.
- Role
- Personal portfolio · design & implementation
- Period
- 2026
- Status
- Prototype
- Stack
- PHP / JavaScript / CSS
- Team context
- Personal project
The problem
The previous site put broad services and fixed-price packages ahead of engineering work. Its projects depended on JavaScript to appear, and its templates produced multiple document structures on one page. The redesign needed a clearer reading order and a more dependable technical foundation.
My contribution
The implementation reorganizes the homepage around work, expertise, approach, and direct contact. Shared PHP templates render the content, while a small JavaScript file handles navigation state and mobile-menu keyboard behavior. Project content and publication settings live in one structured dataset.
Architecture & key decisions
Keep the existing stack. PHP renders complete pages without a frontend framework or a build step. This reduces deployment requirements and keeps the core reading and navigation experience available without JavaScript.
Separate content from presentation. A shared project dataset supplies cards and case studies, so titles, status labels, and technology lists stay consistent.
Use progressive enhancement. Native links work first; JavaScript adds active-section tracking, focus management, and menu dismissal. CSS handles responsive layouts and reduced-motion preferences.
Challenges & solutions
Old section links still need a useful destination. Legacy anchor aliases preserve navigation, and the router redirects former PHP page URLs to the relevant sections.
A stronger portfolio cannot come at the expense of factual accuracy. Unconfirmed employment, current availability, private projects, and résumé publication are withheld rather than filled with invented details.
Results
The redesign provides server-rendered project content, individual case-study routes, a custom 404 page, and a consistent responsive interface. The prototype uses local assets and does not require a database, tracking service, or JavaScript framework. Field performance and hiring outcomes have not been measured.
What I’d improve
The next content improvement is a set of approved product case studies with genuine screenshots and specific engineering decisions. That evidence is more useful than adding decorative features or increasing the number of project cards.
Explore the implementation
The homepage demonstrates the reading order, responsive components, and navigation described here.
Explore the portfolio