Resumen
The dossier template is for longer analysis: more evidence, more structure, and more explicit trade-offs. It should still feel calm and readable on a phone.
dossier /views/ai-tooling-dossier/ Publicado 8 abr 2026 Actualizado 8 abr 2026
AI Tooling Dossier
A richer report page with sections, evidence, diagram, table, and source attribution.
This page shows the richer side of the system. It is still mobile-first, but it gives space to multiple evidence formats: prose, insight cards, charts, diagrams, comparison tables, and source attribution.
The important thing is not that every dossier use every block. The important thing is that when the task needs those blocks, they already exist and look like part of the same system.
Hallazgos
Foundation work should happen once
If every new page task has to reinvent routing, components, and styling, the system becomes unreliable. The foundation should already exist.
Constraints make output better
A narrow design language and a small component kit increase consistency and reduce the chance of low-quality one-off pages.
Diagrams should behave like evidence
They are there to make a system legible, not to show that a graph library is available.
Where consistency comes from
Three sources of quality in the system.
Examples and shared blocks usually contribute more to consistency than abstract rules alone.
Publishing flow
The intended path from request to delivered page.
The only interactive blocks should be charts or diagrams; the rest remains static.
Template comparison
| Template | Best for | Density | Default route |
|---|---|---|---|
| briefing | quick decisions | low | /private/<token>/ |
| dossier | deeper research | medium | /views/<slug>/ |
| dashboard | metrics and trends | medium-high | /views/<slug>/ |
Fuentes
- Cloudflare Pages — Static hosting target.
- Astro Content Collections — Structured report content.