Projects and evidence

Show the constraints as clearly as the outcome

Useful project work explains the context, the decision, the trade-offs and what was actually verified.

Discuss your needs

Published projects

Systems that cross product boundaries

These pages are driven by structured content: they can be expanded, ordered, illustrated and connected to related software from Drupal.

Cross-functional project

Association payments and reconciliation

Connect forms, payment providers and CiviCRM contributions without confusing browser return with accounting state.
Explainable states, replayable events and a CiviCRM contribution retained as the business reference.

Delivered product

Cross-entity search in CiviCRM

Retrieve heterogeneous entities quickly without moving permissions or the source of truth outside the CRM.
A derived index, explicit scopes and observable change recovery.

Delivered product

Field control and digital wallet

Extend registrations, sessions and access rights into mobile applications capable of operating offline.
Responsibility distributed across CRM, field client and wallet, with idempotent synchronisation.

Specific experience

Component-based bilingual Drupal platform

Build an editable French and English website without hard-coding commercial content into the theme.
Canvas pages, reusable components and structured content types on a multisite-ready foundation.

Cross-functional project

International web coordination and cost optimisation

Coordinate an international WordPress ecosystem, newsletters and digital spending without losing operational continuity.
A shared view of websites, campaigns and costs, with traceable decisions across international teams.

Specific experience

HTMX qualification journey and accessible payment

Guide individuals, companies and other audiences through HTMX cards before sending each situation to the appropriate form or final payment state.
A progressive journey that qualifies before routing, retains the user’s choices and treats payment as only one of its final states.

Types of evidence

Present each experience at the right scale

The same Drupal structure now distinguishes cross-functional projects, delivered products, specific experiences and open-source contributions.

Cross-functional

Multi-system coordination

Governance, providers, budget, content, integrations and operations brought into one trajectory.

Delivery

A product actually delivered

Scope, deliverables, environment, acceptance and observable limitations.

Experience

Specific engagement

A clearly bounded incident, migration, on-site delivery, integration or architecture decision.

Open source

Verifiable contribution

Upstream project, role, repository, merge request or release without confusing participation and ownership.

Case-study format

Evidence, not just a gallery

Future case studies may be concise, but they will always separate findings, action and verification level.

01

Context

Organisation, users, dependencies and operational risk.

02

Decision

Selected architecture, scope and explicitly accepted trade-offs.

03

Verification

Testing, deployment, observation and remaining limitations.

Your context

The next project starts with a real constraint

Explain what is blocked before looking for the name of the solution.

Discuss your needs