Discuss your needsLet’s talk
EN
DTSC / Our members / Samuel Aulotte

Special issue, case study

Website DTSC

Five versions of the same site. And the voice of the client found again.

Making an ecosystem readable onlineConsulting and servicesApplied researchSMEs

Role
Design, development, coordination of reviews
Period
From the original WordPress sites to November 2026
Team
Alone at the controls, eleven members as reviewers
Method
Lean, Scrum and Agile, applied to the project
Special issueWebsite DTSCThe DTSC website, version after versionS. AulotteNo. 18 18Website DTSCH.S.
5versions84commits11reviewers453pagesLean, Scrum, AgileVoice of the client

This special issue tells the story of a project more than of a product. Three separate sites became a single entry point for the ecosystem, in five versions. I learned WordPress, React, Next.js and Three.js along the way, then learned to take things away. Above all I learned to steer: having each page reviewed by the person who knows it, publishing often, going back when the effect took over from the message.

5versions, from WordPress to paper
84commits in four weeks for the universe
11ecosystem members as reviewers
453pages online, in three languages
01

Context

DTSC is a Liège-based ecosystem for consulting, project management, training and applied research. It is organised into three hubs: LUCID advises, SPARK delivers, BRAIN innovates.

A systems, network and security engineer at DTSC, I also look after its websites. At the start there were three, each at its own address; a fourth, spark.dtsc.be, was planned but never saw the light of day, for lack of time in-house. The project: to turn them into a single entry point, without losing what each one said, and without ever speaking in place of the ecosystem.

  • Designing the reading path and the architecture
  • Developing each version, testing it, publishing it
  • Having each page reviewed by the person concerned
  • Arbitrating between the effect and the message
3addresses at the start
dtsc.bebrain.dtsc.belucid.dtsc.bespark.dtsc.be
+ a fourth one planned, never launched
1entry point at the end
3hubs, one voice
LUCIDSPARKBRAIN
02

Five versions of the same site

Each version answered what the previous one lacked. None was thrown away: each left something to the next.

01
dtsc.be

The original site

dtsc.be

dtsc.be
WordPressAvadaContact Form 7

The ecosystem’s first site, which stayed online until the switchover of November 2026. I learned WordPress for the occasion: theme, pages, forms, audience measurement.

Research had its own site. The ecosystem spoke at two addresses.

What was missing
02
brain.dtsc.be

The laboratory

brain.dtsc.be

brain.dtsc.be
WordPressAvada

The BRAIN laboratory’s site, of the same kind: projects, team, alumni, student certificates, pages for companies, researchers and students.

Same family, another address, another story. No link with consulting.

What was missing
03
lucid.dtsc.beHome page of the LUCID site: “Le format d’un freelance. La puissance d’un cabinet.”, menu in four languages

The consulting hub

lucid.dtsc.be

lucid.dtsc.be
React 18ViteServer-side rendering4 languages

More advanced technically: 204 routes pre-rendered on the server, four languages, careful search engine optimisation. At the centre of the home page, the SME; the LUCID areas of expertise in orbit around it.

One more hub, at its own address. And spark.dtsc.be, planned, never saw the light of day for lack of time in-house.

What was missing
04
samaulotte/DTSC-WebsiteHome page of DTSC Universe: WebGL galaxy with SPARK, LUCID and BRAIN around the DTSC logoLiving 3D city of the DTSC Universe diagnosticThe city of the diagnostic

October and November 2026

DTSC Universe

samaulotte/DTSC-Website
Next.js 16React 19Three.jsBlenderDocker

The first site to bring the three hubs together. A WebGL galaxy where you dive towards each hub, a living city of 22 places for the diagnostic, the inverted pyramid in particles, three languages. 84 commits in four weeks.

More advanced artistically and technically, it lost the message and the voice of the client.

What was missing
05
dtsc.beHome page of the site: the We Add Value motto and a folder open on the three hubs, LUCID, SPARK and BRAINMobile menu of the site

November 2026, online

The paper site

dtsc.be
HTMLCSS 3DJavaScriptThree languagesPre-rendered pages

The work table of my portfolio applied to the DTSC site. First a mock-up in a single file, then a real site, at the address of the first one: 151 addresses in French, English and Dutch, that is 453 pages readable without JavaScript. The universe remains, as planets drawn in CSS, but the message comes first.

Have the Dutch reviewed, redirect brain.dtsc.be and lucid.dtsc.be, tell client reference stories.

What remains
03

Four steps, five versions

The reflection of my technical learning: each version required me to learn something new. The last one taught me to take things away.

Step 01WordPressLearning a tool for a need
Theme and page builderPluginsFormsAudience measurementHosting
Step 02React and ViteWriting the site rather than assembling it
React componentsServer-side rendering204 pre-rendered routesFour languagesSearch engine optimisationAnimation without a library
Step 03Next.js and Three.jsPushing technique and image
Next.js 16, TypeScriptWebGL with Three.jsBlender, videoDocker, TraefikAutomated testsImport of archives
Step 04Standalone HTMLLearning to take away
A single fileCSS 3DDependency-free JavaScriptText checksKeyboard, reduced motionCareful mobile version

The last step adds no technology: it takes some away. It is the one that taught me the most.

04

An inverted-pyramid strategy

Click on a level. Like the DTSC model, the pyramid is inverted: the voice of the client at the top, technique at the tip, in the service of everything else.

Level 1 of 5

The voice of the client

Start from the situations the reader recognises, not from our tools. Each page first answers one question: what do I gain from it?

Applied: revision of 17 October: the home page spells out the benefits from the first screen, without touching the structure.

05

Key decisions

Four trade-offs, each with what it cost me and what it brought.

5.1

Bringing three sites together into one entry point

Three sites, three addresses, three ways of presenting DTSC. The fourth, SPARK’s, never saw the light of day for lack of time in-house. A visitor had to guess where to look.

Trade-offGiving up standalone sites per hub, each in charge of its own presentation.
ResultA single site to maintain instead of four, three hubs, and a diagnostic that points to the right hub depending on the visitor’s situation.
dtsc.bebrain.dtsc.belucid.dtsc.bespark.dtsc.beplanned, never launched one universe, three hubs
5.2

Importing before rewriting

Before touching a single text, I imported the existing sites as they were: pages, profiles, projects, certificates.

Trade-offA slower start, and archives to keep in order.
ResultNothing lost: LUCID in four languages, BRAIN with 7 projects, 12 alumni and 11 certificates intact, every source file kept with its fingerprint.
5.3

Keeping faces intact

On 18 October, the members’ portraits dissolved into starlight on scroll. Spectacular.

Trade-offLess effect on the most human page of the site.
ResultFrom the next day, the photos stay intact: a member must remain recognisable.
5.4

Moving from the galaxy to paper

The WebGL universe was the most accomplished version, artistically and technically. But it required a 3D-capable browser, and the message came after the show.

Trade-offGiving up WebGL, the flights between planets, part of what I had just learned.
ResultA single source file, 143 pages, the universe kept as planets drawn in CSS, and the ecosystem’s message first, on computer and phone alike.
After: home page of the paper siteBefore: home page of DTSC Universe, in WebGL WebGL universePaper site

Same home page, same signature. Drag to move from the universe to paper.

06

A project led alone, reviewed by eleven

Alone in designing and developing, I did not write alone. Each member reviewed what they know best: a list of points to validate per person, a piece of feedback, a dated correction.

ThibaultCoordination of the ecosystem

Shared narrative, headcount and evidence. Reviews of 21 October and 3 November, launch review on 12 November, reviews of the paper version on 13 and 17 November.

NicolasFreelance path

Plans and included services confirmed on 23 October. Feedback on navigation on 18 November.

MathieuEmployee path

Employed consultant, finance and simulation.

JuniorSMEs

Offers for SMEs, support pathways.

Denis and DavidLUCID and Dutch

LUCID consistency, Dutch-language coverage. Flanders and Agile training on 2 November.

QuentinCompanies and Public Services

Pathway for companies and public services.

AnnaïckBRAIN

Scope and presentation of the laboratory. Her four offers for companies.

SaraBRAIN

Scientific files and collaborations. Her BRAIN projects document, taken up on 16 November.

Maud and SylvainSPARK

Academy and training figures.

A short loop, repeated with every piece of feedback

Steering comes down to one loop: a piece of feedback becomes a point to validate, then a dated correction, then a published version that is reviewed again.

  • A list of points to validate for each member, sorted by topic
  • Consent requests prepared for each testimonial, nothing published without them
  • Migration and handover notes: the project can be picked up on another machine
  • AI coding agents as reinforcement, framed by instructions written in the repository

Five weeks, sixteen milestones

Drag
16 Oct

Import of the LUCID sites, in four languages, and BRAIN: sources archived, nothing modified.

17 Oct

“What the client gains from it” revision. Story of the ecosystem. Published version 16.

18 Oct

The members’ portraits dissolve into starlight.

19 Oct

Going back: photos intact. Living city of 22 places for the diagnostic.

20 Oct

Inverted pyramid in particles. Published version 30.

21 Oct

Thibault’s review. Offers aligned with the sales matrix. Versions 41 and 42.

23 Oct

Freelance pathways confirmed by Nicolas.

2 Nov

Feedback from David, LUCID meeting, editorial line. “We Add Value” displayed large.

3 Nov

Figures verified, testimonials sourced, 121 reference logos checked.

12 Nov

Launch review. Full site in English and Dutch. Mobile navigation.

13 Nov

Paper mock-up: 136 pages in a single file. Published version 9.

14 Nov

Thibault’s review applied: first screen redone, five entry points, Join DTSC in three pages.

15 Nov

brain.dtsc.be taken over: three doors for companies, researchers and students, 59 redirects prepared.

16 Nov

Three languages and a real address for each page: sitemap, structured data, pages readable without JavaScript.

17 Nov

Thibault’s review of the live site: 14 of the 22 tracked points are settled.

18 Nov

Feedback from Thibault and Nicolas fixed the same day. Testimonials in three languages, audience measurement subject to consent.

07

Lean, Scrum and Agile, in practice

This site is also a reflection of my ability to manage a project. Here is what I put into practice, with supporting evidence.

Lean

The SPARK method
The voice of the client
Each page starts from a situation the reader recognises, as the 17 October revision shows.
Eliminating waste
No animation library on LUCID, around 85 KB avoided. Four ideas kept from an audit, the rest set aside. WebGL removed when it no longer served a purpose.
Going to see in the field
The points to validate start from the members concerned, not from my assumptions.
Continuous improvement
Each piece of feedback becomes a dated correction, never a project to reopen.

Scrum

Increments, reviews
Usable increments
Versions published one after another: 16, 30, 41 and 42 for the universe, 9 for the mock-up, then the live site, updated as feedback comes in.
A backlog per stakeholder
A list of points to validate for each member, sorted by topic.
Reviews
Review of 21 October, feedback of 23 October and 2 November, launch review on 12 November, reviews of 13 and 17 November.
A definition of “done”
Tests, route checks, no errors in the console, original texts compared with every version.

Agile

Adapting rather than following the plan
People before tools
A member-by-member review, a consent request for each testimonial.
A working site
At each stage, an online version to show rather than a document.
The client in the loop
The ecosystem is my client: its words, its verified figures, its approvals.
Welcoming change
Leaving the 3D universe when it was hiding the message.

The vocabulary SPARK teaches teams, applied to my own project.

Retrospectives: what I called into question

08

Review

01Technique is not the message

It sits at the tip of the pyramid, in the service of the rest. The most impressive version was not the most accurate.

02Everyone reviews what they know

Eleven targeted reviewers are better than one general meeting: the feedback arrives faster and is more precise.

03Iterate, publish, know how to go back

An online version, a piece of feedback, a dated correction. And accepting to undo an effect the very next day.

4 → 1addresses planned, then a single entry point
4languages on the LUCID site
22places in the city of the diagnostic
6 084text fragments compared with every version of the mock-up

Next steps planned

  • Have the Dutch reviewed by a Dutch-speaking member
  • Redirect brain.dtsc.be and lucid.dtsc.be, page by page
  • Tell client reference stories, backed by results

Acknowledged limits

The two WordPress sites are shown only as a diagram: I did not keep a screenshot of them. The site is online, but not finished: the review of the Dutch by a Dutch-speaking member, the redirects from brain.dtsc.be and lucid.dtsc.be and the client reference stories are still to be done.

Under the binding

WordPressAvadaReact 18ViteServer-side renderingNext.js 16React 19TypeScriptThree.jsWebGLBlenderDocker ComposeTraefikHTMLCSS 3DJavaScriptPythonPre-rendered pagesPlaywright

Thank you for reading this special issue.

The message first. Technique next.

CASE STUDY · COMPLETED ·HS