Skip to content
Back to achievements

Achievements

Building a professional portfolio

Building a complete portfolio with Next.js, GSAP, bilingual i18n, GDPR compliance, analytics, and a technical blog.

Achievement summary

This summary provides the essential reading points. It does not replace the complete case study: scroll down to review the detailed context, steps, limitations, and critical review.

Context
This portfolio was rebuilt to meet the training assessment rubric while giving recruiters a clear view of the journey and achievements.
Challenge
Make a technical journey and projects assessable by a panel and readable by a recruiter without reducing evidence to a technology list.
My role
I handle its architecture, development, design, writing, testing, deployment, and maintenance, with human review of assisted content.
Key decision
Structure the site around bidirectional links between experience, skills, achievements, and evidence, in French and English.
Result
The site connects experience, skills, achievements, and evidence in a bilingual application with a technical blog, consent management, and assessment-oriented navigation.
Evidence
The published site, its Git history, the skill pages, and automated checks provide reviewable material for this achievement.View the detailed evidence

01

Presentation

I started this portfolio in March 2026 to present my work for the Expert in Software Engineering qualification. I also wanted recruiters to understand my role in a project without prior knowledge of Odoo, my company or the school’s rubric. I built the site around documented work examples, which readers can reach through my career history, skills or achievements.

A previous portfolio that had become insufficient. Before this reconstruction, I already had a portfolio and a GitHub profile page. A GitHub profile page can display an introduction, links, and code repositories on the platform used to host projects. These materials provided an initial overview of my activity but did not match the qualification examiners' expectations. In particular, they lacked the required level of writing, structure, and relationships between skills, experience, and achievements.

Showing my objective of becoming an experienced developer and Odoo specialist. This positioning is presented through my skills, current projects, and achievements. Articles about Odoo migration, business modules, and integrations show that I do more than configure an ERP. They explain how I analyze its code, adapt functions, automate processes, handle user feedback, and take ownership of structural changes. Together, they should make my progress toward becoming an experienced developer and an Odoo specialist capable of supporting Odoo-related decisions visible.

I handle design, code, writing and maintenance. The bilingual site also includes a technical blog for people facing problems I have worked through, such as an Odoo upgrade.

02

Objectives, context and stakes

Assessors needed to find ten skills, five achievements and my career history, then connect each skill to an example and an outcome. Recruiters needed to understand my profile quickly and choose the project they wanted to explore. I added an opening summary to each case study and links between related pages.

Separating assessment scope from personal enhancements. English translation and the blog provide professional value but could be postponed without making the portfolio non-compliant with the French rubric. Bilingual delivery broadens readership and the blog demonstrates my ability to share solutions. neither should delay a mandatory skill article or incomplete achievement. This distinction supports prioritization without abandoning the functions that will keep the website alive after examination.

The content needed to remain understandable on mobile, in both languages and with reduced motion. Technical articles had their own pages so readers could explore detailed analysis without making the assessment pages longer.

03

Risks and mitigation measures

A technology list can obscure who did the work. At the other extreme, documenting every detail can bury important decisions. I separated facts, my role and outcomes, then sought feedback on whether readers could trace each claim to an example.

Accidental publication of confidential information. I prepare evidence myself and can therefore make a redaction mistake or overlook a name in a background, URL, log, or metadata. Showing the material to the relevant people before publication adds a second check. Excerpts must also be reviewed in their final website form because a properly redacted file can be accompanied by a caption or text that indirectly reveals what the image hides.

A Codex first draft capable of distorting experience. Writing assistance may mistranscribe an oral answer, replace a term with a different concept, or remove a nuance incorrectly considered secondary. It can also produce a convincing explanation that does not match the facts. Generated text is therefore never a source. My answers, project files, approved evidence, and manual review remain the references that determine the published release.

A GDPR non-compliance risk with analytics. The General Data Protection Regulation, or GDPR, governs personal-data processing. Loading a measurement tool before consent, storing a choice ambiguously, or failing to provide an effective rejection would create legal and ethical risk. Analytics scripts must therefore remain disabled until the corresponding category is accepted, while necessary functions such as language or theme can operate independently.

04

The steps — what I did

Detecting language as soon as a visitor arrives. A Next.js proxy intercepts requests that do not yet contain a language and redirects them to the appropriate address. A proxy is a layer executed before a page is displayed. It first checks the NEXT_LOCALE cookie, which remembers an earlier choice, then the Accept-Language header sent by the browser, and uses French by default if no usable preference exists. The language switcher then replaces the first URL segment, preserves the rest of the path, and stores the preference for one year.

Separating server loading from interactive use of translations. Interface copy is centralized in two JSON dictionaries, one per language. JSON is a structured key-value format. Components executed on the server load only the requested dictionary, while a limited React context passes interactive components only the labels they need. This choice avoids duplicating copy in every component and requires both dictionaries to be updated whenever a new key is created. The localized layout also emits the document's lang attribute on the server, before hydration, for screen readers and search engines.

Modeling ten comparable skills. I defined ten records split between human and technical skills. Each one contains a shared score out of 100, a type, definition, anecdotes, self-assessment, development plan, and related achievements. The listing page turns the ten values into a radar chart — each axis represents one skill and distance from the center represents its relative level. This representation is not intended as a scientific measurement. It mainly makes each skill's place in relation to the others immediately understandable.

Turning the journey into a reverse-chronological timeline. The experience section first shows periods that end most recently, with “Present” at the top. When two periods share an end date, the latest start date breaks the tie. Every entry provides an initial reading level—period, position or diploma, organization, and logo—then responsibilities, description, and related links. Institution and company logos can point to their websites. A continuous vertical line and one marker per entry materialize this chronology on mobile as well as on large screens.

Links checked in both directions. Each skill profile links to the projects that supply its examples. Each case study highlights three skills and links to additional profiles beside the passages that document them. A test compares associations from both sides and checks that each has a documented example. Pages use those identifiers to generate links in both languages.

Developing a form validated in both browser and server. The contact form uses React Hook Form to manage fields and Zod to describe rules — name and message length, valid email address, mandatory reason, and a custom subject when “other” is selected. The same schema is executed again by a Server Action, a Next.js function running on the server. This double validation provides fast feedback without trusting data received by the server. Values are escaped before insertion into email to prevent a message from being interpreted as HTML code.

Building the consent banner myself. I did not install an external consent platform — the component provides “accept all,” “reject all,” and detailed preference management. It distinguishes cookies necessary for operation—language and theme—from optional audience measurement. The choice is stored locally, and an event immediately informs the analytics component. Google Tag Manager or Google Analytics is inserted only after consent for that category, technically implementing the GDPR consent principle, the European regulation protecting personal data.

Building several test levels. Vitest and React Testing Library verify isolated functions and components — language rules, form, anti-spam, consent, search, navigation, and reciprocal links. Vitest browser mode uses Chromium to check real behavior and selected visual snapshots, including the form, cookie banner, and language switcher. Playwright runs end-to-end, or E2E, tests that navigate the built application like a visitor. This combination covers both logic that can be tested quickly and journeys in which several layers interact.

05

The stakeholders — interactions

I showed several versions to my learning coach. One round of feedback led me to develop the examples on the skill and achievement pages. Another helped me move the career section higher on the homepage so readers could follow my progression before opening individual pages.

Relatives as informal interface testers. Relatives also browsed the website and viewed proposals created in Figma. An informal tester does not follow a written protocol with measurements — they use the interface freely and explain what they understand, appreciate, or consider improvable. Their feedback confirmed that the overall design was convincing and surfaced suggestions for interface improvement. I do not give these discussions a level of precision they did not have — they were qualitative observations, not a full usability study.

The CEO as authority over company evidence. Screenshots, excerpts, or information from my employer's projects cannot be published on my decision alone. I show the CEO exactly what I intend to use, already anonymized where necessary. They can approve it, reject it, or request a change. This control protects customers, internal data, company-owned code, and the organization's image. It defines what I can prove publicly without undermining the reality of the work presented.

06

The results

The site contains ten skill profiles, five case studies, six published articles and a detailed career history. Examples on the skill pages link to the associated projects, and each case study highlights the main skills I used. The site itself demonstrates this reading path.

A dated audit that surfaced a specific issue. On July 16, 2026, I audited 100 URLs with Lighthouse in mobile simulation. At the time, 98 pages scored at least 90 for performance, and the median was 96. Both CAP2vie pages scored 57. Video players loaded upfront were a major source of the slowdown. The audit guided the move to preview images that load the player after interaction. The figures describe the version tested at the time and provide a baseline for a new run.

An end-to-end contact check. In the checks recorded during development, test messages went through the form, server validation and Resend before reaching the destination inbox. That test confirms the flow worked in the environment used at the time. Real inquiries and final hosting configuration need their own check when preparing a new submission.

Technical learning centered on accessibility and compliance. The project made me work on topics I had explored less thoroughly before — consent, data protection, page semantics, motion preferences, keyboard navigation, metadata, and security policies. This progress goes beyond graphical integration. It taught me to treat a website as a product for real visitors, with responsibilities beginning before development and continuing after launch.

The assessment recognized the site’s structure and the quality of the examples. I used that feedback to make the case studies more concise, give my learning plans more detail and show my values through engineering decisions.

07

After the project

Asking two audiences to review the work. For a future submission, I would ask the learning coach to check the work against the rubric. I would then ask someone unfamiliar with Odoo and my background to read one case study and summarize the problem, my contribution and the result, pointing out where they found the evidence. Together these reviews could identify a missed criterion or a passage that still depends on oral explanation.

Dated wording to review regularly. Odoo versions, article counts, my declared level, objectives, and expressions such as “currently” can quickly become inaccurate. With every change, I will need to locate this information in both French and English releases, update related relationships, and rerun tests. Bilingual delivery particularly requires avoiding an update in only one language.

Checking the effect of deferred loading. I would repeat the audit under the same conditions as the July baseline for both CAP2vie pages and a comparison page. I would compare when the main content appears and inspect browser requests to confirm that the player loads only after consent and interaction. This would help isolate the effect of the video change and surface possible regressions elsewhere.

08

My critical review

In trying to address every criterion, I wrote case studies that were much too long. The assessor found the substance but had to read through many explanations to isolate a decision and its effect. I learned to offer a summary first and choose the facts that substantiate the contribution I describe.

Trying to animate the website too early. My main mistake was starting animation before stabilizing page content and structure. Animation quickly creates a sense of progress because its result is visible, but it depends on block size, order, and message. When those elements change later, the effect must be adjusted or removed. I therefore invested time in a finishing layer while the material it was meant to support remained insufficiently defined.

Integration coverage still to strengthen. An integration test verifies that several real parts of a system work together, such as the form, server action, anti-spam protection, and delivery service. The project has unit, component, and end-to-end tests, but external dependencies are often simulated. Resend, reCAPTCHA, and rate limiting are replaced with mocks, meaning controlled test versions. Dedicated scenarios validating the boundaries between the deployed application and its services more faithfully are therefore still missing.

For the next revision, I would ask someone unfamiliar with my projects to read a case study earlier and explain back my role, the outcome and its evidence. Automated tests check the site and its links. A reader can help check understanding, which was one of the goals from the start.