Add cover and publishing assets

Author: happi

.gitignore

@@ -16,6 +16,8 @@ beam-book.pdf
 beam-book-a4.pdf
 beam-book.epub
 beam-book-publish.pdf
+back_of_cover.pdf
+back_jacket.pdf
 opcodes_doc.asciidoc
 .#.gitignore
 genop.tab

README.md

@@ -1,40 +1,56 @@
-![Pages Build](https://github.com/happi/theBeamBook/actions/workflows/gh-pages.yml/badge.svg) 
+![Pages Build](https://github.com/happi/theBeamBook/actions/workflows/gh-pages.yml/badge.svg)
 ![PDF Build](https://github.com/happi/theBeamBook/actions/workflows/build-pdf.yml/badge.svg)
 
 [Download latest PDF](https://github.com/happi/theBeamBook/releases/latest/download/beam-book-a4.pdf)
 
 # The BEAM Book
 
-**1.0 — First Edition now *in print***
+This repository contains the latest free and open edition of The BEAM Book,
+a deep dive into the internals of the Erlang runtime system and its virtual
+machine, the BEAM.
 
-Grab the tree‑ware from your local Amazon store:
+The current open edition is **1st Edition** (2025), licensed under CC BY 4.0.
 
-* 🇺🇸 [US](https://www.amazon.com/dp/9153142535)
-* 🇬🇧 [UK](https://www.amazon.co.uk/dp/9153142535)
-* 🇩🇪 [DE](https://www.amazon.de/dp/9153142535)
-* 🇸🇪 [SE](https://www.amazon.se/dp/9153142535)
+You can read the book as a [PDF](https://github.com/happi/theBeamBook/releases/latest),
+[browse it online](https://happi.github.io/theBeamBook/), or read the
+AsciiDoc source directly on GitHub starting from [book.asciidoc](book.asciidoc).
 
-This project documents the internals of the Erlang runtime system and its virtual machine, the **BEAM**.
+The printed edition is available on Amazon:
+[US](https://www.amazon.com/dp/9153142535) |
+[UK](https://www.amazon.co.uk/dp/9153142535) |
+[DE](https://www.amazon.de/dp/9153142535) |
+[SE](https://www.amazon.se/dp/9153142535)
 
-You can read or download the book as a PDF (current stable release **1.0 – First Edition**) from the [latest stable release](https://github.com/happi/theBeamBook/releases/latest) or [browse it online](https://happi.github.io/theBeamBook/).
+## Edition Policy
 
-The book is written in AsciiDoc and most chapters can be read directly from source on GitHub. Open [book.asciidoc](book.asciidoc) for a quick start.
+This book follows a rolling open model.
 
-You can also read it as a [GitHub Pages site](https://happi.github.io/theBeamBook/).
+- The newest edition is published commercially.
+- The previous edition is released publicly in this repository.
+- Over time, all major editions become open.
+
+This means the open version may lag behind the latest printed edition.
+The open version is stable and complete, but may not contain the newest
+chapters or revisions.
 
 ## Contributing
 
-The goal is a collaborative, authoritative reference on the Erlang runtime system. Please contribute—this work is far from complete.
+Contributions are welcome. Raise an issue, comment on open threads, or
+open a pull request.
 
-* Raise an issue, comment on open threads, or open a pull request.
-* All contributions fall under the project’s Creative Commons licence (see below).
+By submitting a pull request, you agree that your contribution is licensed
+under the same license as this repository (CC BY 4.0). Contributions may
+appear in future commercial editions of the book with attribution.
 
 Each chapter can be in one of four states:
 
-1. **Placeholder** — only a title and maybe an outline. Grab the matching issue and start writing.
-2. **First draft** — the text is mostly there but needs editing: missing content, clarity, diagram tweaks, etc.
-3. **Final draft** — typo‑hunting and polishing.
-4. **Done (for OTP X)** — until a newer OTP version changes things.
+1. **Placeholder** -- only a title and maybe an outline.
+2. **First draft** -- the text is mostly there but needs editing.
+3. **Final draft** -- typo-hunting and polishing.
+4. **Done (for OTP X)** -- until a newer OTP version changes things.
+
+For larger rewrites, check the chapter's status and existing issues.
+Coordinate with any active authors before heavy edits.
 
 ### Style guide
 
@@ -44,164 +60,74 @@ AsciiDoc constructs should render nicely in this order of priority:
 2. HTML output
 3. Direct view on GitHub
 
-We’ll accumulate specific do’s and don’ts here as we learn what works.
-
-#### Comments in AsciiDoc
+#### Linking to OTP source code
 
-Each chapter starts with a comment marking its status (`// Placeholder`, `// First Draft`, etc.) and possibly a link to an issue that tracks next steps.
-
-#### Linking to OTP/Erlang source code
-
-Always link to a *tagged* OTP version, e.g.
+Always link to a tagged OTP version, e.g.
 
 ```
 link:https://github.com/erlang/otp/blob/OTP-19.1/erts/emulator/beam/erl_time.h[erl_time.h]
 ```
 
-#### Directory structure and build
+#### Directory structure
 
-* Chapters live under `chapters/` in their own `.asciidoc` files (use `_` for word breaks).
-* Code samples go in `code/CHAPTERNAME_chapter/src` and are included via `ap-code_listings.asciidoc`.
-* Images sit in `images/`.
+- Chapters live under `chapters/` in their own `.asciidoc` files.
+- Code samples go in `code/CHAPTERNAME_chapter/src`.
+- Images sit in `images/`.
 
 #### Tag conventions
 
-* Chapters: `CH-…`
-* Parts: `P-…`
-* Sections: `SEC-…`
-* Figures: `FIG-…`
-* Appendices: `AP-…`
-* Code listings: `LISTING-…`
-
-### Process
+- Chapters: `CH-...`
+- Parts: `P-...`
+- Sections: `SEC-...`
+- Figures: `FIG-...`
+- Appendices: `AP-...`
+- Code listings: `LISTING-...`
 
-Found something odd or incorrect? Open an issue in the [tracker](https://github.com/happi/theBeamBook/issues).
+## Commercial Editions
 
-Spotted a typo? File a quick PR.
+Printed and Kindle editions help fund continued work on this book.
+If you want the most recent version and professionally typeset formats,
+consider purchasing the latest edition.
 
-For larger rewrites, check the chapter’s status and existing issues. Coordinate with any active authors before heavy edits.
+## Building the PDF locally
 
----
-
-## Building the PDF locally from source
-
-A `Makefile` builds both PDF and HTML. With dependencies installed, run:
+A `Makefile` builds both PDF and HTML. With dependencies installed:
 
 ```shell
-make
+bundle install
+bundle exec make pdf-a4
 ```
 
-Result: `beam-book.pdf` in the project root and an HTML copy under `site/`.
-
 Docker users can avoid local installs:
 
 ```shell
-make docker-build  # build the image
-make docker        # build the book inside the container
+make docker-build
+make docker
 ```
 
-Devcontainer aficionados: open the repo in your IDE’s devcontainer and just run `make`.
-
 ### Manual dependencies
 
-See platform‑specific instructions below if you prefer native builds.
-
 #### Linux (Debian/Ubuntu)
 
 ```shell
 sudo apt install git rsync wget curl make \
                  ruby ruby-dev default-jre \
                  asciidoctor graphviz
-sudo gem install asciidoctor-pdf asciidoctor-diagram rouge
-make
+bundle install
+bundle exec make pdf-a4
 ```
 
 #### macOS + Homebrew
 
-Build on macOS prior version 15
-
-```shell
-brew install asciidoctor graphviz wget ditaa
-sudo gem install asciidoctor-pdf asciidoctor-diagram rouge
-make
-```
-
-macOS 15 ships with ruby 2.6+ while rouge 4.5+ requires ruby 2.7+. Use following
-to install required tools and libraries
-
 ```shell
 brew install asciidoctor graphviz wget ditaa ruby
-```
-
-This will install ruby 3.3+, but to avoid errors new ruby not added to PATH. To fix this
-add ruby to PATH manually in command shell (or add to shell's rc file):
-
-```shell
 export PATH=$(brew --prefix ruby)/bin:$PATH
-```
-
-Install required ruby libraries:
-
-```shell
 bundle install
-```
-
-and then run build pdf file with
-
-```shell
-make
+bundle exec make pdf-a4
 ```
 
 ## Licence
 
-*The Erlang Runtime System* by **Erik Stenman** is licensed under **CC BY 4.0**. See [LICENSE](LICENSE) for details.
-
----
-
-# A short and personal history of the book
-
-I, Erik Stenman (Happi), started writing this book back in 2013.
-After twelve years of starts, stops, and rewrites, version 1.0
-ships—less because the BEAM has stopped evolving, and more because
-it felt time to draw a line in the sand.
-
-At first, I was thinking of self‑publishing the book on my blog,
-but since English isn't my native language, I felt I needed help
-from a good editor.
-
-I managed to get a deal with O'Reilly and started converting my
-outline to their build process. My original plan was for a very long
-and thorough book, which the editor felt would get few readers. I
-started cutting my content and tried to write more of a tutorial than
-a manual. Unfortunately, progress was slow, and pre-sales were even
-slower, and the publisher cancelled the book in 2015.
-
-I managed to get a new deal with Pragmatic. I started converting my
-content to their build system and rewriting the book according to the
-more pragmatic style of the new publisher, cutting down the content
-even further. The series editor also wanted me to fit the book into
-the Elixir series, and I tried to add more Elixir examples. I did not
-manage to make it into an Elixir book, and my progress was
-still slow, which led to another cancellation of the book in early 2017.
-
-Now I had three repositories with three different book-building systems
-with three different outlines of the book. In the end, I more or less
-went back to the original longer book outline and the original AsciiDoc
-build system. I started a new repository in a private GitHub account and
-started pulling in content from the three different versions.
-
-Then on April 7, 2017, I opened the repository to the public to share it with
-some students. I didn't think anyone else would notice, and I was not
-planning to release the book for real yet since the repo currently
-contains bits and pieces from the different versions of the book.
-
-There was more interest than I had expected, though, and fortunately,
-also several who were willing to contribute. From now on, the book
-is a collaborative effort to document the Erlang runtime system, ERTS
-and the Erlang virtual machine BEAM,
-and it is released with a Creative Commons license (see above).
-
-Watch this space for further news and to see the whole book take shape.
-
--- Erik Stenman aka Happi
-
+*The Erlang Runtime System* by Erik Stenman is licensed under
+**Creative Commons Attribution 4.0 International (CC BY 4.0)**.
+See [LICENSE](LICENSE) for details.

cover.pdf

@@ -0,0 +1,68 @@
+---
+geometry: "paperwidth=6in,paperheight=9in,margin=0.6in"
+fontsize: 11pt
+pagestyle: empty
+mainfont: "Lato"
+header-includes:
+  - \usepackage{xcolor}
+  - \color{white}
+  - \usepackage{graphicx}
+  - \usepackage{eso-pic}
+  - \AddToShipoutPictureBG{\AtPageLowerLeft{\includegraphics[width=\paperwidth,height=\paperheight]{publishing/bg_texture.jpg}}}
+---
+
+\vspace*{1.5cm}
+
+\noindent
+\begin{minipage}[t]{1.3in}
+\vspace{0pt}
+\includegraphics[width=1.3in]{publishing/erik_cropped.jpg}
+\end{minipage}
+\hfill
+\begin{minipage}[t]{2.8in}
+\vspace{0pt}
+\begingroup\small
+\textbf{Erik Stenman} is a software engineer, researcher, and entrepreneur with
+deep expertise in Erlang, BEAM, and high-performance distributed systems.
+As one of the early pioneers in BEAM internals, Erik has spent decades
+optimizing concurrent systems and designing fault-tolerant architectures.
+\endgroup
+\end{minipage}
+
+\vspace{0.3cm}
+\noindent\textcolor{white!40}{\rule{\linewidth}{0.4pt}}
+\vspace{0.6cm}
+
+BEAM is the heart of Erlang and Elixir, powering fault-tolerant, concurrent,
+and distributed systems used in finance, telecom, and messaging platforms
+worldwide.
+
+\vspace{0.3cm}
+
+This book takes you deep into the Erlang RunTime System (ERTS), revealing
+how the BEAM VM works under the hood. It provides the technical depth you
+need to master process scheduling, memory management, and bytecode execution.
+
+\vspace{0.3cm}
+
+- BEAM internals and bytecode execution
+- Process scheduling and concurrency
+- Memory management and garbage collection
+- Profiling, debugging, and tracing BEAM applications
+
+\vspace{0.6cm}
+
+\begingroup\small\noindent
+The HappiHacking Systems Series focuses on scalable architecture, runtime
+behavior, and ownership-driven system design in high-complexity environments.
+\endgroup
+
+\vfill
+
+\noindent
+\begin{minipage}[b]{2.5in}
+\begingroup\scriptsize
+Published by HappiHacking, Stockholm, Sweden\\
+\texttt{happihacking.com}
+\endgroup
+\end{minipage}

publishing/back_jacket.md

@@ -0,0 +1,11 @@
+---
+geometry: "paperwidth=6in,paperheight=9in,margin=0in"
+pagestyle: empty
+header-includes:
+  - \usepackage{graphicx}
+  - \usepackage{eso-pic}
+  - \AddToShipoutPictureBG{\AtPageLowerLeft{\includegraphics[width=\paperwidth,height=\paperheight]{publishing/bg_texture.jpg}}}
+---
+
+\thispagestyle{empty}
+\mbox{}

publishing/back_of_cover.md

@@ -0,0 +1,38 @@
+---
+geometry: "paperwidth=6in,paperheight=9in,margin=0in"
+pagestyle: empty
+header-includes:
+  - \usepackage{graphicx}
+  - \usepackage{xcolor}
+  - \usepackage{fontspec}
+  - \setmainfont{Lato}
+  - \usepackage{tikz}
+  - \usepackage{eso-pic}
+  - \AddToShipoutPictureBG*{\includegraphics[width=\paperwidth,height=\paperheight]{resources/redcover.jpg}}
+---
+
+\begin{tikzpicture}[remember picture, overlay]
+% Title
+\node at ([yshift=-1.3in]current page.north)
+  {\fontsize{40}{48}\selectfont\color{white}The};
+\node at ([yshift=-2.5in]current page.north)
+  {\fontsize{72}{84}\selectfont\bfseries\color{white}BEAM};
+\node at ([yshift=-3.5in]current page.north)
+  {\fontsize{52}{62}\selectfont\bfseries\color{white}Book};
+% Rule
+\draw[white, opacity=0.4, line width=0.5pt]
+  ([yshift=-4.1in, xshift=-1.5in]current page.north) --
+  ([yshift=-4.1in, xshift=1.5in]current page.north);
+% Subtitle
+\node at ([yshift=-4.7in]current page.north)
+  {\fontsize{15}{22}\selectfont\color{white}Understanding the Erlang};
+\node at ([yshift=-5.05in]current page.north)
+  {\fontsize{15}{22}\selectfont\color{white}Runtime System};
+% Author
+\node at ([yshift=1.0in]current page.south)
+  {\fontsize{31}{36}\selectfont\bfseries\color{white}Erik Stenman};
+% Publisher mark
+\node[opacity=0.45, anchor=south east]
+  at ([xshift=-0.4in, yshift=0.3in]current page.south east)
+  {\includegraphics[height=0.5in]{resources/hh_publisher_mark.png}};
+\end{tikzpicture}