After collecting everything I could about artificial intelligence (Episode 1) and exploring how it could apply to my field, I decided to move from theory to practice by completely rebuilding my website.
Goal: Put my new knowledge into action and test, in real-world conditions, what AI can truly bring to a content professional.

Over the past few months, I dove deep into the fascinating world of AI. A joyful and hands-on exploration of artificial intelligence in service of digital creativity: a full website redesign powered by Docusaurus, generative AI, my expertise, and passion as the driving force.

I'm training in AI. Not to follow a trend. But to understand what it can truly bring to my profession.
With a solid background in building and maintaining documentation sites, I aim to go further by understanding AI models, testing tools, and learning how to use them wisely. AI indeed offers many potential benefits...

I'm a lifelong learner.
There are many key benefits of lifelong learning, like staying current, gaining confidence, boosting creativity, and finding deeper meaning in work. Graduating isn't the end of learning, and knowledge from school alone isn't enough for a full career.

A while back, someone asked me what tool I use for technical documentation — and instead of picking just one, I realized my setup is more of a creative trio.
I write in Markdown, build with Docusaurus, and sketch with Excalidraw. In this post, I’ll share why this combo works so well for me and how it keeps writing both simple and powerful.

I’ve been building online help since the early days — back when HTML ruled and editors were mainly plain text. Things have changed a lot, but some fundamentals are still going strong.
In this piece, I look back at how Help has evolved, from RoboHelp and tri-pane structures to the cleaner world of Markdown and static site generators. It’s part nostalgia, part practicality — and all about making documentation better.

For years, documentation happened only after development was finished. The method involved gathering information — sometimes straight from developers, but mostly within our own bubble, working among technical writers. Then one day, I realized something: I was using Git, writing in Markdown, pushing commits, editing in VS Code. Wait a minute — I was doing docs-as-code.

This summer, I dove back into a client's documentation with a dual mission: explain their new API and migrate the entire site to Docusaurus V2.
From search engines to stylish admonitions and ReDoc integration, this version doesn’t just look good — it works brilliantly. Here’s what we gained, and what to watch out for.