Understand before evaluating
Personal context, technical capability, qualifications, and contact information needed separate but connected routes.
Implemented self-directed projectLive and maintained
Designing and shipping a bilingual portfolio platform
I designed and developed this portfolio as a maintained software product connecting personal context, professional evidence, projects, credentials, knowledge guides, and contact paths across English and French.
Built with HTML, CSS, JavaScript, automated validation, and a version-controlled GitHub Pages release process. This is a self-directed project, not a client commission.
Technology portfolio
Evidence, clearly organized.
EN / FRReciprocal bilingual journeys
34Public routes validated on 22 August 2026
CIAutomated checks on releases
LiveDeployed with GitHub Pages
Product problem
One profile, several kinds of evidence
A résumé-style homepage could not explain three disciplines while keeping professional experience, implemented work, representative workflows, and learning projects distinct.
Make every claim proportional
The interface labels what each artifact proves so self-directed and learning work is never presented as client delivery.
Maintain equivalent journeys
English and French visitors need reciprocal routes and natural localized content without maintaining two disconnected products.
Keep the product resilient
The public experience must remain fast, readable, and navigable before progressive JavaScript enhancements run.
Front-end architecture
A static system with automated safeguards
Shared assets connect bilingual HTML routes to local validation, continuous integration, and production deployment.
- Bilingual routesFocused pages and reciprocal language paths
- Shared assetsCSS, JavaScript, images, data, and documents
- Local validationStructure, links, parity, budgets, and routes
- GitHub ActionsSyntax, behavior, and static-site checks
- GitHub PagesVersioned production deployment
Selected decisions
Design choices that support maintenance
Personal entry, professional depth
About became the homepage while evidence-heavy recruiter content remained in Portfolio, Projects, Certifications, and case studies.
Content before interaction
Semantic HTML provides the foundation; scripts enhance themes, filters, contact assistance, and measurement.
Layouts change instead of shrinking
Components move from three columns to two and one, wrap safely, and preserve readable decision order.
Shared patterns, natural language
Registered page pairs and automated checks reduce structural drift while French content remains professionally adapted.
Accessible and privacy-conscious
Safeguards built into the interface
The implementation treats accessibility and privacy as engineering constraints, not decorative claims.
Multiple ways to perceive and operate
Semantic landmarks, heading order, skip links, keyboard controls, visible focus, form labels, live status regions, and reduced-motion handling support a wider range of use.
Measurement remains optional
The Google tag stays unloaded before opt-in. GPC and DNT force denial, and custom events exclude form values, messages, query strings, and custom user identifiers.
Quality engineering
A release is not complete when it only works locally
The validator and CI workflow protect routes, resources, bilingual relationships, accessibility markers, metadata, performance budgets, and production readiness.
- JavaScript syntax and assistant behavior checks
- Internal links, documents, images, JSON, XML, and HTTP routes
- Canonical, hreflang, structured-data, and sitemap relationships
- Bilingual component parity and locale-safe navigation
- Protected resources and front-end performance budgets
Evidence boundary
What this project does—and does not—prove
It demonstrates a public static product, front-end decisions, bilingual maintenance, validation, and disciplined releases. It does not demonstrate client delivery, authenticated application flows, a database service, team development, or enterprise scale. Accessibility safeguards are implemented, but no formal certification is claimed.
Continue the conversation
Need someone who connects UX, front-end implementation, and disciplined delivery?
I am open to roles, internships, and projects involving accessible interfaces, maintainable front-end work, automation, or multidisciplinary technology delivery.