Skip to main content

How I Took Control of My Metadata

· 8 min read
Florence
Florence
Expert Technical Writer

How I used structured data to control my digital identity

In a world where everything is data — our photos, documents, publications, websites — metadata has become a major strategic asset.
Search engines, generative engines, ATS platforms, freelance marketplaces, AI systems... they all read metadata before they read content.

Metadata therefore directly influences how search engines, generative engines, ATS, AI systems, and even internal tools interpret your content.
It has effectively become a form of digital identity, a semantic passport.

Unlike a PDF* or a static knowledge base, a website offers a decisive advantage: you can write your own metadata — and therefore control it.

My 2026 Toolset

· 4 min read
Florence
Florence
Expert Technical Writer

The 2026 Toolset for Docs‑as‑Code and AI‑Friendly Technical Writers

In the age of AI, docs‑as‑code isn't a technical choice. It's a strategic one.

AI is advancing at an incredible pace. After agents, skills, and BMAD approaches, one thing has become clear: AI performs best when it works with clear structures, versioned data, textual content, and contextual information. In other words: the natural terrain of code.

That's exactly why documentation must now be treated like code.

How I Personally Did the SEO of My Website

· 5 min read
Florence
Florence
Expert Technical Writer

Implementing real-world SEO on a Docusaurus website, with GEO in mind

SEO is one of those topics everyone talks about, but few actually practice end-to-end on a real website. It is a real profession with real skills, and not something that can be improvised by simply stuffing the <head> with keywords.

When I built CoffeeCup.tech, I didn't want SEO to remain a theoretical checklist (as I confess, I did in my previous Hugo Coffee Cup website).

My AI Journey – Episode 2️⃣

· 4 min read
Florence
Florence
Expert Technical Writer

Hands-On Time

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.

I'm Training in AI

· 2 min read
Florence
Florence
Expert Technical Writer

Putting AI at the Service of Technical Writing

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

· 2 min read
Florence
Florence
Expert Technical Writer

The Continuous Pursuit of Knowledge and Skills

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.

My Favorite Tools

· 4 min read
CoffeeCup
CoffeeCup
Senior Technical Writer

Markdown, Docusaurus & Diagrams — My Happy Trio for Docs

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.

Online Doc Fundamentals

· 4 min read
CoffeeCup
CoffeeCup
Senior Technical Writer

The Help Files Evolution: From Pop-Ups and Frames to Markdown Bliss

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.

The Docs as Code Philosophy

· 3 min read
CoffeeCup
CoffeeCup
Senior Technical Writer

The Docs-as-Code Way: A Philosophy That Builds Better Docs

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.