Designing, structuring and hardening a professional portfolio

A presentation, evidence and contact resource

The portfolio needed to evolve to make the professional positioning clearer, make evidence of work easier to find, and offer a straightforward way to get in touch. It is intended for recruiters, managers and operational contacts, as well as prospective partners.

It is delivered as a personal project, not comparable to a scalable enterprise information system. It is a practical demonstration of a method for simple website design, content structure, checks, and release.

Different audiences, one consistent standard

Selecting a foundation suited to an editorial portfolio

Separate editorial and technical foundations

The Astro framework has been retained, as it provides static generation and presentation code, and Content Collections to define content structures and consistency checks
In addition, Front Matter CMS has been added on top to provide a local editing interface while content is stored in Markdown collections.

Because Astro calls for a product-build approach, GitHub is also used to track changes. The static site is hosted by OVH.
The Contact form relies on Supabase and Brevo: the first handles server-side processing and enquiry data in line with the retention policy, while the second routes notifications.

This arrangement deliberately separates editorial content, presentation code, build controls, and publication. It makes responsibilities and checks easier to handle, including for non-dev users.

Identified constraint

From local editing to a checked release

1. Step 1

   Creation

   A new page is created by selecting a Content Type and its place in the existing site structure.

2. Step 2

   Editing

   Content is created or adjusted in the selected Markdown collection, using explicit structures and labels.

3. Step 3

   Preview

   Changes are reviewed locally to check rendering, links, language versions, and content that is still in draft.

4. Step 4

   Build

   Static generation validates the collections and produces a version that can be checked directly in a browser.

5. Step 5

   Control & validation

   Checks include expected rendering, routes, language links, and the absence of visible regressions. Each validated page has its draft status removed.

6. Step 6

   Publication

   The validated version is published online by SFTP. Separating draft, preview, and publication reduces the risk of an unintended early release.

A transferable working practice

Targeted, verified safeguards

An extensible editorial framework, with stated limits

The outcome is a bilingual portfolio with editable content, extensible case studies, and a documented workflow. Its editing model allows presentation to vary while maintaining overall visual consistency.
Local preview, build checks, and controlled publication make it possible to review a change before it goes live.

The safeguards remain proportionate and verifiable: they cover the site and its contact form in line with general security good practice, without claiming cybersecurity expertise.

Limit of the demonstrated scope

Planned developments

• Expand editorial publications over time.
• Run periodic accessibility and performance audits.
• Evolve editorial templates when Front Matter usability makes this worthwhile.