rshow 0.0.0-stage → 0.0.2

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.
Files changed (84) hide show
  1. package/LICENSE +21 -0
  2. package/README.md +50 -2
  3. package/dist/main.js +8500 -0
  4. package/package.json +48 -4
  5. package/skills/rshow/SKILL.md +144 -0
  6. package/skills/rshow/reference/cli.md +263 -0
  7. package/skills/rshow/reference/dashboard.md +122 -0
  8. package/skills/rshow/reference/mockups.md +113 -0
  9. package/skills/rshow/reference/page-contract.md +83 -0
  10. package/skills/rshow/reference/pages.md +174 -0
  11. package/skills/rshow/reference/poster.md +137 -0
  12. package/skills/rshow/reference/project-page.md +132 -0
  13. package/skills/rshow/reference/reports.md +158 -0
  14. package/skills/rshow/reference/sketch.md +78 -0
  15. package/skills/rshow/reference/terminal.md +148 -0
  16. package/skills/rshow/reference/themes.md +139 -0
  17. package/skills/rshow-implement/SKILL.md +112 -0
  18. package/skills/rshow-implement/reference/compare.md +156 -0
  19. package/skills/rshow-implement/reference/handoff.md +125 -0
  20. package/skills/rshow-implement/reference/map.md +151 -0
  21. package/skills/rshow-slides/SKILL.md +136 -0
  22. package/skills/rshow-slides/reference/layouts.md +251 -0
  23. package/themes/default/dashboard.css +521 -0
  24. package/themes/default/dashboard.js +1390 -0
  25. package/themes/default/deck.css +586 -0
  26. package/themes/default/deck.js +741 -0
  27. package/themes/default/example/capture.ans +1 -0
  28. package/themes/default/example/dashboard.html +106 -0
  29. package/themes/default/example/demo.cast +14 -0
  30. package/themes/default/example/drawing.excalidraw +377 -0
  31. package/themes/default/example/index.html +311 -0
  32. package/themes/default/example/mockup-desktop.html +331 -0
  33. package/themes/default/example/mockup-platforms.html +742 -0
  34. package/themes/default/example/mockup.html +416 -0
  35. package/themes/default/example/page.html +153 -0
  36. package/themes/default/example/poster-figure.svg +58 -0
  37. package/themes/default/example/poster.html +181 -0
  38. package/themes/default/example/project.html +229 -0
  39. package/themes/default/example/report.html +404 -0
  40. package/themes/default/example/results.csv +61 -0
  41. package/themes/default/example/sketch.html +178 -0
  42. package/themes/default/example/teaser.svg +66 -0
  43. package/themes/default/example/terminal.html +231 -0
  44. package/themes/default/example/tui.html +223 -0
  45. package/themes/default/fonts/IBMPlexMono-Regular-Latin1.woff2 +0 -0
  46. package/themes/default/fonts/IBMPlexSans-Light-Latin1.woff2 +0 -0
  47. package/themes/default/fonts/IBMPlexSans-Regular-Latin1.woff2 +0 -0
  48. package/themes/default/fonts/IBMPlexSans-SemiBold-Latin1.woff2 +0 -0
  49. package/themes/default/fonts/OFL.txt +93 -0
  50. package/themes/default/fonts.css +63 -0
  51. package/themes/default/index.html +573 -0
  52. package/themes/default/mockup.css +1078 -0
  53. package/themes/default/mockup.js +1433 -0
  54. package/themes/default/mode.js +242 -0
  55. package/themes/default/page.css +320 -0
  56. package/themes/default/poster.css +480 -0
  57. package/themes/default/poster.js +223 -0
  58. package/themes/default/project.css +482 -0
  59. package/themes/default/project.js +116 -0
  60. package/themes/default/report.css +776 -0
  61. package/themes/default/report.js +427 -0
  62. package/themes/default/sketch.css +166 -0
  63. package/themes/default/sketch.js +681 -0
  64. package/themes/default/skins/adwaita.css +669 -0
  65. package/themes/default/skins/custom.css +596 -0
  66. package/themes/default/skins/egui.css +639 -0
  67. package/themes/default/skins/fluent.css +1093 -0
  68. package/themes/default/skins/fluent.js +458 -0
  69. package/themes/default/skins/mac.css +647 -0
  70. package/themes/default/skins/material.css +692 -0
  71. package/themes/default/skins/sketch.css +436 -0
  72. package/themes/default/skins/sketch.js +494 -0
  73. package/themes/default/skins/wire.css +561 -0
  74. package/themes/default/terminal.css +292 -0
  75. package/themes/default/terminal.js +433 -0
  76. package/themes/default/theme.json +149 -0
  77. package/themes/default/tokens.css +255 -0
  78. package/themes/default/tui.css +703 -0
  79. package/themes/default/tui.js +472 -0
  80. package/worker/index.js +6918 -0
  81. package/worker/migrations/0001_init.sql +52 -0
  82. package/worker/migrations/0002_blobs.sql +5 -0
  83. package/worker/migrations/0003_projects.sql +31 -0
  84. package/worker/migrations/0004_page_data_blob.sql +19 -0
@@ -0,0 +1,181 @@
1
+ <!doctype html>
2
+ <html lang="en">
3
+ <head>
4
+ <meta charset="utf-8">
5
+ <meta name="viewport" content="width=device-width, initial-scale=1">
6
+ <meta name="color-scheme" content="light dark">
7
+ <title>rshow poster: publishing a folder as an artifact that keeps working</title>
8
+ <!--
9
+ Theme links. A published poster points at the theme artifact with
10
+ root-relative URLs at one pinned version:
11
+
12
+ <link rel="stylesheet" href="/_themes/<name>@<n>/fonts.css">
13
+ <link rel="stylesheet" href="/_themes/<name>@<n>/tokens.css">
14
+ <link rel="stylesheet" href="/_themes/<name>@<n>/poster.css">
15
+ <script src="/_themes/<name>@<n>/mode.js"></script>
16
+ <script defer src="https://cdn.jsdelivr.net/npm/qrcode-generator@1.4.4/qrcode.js"></script>
17
+ <script defer src="/_themes/<name>@<n>/poster.js"></script>
18
+
19
+ This copy links the theme folder itself, so it previews from a local checkout
20
+ with only the QR library coming from a CDN. mode.js runs in the head, before
21
+ the body paints. poster.js is deferred and runs after the QR library: it draws
22
+ the code from the URL in data-qr, scales the sheet to the window and copies the
23
+ sheet size into @page. If the library never loads, the address printed under
24
+ the code is the fallback and nothing else changes.
25
+
26
+ The four sheets are a0 (default), a1, 36x48 (the 3x4 ft sheet shown landscape)
27
+ and 48x36 (the same sheet stood portrait); ?size=a1 in the address picks one
28
+ without a click, which is what the print check uses.
29
+
30
+ The authors, the affiliations and the venue are placeholders. Every value in
31
+ the chart is example data and the figure says so twice.
32
+ -->
33
+ <link rel="stylesheet" href="../fonts.css">
34
+ <link rel="stylesheet" href="../tokens.css">
35
+ <link rel="stylesheet" href="../poster.css">
36
+ <script src="../mode.js"></script>
37
+ <script defer src="https://cdn.jsdelivr.net/npm/qrcode-generator@1.4.4/qrcode.js"></script>
38
+ <script defer src="../poster.js"></script>
39
+ </head>
40
+ <body>
41
+
42
+ <div class="poster-toolbar">
43
+ <div class="poster-sizes" role="group" aria-label="Poster size">
44
+ <button type="button" data-poster-size="a0" aria-pressed="true">A0</button>
45
+ <button type="button" data-poster-size="a1" aria-pressed="false">A1</button>
46
+ <button type="button" data-poster-size="36x48" aria-pressed="false">36 × 48 in<span class="poster-size-face">, landscape</span></button>
47
+ <button type="button" data-poster-size="48x36" aria-pressed="false">48 × 36 in<span class="poster-size-face">, portrait</span></button>
48
+ </div>
49
+ <button type="button" data-poster-print>Print</button>
50
+ <span class="poster-status" data-poster-status>A0, 841 mm wide x 1189 mm tall, three columns</span>
51
+ <button type="button" data-rshow-mode-toggle></button>
52
+ </div>
53
+
54
+ <div class="poster-stage">
55
+
56
+ <div class="poster" data-size="a0">
57
+
58
+ <header class="poster-head">
59
+ <h1 class="poster-title">Publishing a folder as an artifact that keeps working</h1>
60
+ <div class="poster-byline">
61
+ <div class="poster-who">
62
+ <p class="poster-authors">[Author One]<sup>1</sup>, [Author Two]<sup>1</sup>, [Author Three]<sup>2</sup></p>
63
+ <p class="poster-affil"><sup>1</sup> [Affiliation, department]</p>
64
+ <p class="poster-affil"><sup>2</sup> [Second affiliation]</p>
65
+ <p class="poster-venue">[Conference name] [Year], poster [n]</p>
66
+ </div>
67
+ <p class="poster-logos">[Logo] [Logo] [Logo]</p>
68
+ <div class="poster-qr" data-qr="https://art.example.com/poster/">
69
+ <p class="poster-qr-url"><a href="https://art.example.com/poster/">art.example.com/poster</a></p>
70
+ </div>
71
+ </div>
72
+ </header>
73
+
74
+ <main class="poster-cols">
75
+
76
+ <section>
77
+ <h2>The problem</h2>
78
+ <p>A link sent in a calendar invite outlives the slide it points at. Most
79
+ publishing tools keep a mutable page behind a stable address, so every
80
+ edit silently rewrites what a reader will see next week, and a citation
81
+ to last year's talk opens this year's version of it.</p>
82
+ <p>rshow takes the other side. A publish writes a numbered version, a
83
+ version never changes, and the address that follows the newest version
84
+ is a separate promise from the address that holds one.</p>
85
+ <p>The claim under test is narrow: after the first publish, the bytes a
86
+ republish sends track the bytes that changed, not the size of the
87
+ folder.</p>
88
+ </section>
89
+
90
+ <section>
91
+ <h2>What a publish does</h2>
92
+ <p>rshow publishes a folder. It hashes every file, writes a manifest,
93
+ uploads what the host does not already hold and records the version
94
+ last, so a publish that fails leaves the previous version in place.</p>
95
+ <ol>
96
+ <li>Read the folder, and run the build command if <code>rshow.json</code> names one.</li>
97
+ <li>Hash every file and write the manifest.</li>
98
+ <li>Upload the files whose hash the host lacks.</li>
99
+ <li>Write the version row, then move the live link.</li>
100
+ </ol>
101
+ <p>The record is the only mutable object in the system: one row per
102
+ slug, holding the title, the owner, the mode, the newest version number
103
+ and the pin if there is one. Content addressing does the rest, because
104
+ a file is stored under the hash of its bytes, so the same picture in two
105
+ decks is stored once.</p>
106
+ </section>
107
+
108
+ <section>
109
+ <h2>What a republish sends</h2>
110
+ <figure>
111
+ <img src="poster-figure.svg" width="720" height="640" alt="Example data: horizontal bars of megabytes uploaded at each of six publishes of one folder, falling from 120 for the first publish to 6 for the last two.">
112
+ <figcaption>Example data, not a measurement: megabytes uploaded per
113
+ publish for six publishes of one folder. The bars are direct labels,
114
+ so no legend sits between the chart and the reader.</figcaption>
115
+ </figure>
116
+ <p>The first publish sends the whole folder, because the store is empty.
117
+ Every later one sends the files whose hash the host lacks, which is the
118
+ same rule the cache header follows: a versioned path never changes, so
119
+ it may be kept for a year, while the live link is rechecked on every
120
+ use.</p>
121
+ </section>
122
+
123
+ <section>
124
+ <h2>Key findings</h2>
125
+ <ul>
126
+ <li>A version path never changes, so a citation to it stays true.</li>
127
+ <li>A republish sends the files that changed, not the folder.</li>
128
+ <li>An immutable path may be cached for a year; the live link is rechecked every time.</li>
129
+ <li>A pin holds one version in place while the folder moves behind it.</li>
130
+ </ul>
131
+ </section>
132
+
133
+ <section>
134
+ <h2>Where it holds</h2>
135
+ <p>A version that never changes is also a version that is hard to
136
+ withdraw. A link that has reached one reader can be deleted from the
137
+ host but not from the copy that reader kept.</p>
138
+ <p>The record assumes one writer at a time. Two people publishing the
139
+ same slug in the same second resolve to one version, and the loser
140
+ publishes again; we take that over a lock, because the case is rare and
141
+ the recovery is cheap.</p>
142
+ <p>There is no per-link grant and no expiring URL. A closed artifact is
143
+ closed by the identity provider and the share list, not by a token in
144
+ the address.</p>
145
+ </section>
146
+
147
+ <section>
148
+ <h2>What comes next</h2>
149
+ <p>The experiment is one folder, edited as a person edits a talk:
150
+ publish after every edit, record the bytes the upload sent, and repeat
151
+ with the cache cold and warm. A cold cache measures the host; a warm one
152
+ measures the reader.</p>
153
+ <p>The chart above is the shape we expect and says nothing about the
154
+ size of a real folder. A result we would publish is the same chart with
155
+ the folder, the host and the date named beside it.</p>
156
+ </section>
157
+
158
+ </main>
159
+
160
+ <footer class="poster-foot">
161
+ <h2 class="poster-refs-title">References</h2>
162
+ <ol class="poster-refs">
163
+ <li>Fielding, R., Nottingham, M. and Reschke, J. (eds). HTTP/1.1
164
+ Caching. RFC 7234, IETF, June 2014.</li>
165
+ <li>Berners-Lee, T. Cool URIs don't change. W3C, 1998.</li>
166
+ <li>Fielding, R. T. Architectural Styles and the Design of Network-based
167
+ Software Architectures. Doctoral dissertation, University of California,
168
+ Irvine, 2000.</li>
169
+ <li>IBM. Carbon Design System. IBM Corporation, 2025.</li>
170
+ <li>Tufte, E. R. The Visual Display of Quantitative Information.
171
+ Graphics Press, Cheshire, Connecticut, 1983.</li>
172
+ <li>Arase, K. qrcode-generator, MIT licence, 2009 to 2024.</li>
173
+ </ol>
174
+ </footer>
175
+
176
+ </div>
177
+
178
+ </div>
179
+
180
+ </body>
181
+ </html>
@@ -0,0 +1,229 @@
1
+ <!doctype html>
2
+ <html lang="en">
3
+ <head>
4
+ <meta charset="utf-8">
5
+ <meta name="viewport" content="width=device-width, initial-scale=1">
6
+ <meta name="color-scheme" content="light dark">
7
+ <title>rshow: publishing a folder as an immutable artifact</title>
8
+ <!--
9
+ A project page: the landing page of a paper. Theme links, one per file, all
10
+ at the same pinned version:
11
+
12
+ <link rel="stylesheet" href="/_themes/<name>@<n>/fonts.css">
13
+ <link rel="stylesheet" href="/_themes/<name>@<n>/tokens.css">
14
+ <link rel="stylesheet" href="/_themes/<name>@<n>/project.css">
15
+ <script src="/_themes/<name>@<n>/mode.js"></script>
16
+ <script defer src="/_themes/<name>@<n>/project.js"></script>
17
+
18
+ This copy links the theme folder itself, so it previews from a local checkout
19
+ and makes no remote request. mode.js runs in the head, before the body paints.
20
+ project.js is deferred and does one thing: the copy button on the BibTeX
21
+ entry, with the clipboard API and a fallback that selects the text.
22
+
23
+ Read <div class="project"> as one column. The children are the title block,
24
+ the teaser, <main> and the footer; the teaser carries class="wide" and takes
25
+ the wider measure. The teaser is an <img>, so teaser.svg carries its own light
26
+ and dark values.
27
+
28
+ Every person, affiliation, venue, address and number here is a placeholder.
29
+ The two exhibits under "Key results" are example data and say so.
30
+ -->
31
+ <link rel="stylesheet" href="../fonts.css">
32
+ <link rel="stylesheet" href="../tokens.css">
33
+ <link rel="stylesheet" href="../project.css">
34
+ <script src="../mode.js"></script>
35
+ <script defer src="../project.js"></script>
36
+ </head>
37
+ <body>
38
+
39
+ <div class="project">
40
+
41
+ <header class="project-head">
42
+ <h1>rshow: publishing a folder as an immutable artifact</h1>
43
+ <p class="authors">[Author One]<sup>1,*</sup>, [Author Two]<sup>1,*</sup>,
44
+ [Author Three]<sup>2</sup>, [Author Four]<sup>2</sup></p>
45
+ <p class="affiliations"><sup>1</sup> [Affiliation One],
46
+ <sup>2</sup> [Affiliation Two]</p>
47
+ <p class="marks"><sup>*</sup> Equal contribution.</p>
48
+ <p class="venue">[Example venue], 2025</p>
49
+
50
+ <nav class="links" aria-label="Paper resources">
51
+ <a class="btn btn--tertiary" href="https://example.org/rshow-paper.pdf">
52
+ <svg class="icon" viewBox="0 0 16 16" fill="none" stroke="currentColor" stroke-width="1.5" aria-hidden="true" focusable="false">
53
+ <path d="M3.5 1.5h6l3 3v10h-9z"></path>
54
+ <path d="M9.5 1.5v3.5h3.5"></path>
55
+ </svg>
56
+ <span class="btn-label">Paper PDF</span>
57
+ </a>
58
+ <a class="btn" href="https://example.org/rshow-code">
59
+ <svg class="icon" viewBox="0 0 16 16" fill="none" stroke="currentColor" stroke-width="1.5" aria-hidden="true" focusable="false">
60
+ <path d="M5.5 5 2.5 8l3 3"></path>
61
+ <path d="M10.5 5l3 3-3 3"></path>
62
+ </svg>
63
+ <span class="btn-label">Code</span>
64
+ </a>
65
+ <a class="btn" href="https://example.org/rshow-artifact">
66
+ <svg class="icon" viewBox="0 0 16 16" fill="none" stroke="currentColor" stroke-width="1.5" aria-hidden="true" focusable="false">
67
+ <path d="M2.5 5.5 8 2.5l5.5 3v5L8 13.5l-5.5-3z"></path>
68
+ <path d="M2.5 5.5 8 8.5l5.5-3"></path>
69
+ <path d="M8 8.5v5"></path>
70
+ </svg>
71
+ <span class="btn-label">Artifact</span>
72
+ </a>
73
+ <a class="btn" href="https://example.org/rshow-video">
74
+ <svg class="icon" viewBox="0 0 16 16" fill="none" stroke="currentColor" stroke-width="1.5" aria-hidden="true" focusable="false">
75
+ <rect x="1.5" y="2.5" width="13" height="11"></rect>
76
+ <path d="M6.5 5.5l4 2.5-4 2.5z"></path>
77
+ </svg>
78
+ <span class="btn-label">Video</span>
79
+ </a>
80
+ <a class="btn" href="https://example.org/rshow-slides">
81
+ <svg class="icon" viewBox="0 0 16 16" fill="none" stroke="currentColor" stroke-width="1.5" aria-hidden="true" focusable="false">
82
+ <rect x="1.5" y="2.5" width="13" height="9"></rect>
83
+ <path d="M8 11.5v2.5"></path>
84
+ <path d="M5.5 14h5"></path>
85
+ </svg>
86
+ <span class="btn-label">Slides</span>
87
+ </a>
88
+ </nav>
89
+ </header>
90
+
91
+ <figure class="teaser wide">
92
+ <img src="teaser.svg" width="800" height="210" alt="A folder of files is published into a version, and the version is served through two links: a newest link that follows each publish and a pinned link that holds one version.">
93
+ <figcaption>One folder, one numbered version and two kinds of address.
94
+ The version never changes after it is written, so the newest link is the
95
+ only address that moves.</figcaption>
96
+ </figure>
97
+
98
+ <main>
99
+
100
+ <p class="tldr"><strong>TL;DR.</strong> rshow publishes a talk as a numbered
101
+ version whose bytes never change, so a link sent before a talk still opens
102
+ the same deck a year later, and a republish sends only what the edit
103
+ touched.</p>
104
+
105
+ <section class="abstract" aria-labelledby="abstract-title">
106
+ <h2 id="abstract-title">Abstract</h2>
107
+ <p>A link sent in a calendar invite outlives the slide it points at. Most
108
+ publishing tools answer this by keeping one mutable page behind a stable
109
+ address, so an edit made tonight silently rewrites what a reader opens
110
+ next week. rshow takes the other side. A publish writes a numbered version
111
+ of the folder, a version never changes once it is written, and the address
112
+ that follows the newest version is a separate promise from the address
113
+ that holds one version in place. This paper describes the design we ship,
114
+ the record an artifact carries, the caching rules that follow from
115
+ immutability, the share model that decides who may read a link, and the
116
+ experiment we would run to test the claim that a republish sends only what
117
+ changed.</p>
118
+ </section>
119
+
120
+ <section aria-labelledby="results-title">
121
+ <h2 id="results-title">Key results</h2>
122
+ <p>We have not run a controlled study, so the two exhibits below are
123
+ example data. They show the shape of the claim rather than a measurement
124
+ of any host: after the first publish, the bytes a republish sends track
125
+ what the edit touched, not the size of the folder.</p>
126
+
127
+ <figure>
128
+ <svg viewBox="0 0 600 240" role="img" aria-label="Example data: megabytes uploaded on a republish of one folder. The first publish sends 120 megabytes, a new section 46, a new figure 13 and a typo fix 4.">
129
+ <g style="fill: var(--accent)">
130
+ <rect x="30" y="50" width="70" height="120"></rect>
131
+ <rect x="175" y="124" width="70" height="46"></rect>
132
+ <rect x="320" y="157" width="70" height="13"></rect>
133
+ <rect x="465" y="166" width="70" height="4"></rect>
134
+ </g>
135
+ <g style="font-family: var(--font-sans); font-size: 16px; fill: var(--fg); font-variant-numeric: tabular-nums; text-anchor: middle">
136
+ <text x="65" y="40">120</text>
137
+ <text x="210" y="114">46</text>
138
+ <text x="355" y="147">13</text>
139
+ <text x="500" y="156">4</text>
140
+ </g>
141
+ <line x1="20" y1="170" x2="580" y2="170" style="stroke: var(--border-strong); stroke-width: 1"></line>
142
+ <g style="font-family: var(--font-sans); font-size: 13px; fill: var(--muted); text-anchor: middle">
143
+ <text x="65" y="192">first publish</text>
144
+ <text x="210" y="192">new section</text>
145
+ <text x="355" y="192">new figure</text>
146
+ <text x="500" y="192">typo fix</text>
147
+ </g>
148
+ <text x="20" y="224" style="font-family: var(--font-sans); font-size: 13px; fill: var(--muted)">Example data, not a measurement.</text>
149
+ </svg>
150
+ <figcaption>Megabytes uploaded per publish, by the kind of edit that
151
+ preceded it. One series, so it takes the interactive blue and every
152
+ value is labelled where it is read.</figcaption>
153
+ </figure>
154
+
155
+ <div class="table">
156
+ <table>
157
+ <caption>Example data: one publish of the folder in the figure
158
+ above, timed with the host's store empty and then holding the
159
+ bytes.</caption>
160
+ <thead>
161
+ <tr>
162
+ <th scope="col">Step</th>
163
+ <th scope="col" class="num-cell">Cold store</th>
164
+ <th scope="col" class="num-cell">Warm store</th>
165
+ </tr>
166
+ </thead>
167
+ <tbody>
168
+ <tr>
169
+ <th scope="row">Hash the folder</th>
170
+ <td class="num-cell">310 ms</td>
171
+ <td class="num-cell">310 ms</td>
172
+ </tr>
173
+ <tr>
174
+ <th scope="row">Upload the missing files</th>
175
+ <td class="num-cell">4.2 s</td>
176
+ <td class="num-cell">41 ms</td>
177
+ </tr>
178
+ <tr>
179
+ <th scope="row">Write the version record</th>
180
+ <td class="num-cell">12 ms</td>
181
+ <td class="num-cell">12 ms</td>
182
+ </tr>
183
+ </tbody>
184
+ </table>
185
+ </div>
186
+
187
+ <p>The hash and the record cost the same either way, because they are
188
+ reads and one small write. The upload is the whole difference, and it is
189
+ also the reason a republish of a folder left alone sends nothing.</p>
190
+ </section>
191
+
192
+ <section aria-labelledby="cite-title">
193
+ <h2 id="cite-title">BibTeX</h2>
194
+ <div class="bibtex-block">
195
+ <pre id="bibtex-entry"><code>@inproceedings{rshow2025,
196
+ title = {rshow: publishing a folder as an immutable artifact},
197
+ author = {[Author One] and [Author Two] and others},
198
+ booktitle = {[Example venue]},
199
+ year = {2025},
200
+ note = {Example entry: authors, venue and address are placeholders.}
201
+ }</code></pre>
202
+ <div class="copy-row">
203
+ <button class="btn" type="button" data-rshow-copy="bibtex-entry">
204
+ <svg class="icon" viewBox="0 0 16 16" fill="none" stroke="currentColor" stroke-width="1.5" aria-hidden="true" focusable="false">
205
+ <rect x="5.5" y="5.5" width="8" height="9"></rect>
206
+ <path d="M10.5 3.5v-1h-8v9h1"></path>
207
+ </svg>
208
+ <span class="btn-label">Copy</span>
209
+ </button>
210
+ <p class="copy-status" role="status" aria-live="polite"></p>
211
+ </div>
212
+ </div>
213
+ </section>
214
+
215
+ </main>
216
+
217
+ <footer class="project-foot">
218
+ <p class="ack">Acknowledgements. We thank [Name One] and [Name Two] for
219
+ reading drafts of this paper, and [Example funding body] for support under
220
+ grant [number].</p>
221
+ <p>Example page for the rshow theme <strong>default</strong>. The authors,
222
+ the affiliations, the venue, the addresses and every number on this page are
223
+ placeholders, and the two exhibits under Key results are example data.</p>
224
+ </footer>
225
+
226
+ </div>
227
+
228
+ </body>
229
+ </html>