reports
@media print, editorial header treatment, footer gutter for page numbers and source. Visualizations, stats, prose, and charts go inside; the frame doesn't pick what those are. basic
quarterly report · 2026 Q1
awarded · FY26 to date
active projects
total awarded
TxDOT share
FY26 Q1 closed with awarded funding 12.4% above the same quarter in FY25, driven primarily by a $9.2M IH-35 corridor-safety renewal from TxDOT and a $4.8M FHWA work-zone classifier grant.
Coordination with TxDOT followed the established cadence. Outstanding action items track to the May steering review.
figure 1
<tux-report-frame
size="letter"
density="editorial"
eyebrow="quarterly report · 2026 Q1"
title="Sponsored research — TTI corridor program"
>
<!-- Hero stat -->
<tux-big-stat value="$84.2M" label="awarded · FY26 to date" />
<!-- 3-up factoid row -->
<tux-factoid :items="factoid" />
<!-- Body prose -->
<p>… narrative summary …</p>
<!-- Embedded R-rendered chart from the Visualizations toolkit -->
<tux-viz-rplot
kind="svg"
src="/viz-rplot-grants.svg"
title="Grant draws by sponsor"
ratio="8/5"
/>
<template #footer>
<span>tti.tamu.edu</span>
<span>page 1 of 4</span>
</template>
</tux-report-frame>scope
When you're producing a deliverable that has to leave the app as paper or PDF — quarterly research reports, IRB submissions, sponsor write-ups, accreditation packages. If the output is meant to live inside the app and stay interactive (filter, drill, pivot), it's a Visualization, not a Report.