tc39
diff --git a/Diff for: ‎PUBLISHING.md
+20 b/Diff for: ‎PUBLISHING.md
+20
diff --git a/Diff for: ‎img/ecma-header.svg
+1 b/Diff for: ‎img/ecma-header.svg
+1
diff --git a/Diff for: ‎img/ecma-logo.svg
+1-120 b/Diff for: ‎img/ecma-logo.svg
+1-120
diff --git a/Diff for: ‎img/figure-1.svg
+1-1 b/Diff for: ‎img/figure-1.svg
+1-1
diff --git a/Diff for: ‎img/figure-2.svg
+1-1 b/Diff for: ‎img/figure-2.svg
+1-1
diff --git a/Diff for: ‎img/module-graph-cycle-async.svg
+1-69 b/Diff for: ‎img/module-graph-cycle-async.svg
+1-69
diff --git a/Diff for: ‎img/module-graph-cycle.svg
+1-63 b/Diff for: ‎img/module-graph-cycle.svg
+1-63
diff --git a/Diff for: ‎img/module-graph-missing.svg
+1-48 b/Diff for: ‎img/module-graph-missing.svg
+1-48
@@ -0,0 +1,20 @@
+# Publishing the annual PDF
+
+First, make sure you've provided appropriate front matter. `title`, `shortname`, `version`, and `date` are **mandatory**. If generating a final annual edition, date should reflect the date of the Ecma GA which will ratify the Standard. For example:
+
+```
+title: ECMAScript® 2024 Language Specification
+shortname: ECMA-262
+version: 15th Edition
+date: 2024-06-25
+```
+
+Use the package script `build-for-pdf`. Importantly, you want to make sure your image directory and print.css file wind up in the same output directory as your markup, i.e.  your `ecmarkup` command should include the options `--assets external`, `--assets-dir out`, and `--old-toc`.
+
+Then, run `prince` to generate your PDF.
+
+```shell
+prince --script ./node_modules/ecmarkup/js/print.js out/index.html -o path/to/output.pdf
+```
+
+Spend 5-10 minutes double-checking the PDF for egregious layout issues. That means quickly skimming all 800+ pages looking for whitespace or content split in a confusing manner. Tinker with `print.css` only as needed. Compare cover & table of contents to previous years.