History: the export gets its own section with a title bar and an info line (32.7 follow-up point 4)
This commit is contained in:
1 parent
e9e26aad78
commit
5dfb804893
1 file changed
+16
-5
+16
-5
@@ -27,11 +27,6 @@
|
||||
<h1>History</h1>
|
||||
<p class="intro">Every saved annual health check, newest first. Saved checks are never overwritten.</p>
|
||||
</div>
|
||||
<!-- The export link and the note that explains it live here now, with no
|
||||
`download` attribute, so the dated filename from Content-Disposition
|
||||
is the one that wins (sections 31 point 3 and 32.7 point 5). -->
|
||||
<a class="secondary-button" href="/api/export">Download CSV</a>
|
||||
<p class="workflow-note" id="workflow-note">Save a health check to see it in the history. Download CSV exports every saved key check, one row per key check, as a dated file.</p>
|
||||
</div>
|
||||
|
||||
<section class="section-block" aria-labelledby="history-list-title">
|
||||
@@ -44,6 +39,22 @@
|
||||
<div id="history-list" aria-live="polite"><p class="empty-state">Loading saved checks…</p></div>
|
||||
</section>
|
||||
|
||||
<!-- The export has a section of its own, after the list: a title bar, the
|
||||
button, and the line that explains what the file holds
|
||||
(section 32.7 follow-up point 4). The button carries no download
|
||||
attribute, so the dated filename from Content-Disposition wins
|
||||
(section 31 point 3). -->
|
||||
<section class="section-block" aria-labelledby="export-title">
|
||||
<div class="section-heading">
|
||||
<div>
|
||||
<p class="eyebrow">Export</p>
|
||||
<h2 id="export-title">Download the report</h2>
|
||||
</div>
|
||||
</div>
|
||||
<a class="secondary-button" href="/api/export">Download CSV</a>
|
||||
<p class="workflow-note">Every saved key check is exported, one row per key check, as a dated CSV file.</p>
|
||||
</section>
|
||||
|
||||
<section class="section-block" id="history-detail" aria-labelledby="history-detail-title" hidden>
|
||||
<div class="section-heading">
|
||||
<div>
|
||||
|
||||
Reference in new issue
Block a user