Project content model
Project records supply the catalogue and case-study pages. The build checks slugs, links and local assets before generating the site.
Personal website & project archive
A personal portfolio with detailed project case studies, technical experience, a guided assistant and a private enquiry form.

Overview
A personal website for understanding my work before starting a conversation. It connects software products, professional contributions and earlier projects with the decisions behind them, while keeping the route to contact simple.
Engineering contribution
Design brief
A personal portfolio presenting my projects, technical experience and contact information.
Technical details
Structured project records generate the pages and navigation. Server-side handlers validate enquiries and manage private storage.
Project records supply the catalogue and case-study pages. The build checks slugs, links and local assets before generating the site.
HTML, a locally hosted font and shared CSS carry the content. JavaScript adds filters, accessible navigation and motion controls without hiding the core pages behind an application shell.
The Node.js handler validates enquiries and saves them to PostgreSQL. Optional files use private storage; a saved enquiry and an accepted email delivery are reported separately.
Workflow
Browse selected work or filter the full project collection.
Read the scope, contribution and engineering decisions.
Use the guided assistant or open a project-specific enquiry.
Send an enquiry or choose direct email for the next conversation.
The assistant answers from the published portfolio. It does not expose private project records.
Verification
Generate the pages, check the server types and regression tests, then inspect the rendered site before publishing.
Resources
Emmanuel Mmanda
Find a published answer or ask Emmanuel directly.
Loading questions…
Need a more specific answer?
No questions yet. Browse the library to start.
Loading published answer…
Leave a comment