Quick Summary
This sample shows the intended workflow: write the source in Markdown, render it into a polished static HTML page, and deploy only when the content is safe to share.
- Source of truth: Markdown lives in
/root/hermes-output/markdown/. - Rendered output: HTML lives in
/root/hermes-output/html/. - Publishing target: Cloudflare Pages at
coretan.lajucepat.cloudonce deployment is intentionally run.
Why This Workflow Works
A Markdown-first process keeps analysis editable, auditable, and reusable. The HTML render step turns the same source into a warm reading page with clear hierarchy, practical copy, and restrained Hermes Agent styling.
Example Evidence Table
| Item | Status | Notes |
|---|---|---|
| Markdown folder | Ready | /root/hermes-output/markdown |
| HTML folder | Ready | /root/hermes-output/html |
| Renderer | Ready | scripts/render_report.py |
| Cloudflare deploy helper | Ready | scripts/deploy_cloudflare_pages.sh |
Example Code Block
/root/hermes-output/scripts/render_report.py /root/hermes-output/markdown/2026-05-02_sample-hermes-report.md
Example Callout
Long reports should be readable as documents, not trapped inside a chat bubble.