Skip to content
← All projects

Development · Product

This portfolio

The site you are reading: a complete, up-to-date CV that I can edit by clicking directly on the page.

  • 6checks before every release
  • 94job keywords present in both languages
  • 2languages, plus a text version for AI
Role
I wrote the brief, the content rules and all the text. The site was built with Claude Code, under my direction.
Period
August 2026 — ongoing
Status
Functional
Team
Personal project
julienfleuridas.com
Home page of julienfleuridas.com, with Julien's name, his tagline and the logos from his background.
Home page of julienfleuridas.com on a phone.

At a glance

  1. 1The problem

    A one-page CV does not say everything, and a portfolio often ends up full of skills without examples and numbers without context.

  2. 2Solution

    A site that tells the whole story, where every skill is linked to a role or a project, and whose content rules are checked automatically before every update.

  3. 3The result

    A recruiter finds everything in one place, in French and English, and the content stays reliable update after update.

Where it stands · Live at julienfleuridas.com since 1 October 2026. Every update passes the checks before it is published.

In pictures

julienfleuridas.com
Home page of julienfleuridas.com, with Julien's name, his tagline and the logos from his background.
The home page, on a computer.
Home page of julienfleuridas.com on a phone.
The home page, on a phone.

Why this site

A one-page CV does not say everything. You cut the details, the projects, what you really did in a role. And a portfolio has the opposite problem: it ends up full of skills without examples and numbers without context, because each small shortcut seems reasonable at the time.

I wanted one place where my whole background can be read, in French and English, and stays reliable update after update.

How it is built

Rather than relying on my own discipline, I had the rules checked automatically. A project without a status, a role, evidence or at least one limitation does not get through. A skill must be linked to a role or a project. A number must have its context.

And when something is refused, the message says which file and which field to fix.

Studio mode

While reading the site, I can switch on a Studio mode, click on any block and write what I want to change. The request goes out with the text on screen and the exact place in the content to edit. That is how I improve the site: by reading it the way a recruiter would.

Readable by AI

A text version of the whole site, generated from the same content, lets an AI assistant read it without getting lost in the layout. It updates with the rest.

Show technical details

Content kept separate

All the text lives in content files, never in the code. Adding a project requires no change to the site.

Six checks before every release

Content (its shape, both languages being present, the links between skills, projects and roles), job keywords, sensitive data (keys, passwords, unexpected addresses), links, types and code quality.

Two languages

Every page exists in French and English. A project published in only one language blocks the update.

What I did

  1. 01Needs definitionI wrote a complete brief: who the site is for, what it must show, and what must never be published.
  2. 02ArchitectureI had the content separated from the code, so I can add a project without touching the site.
  3. 03Rule designI turned the content rules into automatic checks that block an update.
  4. 04Assisted developmentThe interface, both languages and the checks were built with Claude Code.
  5. 05DocumentationI wrote a guide explaining how to add a project and what the site refuses.

Numbers

6

checks before every release

content, keywords, sensitive data, links, types and code quality

Source · check scripts run before every release

94

job keywords present in both languages

the terms from the job ads I target. If one is missing, in French or English, the update is blocked.

Source · the repository's keyword check

2

languages, plus a text version for AI

a project published in only one language blocks the update

Source · repository translation parity check

Evidence

  • Content rules are checked

    verified

    A project without a status, a role, evidence or a limitation does not get through. These are not guidelines, they are automatic checks.

    Source
    repository content schema
    Verify with
    Deliberately removed a required field, then saw the update fail.
  • No number without context

    verified

    Every number has its context and its source. A number that cannot be checked is never presented as proof.

    Source
    repository evidence components
    Verify with
    Read the rules for numbers and how they are displayed.
  • No sensitive data published

    verified

    A check blocks the update if a key, a password, an unexpected address or a path from my computer appears in the content.

    Source
    repository detection script
    Verify with
    Ran the check across all published content.

Limitations

  • Project screenshots are taken by hand. They do not update themselves.
  • The display is checked by hand, without automated browser tests.
  • The checks cover content, not design: nothing prevents a badly designed page.

What I take away

  • Writing the rules before the content paid off straight away: the first case studies were rejected by the checks, for real reasons.
  • Making a field mandatory, like a project's limitations, forces you to look honestly for what does not work yet.
  • Being able to click on a block to request a change makes all the difference: I fix the site while reading it, the way a recruiter would.

What it could bring to a company

  • Any team publishing structured content (product sheets, documentation, careers pages) can check its quality rules automatically rather than in a style guide.
  • A compliance team can block any publication containing sensitive data in the same way.
TechnologiesNext.jsTypeScriptZodMDXTailwind CSS

Does this project speak to you?

Let's talk about what I could bring to your team.

Get in touch →