stack-site-builder 1.25.4 → 1.26.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -11,6 +11,32 @@ content schema, while a consuming site supplies only content, taxonomy data and
11
11
  config. Sites track the theme with `pnpm up stack-site-builder`, so each release
12
12
  here is a plain version bump they pull in.
13
13
 
14
+ ## [1.26.0] - 2026-09-02
15
+
16
+ ### Added
17
+
18
+ - **PDF pages carry the deck footer and a page number.** The deck's fixed
19
+ footer and pager are screen chrome and stay hidden in print — a fixed
20
+ element would repeat over the content of every page, and the pager would
21
+ stamp the same "current" number everywhere. The deck script now gives every
22
+ slide its own print-only bottom line instead: the footer's text (presenter
23
+ · date) on the left and `n / total` on the right, styled like the screen
24
+ footer. A deck with no footer configured still gets the page numbers.
25
+
26
+ ## [1.25.5] - 2026-09-02
27
+
28
+ ### Fixed
29
+
30
+ - **A slide's last line could be sliced off at the bottom of the PDF page.**
31
+ 1.25.4 sized the print page so *width*-relative proportions match a large
32
+ desktop window, but the vertical axis has the same failure mode: rem-capped
33
+ text keeps its screen size while viewport-height media (a screenshot capped
34
+ at `58vh`, say) shrinks with the page, so on a 972px-tall page their sum
35
+ could exceed the slide and the caption under an image lost its last line.
36
+ The page is now 24in × 13.5in (2304 × 1296 CSS px) — still 16:9, but taller
37
+ than the viewports decks are authored in, so every slide gets at least the
38
+ vertical room it had on screen.
39
+
14
40
  ## [1.25.4] - 2026-09-02
15
41
 
16
42
  Print/PDF export of a deck now reproduces what the screen shows: images load
@@ -638,6 +664,8 @@ catalog sites from a thin content-only repository.
638
664
  - **Standalone development setup** — a devcontainer and a minimal `playground/`
639
665
  consuming site for developing and previewing the theme on its own.
640
666
 
667
+ [1.26.0]: https://github.com/CodeComposeStudio/stack-site-builder/compare/v1.25.5...v1.26.0
668
+ [1.25.5]: https://github.com/CodeComposeStudio/stack-site-builder/compare/v1.25.4...v1.25.5
641
669
  [1.25.4]: https://github.com/CodeComposeStudio/stack-site-builder/compare/v1.25.3...v1.25.4
642
670
  [1.25.3]: https://github.com/CodeComposeStudio/stack-site-builder/compare/v1.25.2...v1.25.3
643
671
  [1.25.2]: https://github.com/CodeComposeStudio/stack-site-builder/compare/v1.25.1...v1.25.2
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "stack-site-builder",
3
3
  "type": "module",
4
- "version": "1.25.4",
4
+ "version": "1.26.0",
5
5
  "license": "MIT",
6
6
  "description": "The engine behind the awesome-*-stack catalog sites: an Astro theme with the catalog/concepts/articles/slides/samples routes, components, styles and markdown pipeline. Sites provide content, taxonomy data and config.",
7
7
  "repository": {
@@ -192,6 +192,31 @@ const priv = entry.data.private;
192
192
  const btnNext = chrome<HTMLButtonElement>('[data-next]');
193
193
  if (elTot) elTot.textContent = String(total);
194
194
 
195
+ // Print-only per-slide footer. The deck's fixed footer and pager are
196
+ // screen chrome — hidden in print, where a fixed element would repeat
197
+ // over the content of every page (and the pager would stamp the same
198
+ // "current" number everywhere). Instead each slide carries its own
199
+ // line: the footer's text on the left, its page number on the right.
200
+ {
201
+ const foot = chrome<HTMLElement>('.aas-deck-footer');
202
+ const footText = foot
203
+ ? Array.from(foot.children)
204
+ .map((c) => c.textContent?.trim() ?? '')
205
+ .filter((t) => t && t !== '·')
206
+ .join(' · ')
207
+ : '';
208
+ slides.forEach((s, i) => {
209
+ const meta = document.createElement('div');
210
+ meta.className = 'aas-slide-print-meta';
211
+ const left = document.createElement('span');
212
+ left.textContent = footText;
213
+ const right = document.createElement('span');
214
+ right.textContent = `${i + 1} / ${total}`;
215
+ meta.append(left, right);
216
+ s.appendChild(meta);
217
+ });
218
+ }
219
+
195
220
  // Heavy embeds (interactive demo iframes) jank slide transitions the
196
221
  // moment they run — worse once the viewer has interacted with one. So
197
222
  // embeds are click-to-run: each iframe starts blank behind a "run"
@@ -2341,6 +2341,27 @@ summary {
2341
2341
  color: var(--aas-muted);
2342
2342
  opacity: 0.7;
2343
2343
  }
2344
+ /* Print-only per-slide footer line, injected by the deck script: the fixed
2345
+ footer above (and the pager) are screen chrome, so in a PDF each slide
2346
+ carries its own copy — footer text left, page number right — styled to
2347
+ read like the screen footer. */
2348
+ .aas-slide-print-meta {
2349
+ display: none;
2350
+ }
2351
+ @media print {
2352
+ .aas-slide .aas-slide-print-meta {
2353
+ display: flex;
2354
+ justify-content: space-between;
2355
+ align-items: center;
2356
+ position: absolute;
2357
+ left: 1rem;
2358
+ right: 1rem;
2359
+ bottom: 1.1rem;
2360
+ font-size: 0.8rem;
2361
+ color: var(--aas-muted);
2362
+ opacity: 0.7;
2363
+ }
2364
+ }
2344
2365
  .aas-deck-footer-sep {
2345
2366
  opacity: 0.5;
2346
2367
  }
@@ -2350,18 +2371,23 @@ summary {
2350
2371
  a stray extra page, and wide enough that image splits never stack. Enable
2351
2372
  "Background graphics" in the print dialog for themed/image backgrounds. */
2352
2373
  @media print {
2353
- /* A 16:9 page, sized 18in × 10.125in (1728 × 972 CSS px) rather than the
2354
- PowerPoint 13.333in: rem-based type (code blocks, clamp() caps) does not
2355
- shrink with the page, so on a smaller page it eats proportionally more
2356
- width than on the desktop windows slides are authored against — and code
2357
- that fit on screen came out clipped at the right edge of the PDF. This
2358
- page is big enough that every clamp() saturates at its rem cap and the
2359
- content column below hits its 96rem cap — the same saturated state as a
2360
- full-size desktop monitor, so the PDF reproduces what the author saw.
2361
- PDF pages are vector; the physical inches are irrelevant on screen and
2362
- shrink-to-fit when printed on paper. */
2374
+ /* A 16:9 page, sized 24in × 13.5in (2304 × 1296 CSS px) rather than the
2375
+ PowerPoint 13.333in: rem-based type (titles, captions, code — every
2376
+ clamp() cap) does not shrink with the page, so on a smaller page it eats
2377
+ proportionally more room than on the desktop windows slides are authored
2378
+ against. Both axes matter. Width: code that fit on screen came out
2379
+ clipped at the PDF's right edge until the content column could reach the
2380
+ same 96rem cap it has on screen. Height: viewport-height media (a
2381
+ screenshot capped at 58vh, say) shrinks with the page while the fixed
2382
+ text around it does not, so their sum overflowed a shorter page and the
2383
+ caption's last line was sliced off. At 1296px the page is taller than
2384
+ the ~1200px viewports decks are authored in, giving every slide at least
2385
+ the vertical room it had on screen. Everything saturates at its rem cap —
2386
+ the same state as a large 16:9 monitor — so the PDF reproduces what the
2387
+ author saw. PDF pages are vector; the physical inches are irrelevant on
2388
+ screen and shrink-to-fit when printed on paper. */
2363
2389
  @page {
2364
- size: 18in 10.125in;
2390
+ size: 24in 13.5in;
2365
2391
  margin: 0;
2366
2392
  }
2367
2393
  .aas-deck-body {
@@ -2388,8 +2414,8 @@ summary {
2388
2414
  scroll-snap-type: none;
2389
2415
  }
2390
2416
  .aas-slide {
2391
- width: 18in;
2392
- height: 10.125in;
2417
+ width: 24in;
2418
+ height: 13.5in;
2393
2419
  overflow: hidden;
2394
2420
  scroll-snap-align: none;
2395
2421
  break-inside: avoid;