Table of contents
antoinebou12: How the GitHub profile is assembled
This is the repository behind my GitHub profile README. It combines ordinary Markdown with images, embedded widgets and scheduled updates. There is no application server in the profile itself.
- Languages
- 0Code breakdown
- Documented components
- 2Explore modules
- Source documents
- 1Read the instructions
Repository languages
Shares calculated from GitHub Linguist bytes.
GitHub reports no language bytes for this repository.
1. Overview
1.1. Why it exists
Automated SVG and metrics rendering workflow maintaining dynamic profile assets.
1.2. Best fit
Automated profile asset generation.
2. Use cases
GitHub profile README with links, badges, pinned projects and stats, kept current by scheduled Actions.
- Read the profile and links
- Profile visitor
README.md opens with the platform and graphics headline, then links (GitHub, LinkedIn, website, CV, email), certification badges and the main languages and tools.
- Browse pinned projects
- Profile visitor
A collapsible Featured projects section shows pin cards for repositories such as AINewsTracker, hass_renpho, ipc-toolkit and TrueMapData, plus the DashCTRL, ETSim and UFOKEK organisations.
- Refresh 3D contribution chart
- GitHub Actions
github-profile-3d-contrib.yml runs daily at 05:00 UTC, generates the 3D contribution calendar, keeps only profile-night-green.svg and commits it.
- Update LeetCode badges
- GitHub Actions
update-readme.yml runs daily at 12:00 UTC, fetches stats from leetcodestats.cyclic.app and rewrites the badges between the LEETCODE_STATS markers in README.md.
- Check README links
- Profile ownerGitHub Actions
On each push or pull request to main or master, check-links.yml runs lychee on README.md and docs/**/*.md and writes a job summary.
- Publish the Jekyll page
- Profile ownerGitHub Actions
jekyll-pages.yml builds docs/ with the jekyll-theme-primer theme and deploys it to GitHub Pages; docs/index.md points back to the profile README.
2.1. Scenario: Edit the profile and let automation keep it current
- The owner edits README.md, for example the Featured projects list, and pushes to master.
- check-links.yml runs lychee on README.md and the docs Markdown and reports broken links.
- jekyll-pages.yml builds docs/ and deploys the small Jekyll site to GitHub Pages.
- Each day, github-profile-3d-contrib.yml regenerates profile-night-green.svg and commits it.
- A visitor opens the profile page and sees the updated README, stats cards and 3D calendar.
Files readREADME.md.github/workflows/github-profile-3d-contrib.yml.github/workflows/update-readme.yml.github/workflows/check-links.yml.github/workflows/jekyll-pages.ymldocs/_config.ymldocs/index.md
3. Getting started
These commands come from the repository documentation. They were not run during this review.
4. Repository references
The repository does not provide a detailed guide for these steps. Start with its README and the source walkthrough above.
5. Features and components 2
- README and assets
- README.md is the visible profile document. The images, models and profile-3d-contrib directories hold assets used alongside it. GitHub renders the document, while linked services may generate their own images separately.
- Scheduled changes
- The update-readme workflow fetches LeetCode statistics, builds badge URLs and replaces the text between dedicated README markers. Separate workflows handle the contribution graphic, link checks and Pages.
6. Architecture
Expand a component to follow its connections, or explore the full diagram.
External statistics
GitHub Actions
Marked README section
- From GitHub Actions
- To GitHub profile
GitHub profile
Mermaid Interactive diagram
System overview of the components and connections verified in the repository.
flowchart LR
n0["External statistics"]
n1["GitHub Actions"]
n2["Marked README section"]
n3["GitHub profile"]
n0 --> n1
n1 --> n2
n2 --> n3
Text version of the diagram
- External statistics → GitHub Actions
- GitHub Actions → Marked README section
- Marked README section → GitHub profile
Follow one path through the code
In update-readme.yml, follow the HTTP response into the badge strings and then into the marker replacement. If either marker is missing, that replacement block is skipped.
7. Technical dossier
Built from the source at commit c519c6b (6 files). Each item comes from a pattern match in the code, so open the linked file before relying on it.
7.1. Layers and modules
Folders are sorted into layers by name, from the user interface down to data access. Because the sorting uses names only, the diagram says nothing about calls between layers.
Mermaid Layered view
flowchart TB
subgraph L_hosting["Build, CI and hosting"]
direction TB
hosting_0[".github<br/>5 files"]
end
7.2. C4 model
From system context to code declarations. Each level reflects the available source evidence.
UML 1 · System context
The widest C4 view: who uses the project and which outside systems and data stores it relies on. Rendered with uml-mcp.
PlantUML source
@startuml
!include <C4/C4_Context>
LAYOUT_LEFT_RIGHT()
System(SYS, "antoinebou12", "This is the repository behind my GitHub profile README")
@enduml
UML 2 · Containers
One level closer: the parts that run separately inside the project, their main language and how calls flow between them. Rendered with uml-mcp.
PlantUML source
@startuml
!include <C4/C4_Container>
LAYOUT_LEFT_RIGHT()
System_Boundary(SYS, "antoinebou12") {
Container(APP, "antoinebou12", "")
}
@enduml
UML 3 · Components and layers
Modules grouped by source-layer classification. Boundaries show organization, not runtime isolation or call relationships. Rendered with uml-mcp.
PlantUML source
@startuml
!include <C4/C4_Component>
LAYOUT_TOP_DOWN()
System_Boundary(SYS, "antoinebou12") {
Boundary(L0, "Build, CI and hosting", "layer") {
Component(M0_0, ".github", ".yml", "5 files")
}
}
@enduml
Level 4: the available sources do not support this view.
7.3. CI/CD pipeline
4 GitHub Actions workflows, 5 jobs. Each box is a job; double-bordered boxes publish or deploy, and arrows follow needs.
Mermaid Pipeline flow
flowchart LR
subgraph wf0["Check links"]
direction LR
wf0_lychee["lychee<br/>ubuntu-latest"]
end
subgraph wf1["GitHub-Profile-3D-Contrib"]
direction LR
wf1_build[["generate-github-profile-3d-contrib<br/>ubuntu-latest"]]
end
subgraph wf2["Deploy Jekyll site to Pages"]
direction LR
wf2_build[["build<br/>ubuntu-latest"]]
wf2_deploy[["deploy<br/>ubuntu-latest"]]
end
subgraph wf3["Update README with LeetCode Stats"]
direction LR
wf3_update_readme[["update-readme<br/>ubuntu-latest"]]
end
t0(["push · pull request · manual run"])
t1(["schedule · manual run"])
t2(["push · manual run"])
t3(["manual run · schedule"])
d0[("GitHub Pages")]
t0 --> wf0_lychee
t1 --> wf1_build
t2 --> wf2_build
wf2_build --> wf2_deploy
wf2_deploy -.-> d0
t3 --> wf3_update_readme
| Workflow | Triggers | Jobs | Publishes to |
|---|---|---|---|
Check links.github/workflows/check-links.yml | push, pull request, manual run |
| — |
GitHub-Profile-3D-Contrib.github/workflows/github-profile-3d-contrib.yml | schedule, manual run |
| — |
Deploy Jekyll site to Pages.github/workflows/jekyll-pages.yml | push, manual run |
| GitHub Pages |
Update README with LeetCode Stats.github/workflows/update-readme.yml | manual run, schedule |
| — |
7.4. Deployment
Mermaid Deployment diagram
flowchart LR
repo[("GitHub repository")]
ci[["GitHub Actions<br/>4 workflows"]]
pub_GitHub_Pages[("GitHub Pages")]
repo -->|"push or pull request"| ci
ci -->|"publishes"| pub_GitHub_Pages
Where it runs
Published to
7.5. Security
Supply chain
The available sources do not document the remaining sections.
8. Reference
1 / 1 eligible files read (88 in the tree); 0 oversized, 0 failed reads and 0 syntax diagnostics.
What the scan covers
Known dependency/build folders, credential files and binaries are excluded. The scan covers READMEs, recognized manifests and parser-supported source files.
Linguist statistics cover the whole repository and may include other languages.
10. Files to read 3
11. Glossary
Repository
The versioned source files, configuration, and history of a project.
README
The repository’s entry document, usually covering its purpose and initial setup.
Dependency
A library, tool, or service that another component needs to build or run.
HTTP
A request-and-response protocol used by browsers and web services. A method, path, headers, and optional body describe a request.
Build
The steps that turn source files and dependencies into a runnable program or distributable artifact.
Continuous integration
Automated checks that run when source changes, such as building, testing, and linting. Passing checks cover only what those checks exercise.
GPU
A processor designed for parallel workloads, including graphics rendering and many numerical operations.
Mesh
A surface represented by vertices and connected elements, often triangles. Its geometry is distinct from its material or texture.
12. References
- antoinebou12. (2026, November 5). antoinebou12. [Software repository] github.com.
- antoinebou12. (2026, November 5). antoinebou12: README. [Repository documentation] github.com.
- antoinebou12. (2026, November 5). README.md. [Source file] github.com.
- antoinebou12. (2026, November 5). .github/workflows/update-readme.yml. [Source file] github.com.
- antoinebou12. (2026, November 5). .github/workflows/github-profile-3d-contrib.yml. [Source file] github.com.
- Boucher, A. (2026, October 23). antoinebou12: How the GitHub profile is assembled. [Project article] antoineboucher.info.
Sources without a publication date show the date they were last checked, November 5, 2026. File links retain the inspected revision where available.