Skill · Documentation · Document a service or a project
Model an architecture beyond context: components, dynamic and deployment views, a single model in code
Split a container into components and know when to stop, draw the supplementary C4 views (landscape, dynamic, deployment), describe a single model in Structurizr DSL exported to Mermaid or C4-PlantUML, and write sequence, component and deployment diagrams in PlantUML checked in CI.
Start lesson 1The Documentation domain
- 4 lessons
- ~2 h 00 of reading
- 4 quizzes
- 0 proof lab
The path
Where it comes from, where it leads
What you need to know first, where you stand on this skill, and what it opens next. Your status is computed in your browser, from what you have read and passed.
Before · 1 prerequisite
Recommended before · 1
This skill, for you
Model an architecture beyond context: components, dynamic and deployment views, a single model in code
Computing
It unlocks · nothing yet
No other skill requires it: it is an end-of-path skill.
The path through the foundations From the most upstream foundation to this skill: what is in place, what remains to read.
Lessons
How to learn it
4 lessons, about ~2 h 00, in program order. Each lesson ends with its quiz.
The program
4 lessons · ~2 h 00
Part 1 · Modéliser une architecture (in French) 3 lessons · ~1 h 30
Part 2 · Représenter en code (in French) 1 lesson · ~30 min
Beyond the lessons
Assess, practise, pass the proof
Reading a lesson confirms nothing. A skill is confirmed by a passed quiz, practised in a guided lab, and put to the test by a challenge or a mission; an imported lab result is not verified by the site.
Assess yourself
4 quizzes
At the end of the lessons: passed at 70%, they confirm the skill.
Practice
No guided lab
No guided lab practices it yet.
Proof
No proof
Neither a challenge nor a mission with a proof yet.
Placement test
Preparing the questions…
Your answers in detail
For each question asked: your answer, the correct answer, its explanation and the page to reread.
Around it
Who requires it, who teaches it
Required by
No published job requires it yet.
Taught by
Same block · Document a service or a project
- Choose the document type and its reader before writing
- Write a clear, accessible and verifiable technical page
- Give a repository its README, CHANGELOG and ADRs
- Represent a system with diagrams as code that read without the image
- Keep documentation alive: owner, review, freshness
- Build and publish documentation checked in CI
- Document code: comments that say why, docstrings, generated reference
- Write a technical document in AsciiDoc: structure, attributes, blocks and conversion
- Build a technical presentation in Markdown or HTML, versioned and exported