✨(frontend) Can print a doc

[AntoLC]

Purpose

If we want to print our docs, they are now displayed correctly.

Demo

Enregistrement.2026-01-26.114028.mp4

[github-actions]

Size Change: +31 B (0%)

Total Size: 4.2 MB

Filename	Size	Change
apps/impress/out/_next/static/72b1ad95/_buildManifest.js	831 B	+831 B (new file)	🆕
apps/impress/out/_next/static/6187331f/_buildManifest.js	0 B	-831 B (removed)	🏆

_{compressed-size-action}

[github-actions]

🚀 Preview will be available at https://1832-docs.ppr-docs.beta.numerique.gouv.fr/

You can use the existing account with these credentials:

• username: docs
• password: docs

You can also create a new account if you want to.

Once this Pull Request is merged, the preview will be destroyed.

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm markdown-it is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: ? → npm/markdown-it@14.1.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/markdown-it@14.1.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm safer-buffer is 94.0% likely obfuscated Confidence: 0.94 Location: Package overview From: ? → npm/safer-buffer@2.1.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/safer-buffer@2.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	jest@​30.2.0
	@​types/​jest@​30.0.0
	clsx@​2.1.1
	ts-node@​10.9.2
	eslint-plugin-react@​7.37.5
	uuid@​13.0.0
	eslint-config-prettier@​10.1.8
	webpack@​5.104.1
	typescript@​5.9.3

View full report

[Ovgodd]

👍

[StephanMeijer]

Seems like a sensible approach. You lose a bit of control versus first converting to Typst and then to PDF, but it gives you a bit more control on the front-end