A portfolio with a reliable editing path
Bring a varied creative and technical practice into one coherent portfolio, with a practical way to update the content.
Project owner and visual direction, with AI-assisted development, migration and testing.
The challenge
The previous portfolio relied on an Express/MySQL service whose database stopped after the hosting trial expired. Administration became unreliable, and the public story needed to connect creative work with software projects.
The decisions that shaped it.
Give the content a clear structure
Present professional experience, learning and projects consistently. Keep creative artwork on Behance, while software projects use their own identities and direct links.
Separate reading from editing
Serve the public portfolio separately from the authenticated content service. Use GitHub sign-in for owner editing, with revision checks and restorable content history.
Preserve the existing routes
Redirect the old portfolio addresses to the current site. Keep professional content available in the initial HTML, and check the website against the reviewed CV files before a release.
What was delivered
- A published English/Arabic portfolio with responsive layouts and light/dark themes.
- A separate owner CMS with GitHub sign-in and content history.
- Permanent redirects from the previous portfolio addresses.
What carries forward
Content structure, editing and release checks need to agree; visual polish alone does not keep a professional profile consistent.