Break up an em-dash in Colleen guide's opening paragraph

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

.gitignore

@@ -1 +1,4 @@
 *.pdf
+*.pptx
+!reference.pptx
+!archive/**

Makefile

@@ -1,10 +1,12 @@
-PANDOC     = pandoc
+PANDOC      = pandoc
-PDF_ENGINE = weasyprint
+PDF_ENGINE  = weasyprint
-TEMPLATE   = template.html
+TEMPLATE    = template.html
-CSS        = style.css
+CSS         = style.css
-PARTNERS   = $(patsubst %.md,%.pdf,$(wildcard partners/*.md))
+PPTX_REF    = reference.pptx
+PARTNERS    = $(patsubst %.md,%.pdf,$(wildcard partners/*.md))
+PPTX_PARTNERS = $(patsubst %.md,%.pptx,$(wildcard partners/*.md))
 
-.PHONY: all clean
+.PHONY: all slides clean
 
 all: template.pdf $(PARTNERS)
 
@@ -13,5 +15,16 @@ all: template.pdf $(PARTNERS)
 %.pdf: %.md $(TEMPLATE) $(CSS)
 	$(PANDOC) $< -o $@ --template=$(TEMPLATE) --pdf-engine=$(PDF_ENGINE) --standalone
 
+# Slide deck for screen-share recordings. pptx ignores style.css -- its look
+# (colors/fonts) comes from reference.pptx's slide master instead, so that's
+# the file to edit if the slide theme needs to change.
+slides: template.pptx $(PPTX_PARTNERS)
+
+%.pptx: %.md $(PPTX_REF)
+	$(PANDOC) $< -o $@ --reference-doc=$(PPTX_REF)
+
 clean:
-	rm -f template.pdf partners/*.pdf
+	rm -f template.pdf template.pptx partners/*.pdf partners/*.pptx
+
+partnership: template.md
+	cp template.md partners/$(SLUG).md

README.md

@@ -25,6 +25,35 @@ make clean                      # removes generated PDFs (never touches the .md
 `make` finds the source `.md` file automatically from the `.pdf` name you ask for, so
 building any filled-in template is just naming the PDF you want.
 
+## Building slides
+
+For recording a screen-share walkthrough of the guide, the same markdown builds
+a PowerPoint deck instead of a PDF:
+
+```sh
+make template.pptx              # slide deck for the base version
+make partners/<slug>.pptx        # a specific partnership's deck
+make slides                      # template.pptx + every partners/*.pptx
+```
+
+Pandoc turns each `##` heading into its own slide. The PDF no longer mirrors
+this one-section-per-page layout — since the guide has no per-step photography
+to fill a page, its sections flow together into continuous pages instead
+(see Notes below). The slide deck keeps one section per slide on purpose: it's
+built for a narrated screen-share, where your voice fills the space a printed
+page can't. If you want scripted talking points per slide, add a
+`::: notes` ... `:::` fenced div under a heading — pandoc exports those as
+speaker notes rather than slide body text.
+
+Pandoc's pptx writer doesn't read `style.css` (pptx isn't HTML-based), so the
+slide theme instead comes from `reference.pptx` — a PowerPoint file whose
+slide master carries the colors and fonts, built once by hand-editing its
+theme XML to mirror `style.css`'s dark background, heading blue, body text,
+and accent colors, plus Roboto/Open Sans fonts. Edit it in PowerPoint/Keynote/
+Google Slides (or its `ppt/theme/theme1.xml` and
+`ppt/slideMasters/slideMaster1.xml` directly) if the slide theme ever needs to
+diverge from or resync with the PDF's.
+
 ## Starting a new partnership
 
 ```sh
@@ -32,7 +61,7 @@ cp template.md partners/<slug>.md
 ```
 
 Edit the new file's title (front matter) and rewrite the opening/closing copy to bridge
-your angle with the partner's audience — the 3 Step sections and their photos are
+your angle with the partner's audience — the 3 Step sections and their pull-quotes are
 generally reusable as-is. Then:
 
 ```sh
@@ -41,11 +70,25 @@ make partners/<slug>.pdf
 
 ## Notes
 
-- The 4 photos in `images/` were extracted from the original PDF. They're intentionally
+- `images/author-photo.jpg` is the only photo in the guide, used on the cover and
-  generic/illustrative (not specific to any one partnership) and don't need to change
+  closing page. The guide deliberately doesn't use stock photography anywhere else —
-  per customization.
+  matching reground.org, which carries its identity through color, type, and voice
+  rather than illustrative imagery. Each Step section instead gets a `.pull-quote`
+  div (see `style.css`) pulling one line verbatim from that section's own paragraph,
+  which gives the page visual rhythm without adding a picture.
+- The PDF's `h2` sections flow continuously (no forced page break) since there's no
+  photo to justify each Step having its own page. Only the cover and the closing CTA
+  force their own page break — a short guide with unbroken flow reads like a real
+  pamphlet rather than a slide deck exported to PDF.
 - `template.html` renders the cover (title + byline + author photo) from the document's
   YAML front matter — you don't need to hand-write that part in the body of each `.md`
   file, just update the front matter.
 - `style.css` is the single source of truth for the visual theme. Edit it once and
   `make all` rebuilds every partner PDF with the change.
+- The closing block's `:::: {.closing .columns}` / `::: {.column} :::` structure
+  matters for slides: pandoc's pptx writer silently drops an image if it shares a
+  plain div with paragraph text, but keeps it in a two-column div. `.closing .column`
+  in `style.css` flattens those columns back to a centered stack for the PDF, so the
+  printed page looks the same as before. Keep that structure when editing the
+  closing copy — a plain `::: {.closing}` div will make the author photo disappear
+  from the slide deck.

partners/colleen.md

@@ -0,0 +1,54 @@
+---
+title: The Quiet Way to Reach the Readers Who Actually Need Your Story
+author: Will Estes
+---
+
+You've probably been told the way to get your story out there is to hustle louder. More posts, more ads, more noise. If you're a sensitive, intuitive writer, that advice has probably never sat right with you. It's not that you don't want to be seen. It's that you already sense there's a truer way to find the people who need what you wrote.
+
+There is. And it starts with a reader who already found you.
+
+## Step 1: Find a review by a reader who deeply connected with your story.
+
+You're looking for reviews that go beyond "great book!" — the ones where a
+reader took time to describe what the story did to them. They might be on
+book-focused sites, blogs, or social media posts. These are the readers who
+got it. They're the seed of everything that follows.
+
+::: {.pull-quote}
+A reader who got it is the seed of it all.
+:::
+
+## Step 2: Comment on their review with heartfelt thanks.
+
+Thank the reviewer for their review. Ideally you do this on the review itself. Be as specific as they were. Be as warm as they were. You're not just
+thanking one reader. You're showing every future reader what it looks like
+when someone gets your work and you notice.
+
+::: {.pull-quote}
+You're not just thanking one reader.
+:::
+
+## Step 3: Share what they connected with in your story.
+
+Share what the reader actually connected with in your story publicly to
+your audience: on social media, your email list, wherever your readers are. Before you thanked them. Now you're responding to the specific thing they connected with.
+ You're not just responding to one person. You're becoming a beacon: showing
+other readers like them that your stories are out there and that someone
+who needed your stories already found them.
+
+:::: {.closing .columns}
+::: {.column width="30%"}
+![](images/author-photo.jpg){.author-photo}
+:::
+
+::: {.column width="70%"}
+By: Will Estes — ReGround
+
+**You don't need a bigger microphone. You need the one reader who's already looking for you.**
+
+Let's talk. I'll look at your specific situation, and we'll map out how you get
+your stories to the readers who need them.
+
+[Let's talk.](https://reground.org/talk){.cta-button}
+:::
+::::

partners/find-your-right-readers-Cheyenne.md

@@ -0,0 +1,54 @@
+---
+title: How To Get Your Stories In Front Of The Readers Who Need Them
+author: Will Estes
+---
+
+Most advice on making a living as a writer tells you to hustle, place ads with the right keywords and the like. That absolutely works. It's also not why you're an author.
+
+You want to know your story reached the one reader who needed it. And if there's one reader who needs your stories, there's more than one.
+
+## Step 1: Find a review by a reader who deeply connected with your story.
+
+You're looking for reviews that go beyond "great book!" — the ones where a
+reader took time to describe what the story did to them. They might be on
+book-focused sites, blogs, or social media posts. These are the readers who
+got it. They're the seed of everything that follows.
+
+::: {.pull-quote}
+A reader who got it is the seed of it all.
+:::
+
+## Step 2: Comment on their review with heartfelt thanks.
+
+Thank the reviewer for their review. Ideally you do this on the review itself. Be as specific as they were. Be as warm as they were. You're not just
+thanking one reader. You're showing every future reader what it looks like
+when someone gets your work and you notice.
+
+::: {.pull-quote}
+You're not just thanking one reader.
+:::
+
+## Step 3: Share what they connected with in your story.
+
+Share what the reader actually connected with in your story publicly to
+your audience: on social media, your email list, wherever your readers are. Before you thanked them. Now you're responding to the specific thing they connected with.
+ You're not just responding to one person. You're becoming a beacon: showing
+other readers like them that your stories are out there and that someone
+who needed your stories already found them.
+
+:::: {.closing .columns}
+::: {.column width="30%"}
+![](images/author-photo.jpg){.author-photo}
+:::
+
+::: {.column width="70%"}
+By: Will Estes — ReGround
+
+**You don't need a bigger microphone. You need the one reader who's already looking for you.**
+
+Let's talk. I'll look at your specific situation, and we'll map out how you get
+your stories to the readers who need them.
+
+[Let's talk.](https://reground.org/talk){.cta-button}
+:::
+::::

style.css

@@ -48,18 +48,25 @@ a {
 
 .cover .author-photo {
   width: 90px;
+  height: 90px;
+  object-fit: cover;
   border-radius: 50%;
   margin: 1.5rem 0 0;
 }
 
-/* One Step per page, like the original PDF */
 h2 {
-  page-break-before: always;
   font-size: 1.5rem;
 }
 
-h2:first-of-type {
+.pull-quote {
-  page-break-before: avoid;
+  font-family: "Roboto", -apple-system, BlinkMacSystemFont, "Segoe UI", Helvetica, Arial, sans-serif;
+  font-size: 1.9rem;
+  font-weight: 700;
+  line-height: 1.35;
+  color: #8fa8d1;
+  border-left: 4px solid #2dd4c4;
+  padding-left: 1.25rem;
+  margin: 2.5rem 0;
 }
 
 img {
@@ -74,8 +81,17 @@ img {
   text-align: center;
 }
 
+/* .closing is also a pandoc "columns" div (photo | text) so its image
+   survives in slide exports -- neutralize the side-by-side layout here so
+   the PDF still renders it as a centered stack. */
+.closing .column {
+  width: auto !important;
+}
+
 .closing .author-photo {
   width: 100px;
+  height: 100px;
+  object-fit: cover;
   border-radius: 50%;
   margin: 0 auto 1rem;
 }

template.md

@@ -3,6 +3,10 @@ title: How To Get Your Stories In Front Of The Readers Who Need Them
 author: Will Estes
 ---
 
+Most advice on making a living as a writer tells you to hustle, place ads with the right keywords and the like. That absolutely works. It's also not why you're an author.
+
+You want to know your story reached the one reader who needed it. And if there's one reader who needs your stories, there's more than one.
+
 ## Step 1: Find a review by a reader who deeply connected with your story.
 
 You're looking for reviews that go beyond "great book!" — the ones where a
@@ -10,37 +14,41 @@ reader took time to describe what the story did to them. They might be on
 book-focused sites, blogs, or social media posts. These are the readers who
 got it. They're the seed of everything that follows.
 
-![](images/step-1-review.jpg)
+::: {.pull-quote}
+A reader who got it is the seed of it all.
+:::
 
 ## Step 2: Comment on their review with heartfelt thanks.
 
-Reply publicly to the review — as a comment, a post, or an email to your
+Thank the reviewer for their review. Ideally you do this on the review itself. Be as specific as they were. Be as warm as they were. You're not just
-list. Be as specific as they were. Be as warm as they were. You're not just
 thanking one reader. You're showing every future reader what it looks like
 when someone gets your work and you notice.
 
-![](images/step-2-thankyou.jpg)
+::: {.pull-quote}
+You're not just thanking one reader.
+:::
 
 ## Step 3: Share what they connected with in your story.
 
 Share what the reader actually connected with in your story publicly to
-your audience: on social media, your email list, wherever your readers are.
+your audience: on social media, your email list, wherever your readers are. Before you thanked them. Now you're responding to the specific thing they connected with.
-You're not just responding to one person. You're becoming a beacon: showing
+ You're not just responding to one person. You're becoming a beacon: showing
 other readers like them that your stories are out there and that someone
 who needed your stories already found them.
 
-![](images/step-3-computer.jpg)
+:::: {.closing .columns}
-
+::: {.column width="30%"}
-::: {.closing}
 ![](images/author-photo.jpg){.author-photo}
+:::
 
+::: {.column width="70%"}
 By: Will Estes — ReGround
 
-**Are you wondering how to get your stories in front of readers who need them?**
+**You don't need a bigger microphone. You need the one reader who's already looking for you.**
 
-Let's talk one on one and find out if this is the right fit for you. I'll
+Let's talk. I'll look at your specific situation, and we'll map out how you get
-look at your specific situation. We'll map out how you keep writing and get
+your stories to the readers who need them.
-your stories to reach the readers who need them.
 
-[Get a Free Strategy Session](http://reground.org){.cta-button}
+[Let's talk.](https://reground.org/talk){.cta-button}
 :::
+::::